Does your plan include API access? Which common tools gate their API by tier

You have planned an integration, picked Zapier, Make or a developer to build it, and then the connection fails, or a vendor tells you the feature you need "requires a higher plan". Very few firms check API access when they buy software, because the API is not something anyone on the team uses directly. It only matters on the day you try to connect two tools.

The direct answer: most business tools now include some API access on paid plans, but many limit it in one of three ways. Some lock the API itself to certain editions, some lock the instant parts (webhooks and workflow actions that send data out) to higher tiers, and almost all set call limits that scale with your plan. Before you build anything, check all three for every tool in the integration. The rest of this article shows how they apply to tools that 10 to 50 person firms commonly use.

The three ways vendors gate their API

Knowing which kind of limit you are facing tells you what the fix is.

1. No API on lower plans. The integration cannot be built at all until you upgrade or buy an add-on. Salesforce is the best-known example.
2. API included, but webhooks or outbound actions gated. You can read and write data, but the tool cannot notify another system the moment something changes. Your integration still works, but it has to poll, which is slower and uses more of your automation allowance. Our guide to webhooks vs polling explains why that matters.
3. API included, with limits that scale by plan. Everything works in testing, then a nightly sync or a bulk import hits a daily cap partway through. These are the failures people notice last.

Tool by tool: what to check

The table below summarizes what each vendor's own documentation said in October 2026. Details follow, with links to the sources; check them again before you sign, because plan packaging changes often.

Salesforce

Salesforce's help article on editions with API access says Essentials and Group Edition cannot get API access, Professional Edition can buy it as an add-on, and Enterprise and above include it. This is the clearest "no API" case among common CRMs. Our article on Salesforce Professional Edition API access covers the add-on, the error code to look for and the alternatives.

Calendly

Calendly's API overview says basic GET and POST requests work on any plan, but webhooks and Scheduling API endpoints need a paid subscription: Professional, Standard, Standard Plus, Teams, Teams Plus or Enterprise, as listed in October 2026. In practice, "send new bookings to the CRM as they happen" needs a webhook, so a free account will not do it properly.

HubSpot

HubSpot's API is available across its tiers, but the limits differ. According to HubSpot's API usage guidelines, as published in October 2026, a privately distributed app gets:

• Free and Starter: 100 requests per 10 seconds per app, 250,000 per day per account.
• Professional: 190 per 10 seconds, 625,000 per day.
• Enterprise: 190 per 10 seconds, 1,000,000 per day.

The daily limit is shared by every private app in the account, so three small integrations draw from one pool. Separately, the workflow action that sends a webhook to another system is listed in HubSpot's knowledge base article on webhooks in workflows as a Data Hub Professional or Enterprise feature. Older HubSpot pages call it Operations Hub; check the "Available with" line on the live article for your portal.

Xero

Xero's API has no customer-side tier, but since 2026 Xero charges app developers by tier. Its developer pricing page lists a free Starter tier for up to 5 connected organizations with 1,000 calls per organization per day, and paid tiers above it. Xero's FAQ says bespoke integrations built for your own practice or a single client are exempt from the new pricing. Read our article on Xero API pricing changes for the details, including the Journals endpoint rule that affects reporting tools.

Clio Manage

Clio's rate limits page gives a default of 50 requests per minute per access token during peak hours, higher off-peak, and says Clio does not grant custom increases to applications. That is enough for day-to-day syncs but slow for bulk work such as importing years of matters. We could not find a public statement on which Clio plans include API access, so ask Clio before you rely on it.

Pipedrive

Pipedrive meters its API with a daily token budget. Its help article on API rate limits says each call consumes tokens, the limit resets every 24 hours, requests fail once it is reached, going over does not add charges, and you can buy extra allowances or upgrade for higher limits. The article points to a Usage page showing which users and integrations make requests; if several integrations draw on the same budget, one heavy sync can block the others until the reset.

Karbon

Karbon's authentication guide lists "a Karbon account with API access" as the prerequisite and says credentials are issued from Settings, Connected Apps, API Applications. Its pricing page does not spell out API access by plan, so if you cannot see that menu, ask Karbon support whether your plan includes it and how to switch it on.

How to check your own stack in an hour

You do not need a developer for this. For each tool in the integration you are planning:

1. Find your exact plan name. It is usually in the billing or account settings, not on the invoice summary.
2. Search the vendor's help center for "API" plus your plan name, and for "webhooks". Note what you find with the link and date.
3. Look for the call limit. Write down the daily or per-minute figure and whether it is per user, per app or per account.
4. Check your automation platform's app page. Zapier and Make list requirements for each app; if they say "premium app" or "requires plan X", believe them.
5. Estimate your volume. How many records will the integration read or write per day, including the first import? Compare that with the limit.
6. Ask the vendor in writing whenever the documentation is unclear. "Does our plan include API access and webhooks, and what are our limits?" is a normal support question.

What to do if your plan does not include what you need

• Compare the add-on with the next tier. A per-user API add-on across your whole team can cost almost as much as an upgrade that brings other features too.
• Turn the integration around. If tool A has no webhooks, perhaps tool B can push data into A instead, or a form tool can write to both.
• Accept polling where speed does not matter. A nightly sync of time entries does not need to be instant.
• Check native integrations and marketplace apps. Some work on plans where the open API does not; certified Salesforce AppExchange apps on Professional Edition are the documented example. Get the vendor's confirmation in writing.
• Ask whether the tool still fits. If every integration you need sits behind an upgrade, that is a fair reason to review whether you still need it at all.

If the integration moves client or patient data, also check with your compliance lead what the vendor's terms say about API access to that data.

How Flow Mesh helps

Every engagement starts with a first call, then a stack audit scoped in writing before it starts. It gives every tool you pay for a verdict (keep, configure, consolidate or replace), including whether your current plans actually allow the integrations you want, and a written scope for the ones worth building. Any build is quoted in writing after the audit and runs inside your own accounts.

Key takeaways

• Vendors gate APIs in three ways: no API on lower plans, gated webhooks or outbound actions, and call limits that scale with your plan.
• Salesforce Essentials and Group have no API; Professional needs an add-on. Calendly webhooks need a paid plan.
• HubSpot, Clio and Pipedrive include API access but cap usage, and shared daily limits can stop every integration at once.
• Check plan name, API, webhooks and limits for each tool before you build, and get unclear answers from the vendor in writing.
• If your plan falls short, compare add-on and upgrade costs, reverse the direction of the integration, or review whether the tool still fits.