Zoho CRM API Limits: Credits, Concurrency and Integration Planning

How do Zoho CRM API limits and credits work?

Zoho CRM does not limit calls per minute. Instead it uses two controls. Credits cap how much work your organization can do in a rolling 24-hour window, counted from each call. Concurrency caps how many calls can be running at the same moment.

Each call deducts credits based on how heavy it is. A simple read costs one credit; converting a lead costs five; starting a bulk write job costs 500. Zoho's docs say that once you have used 50% or more of the daily allowance, the response header X-API-CREDITS-REMAINING shows what is left, which is useful for monitoring. Trial editions follow the same limits as the matching paid edition.

How many API credits does each edition get?

The allowance is a base of 50,000 credits plus an amount per user license, plus any add-on credits, capped at an edition maximum. These are the figures on Zoho's API limits page in November 2026.

Worked examples: Zoho's own calculator shows 100 Enterprise users getting 150,000 credits. A 20-user Professional account gets 50,000 + (20 x 500) = 60,000. A 10-user Standard account gets 52,500. If you need more, Zoho says the super admin can raise the limit from the API Dashboard, billed monthly for credits actually used. Check Zoho's pricing for add-on rates in your region.

Which API calls use the most credits?

Most integration budgets are blown by a few expensive operations run too often, not by ordinary reads. The table lists costs from Zoho's credit table that matter most in planning.

The lesson: batch writes in groups of 100, use COQL to fetch only the fields you need, and avoid polling record counts on a timer.

Here is how that plays out on a 20-user Professional account with 60,000 credits a day. A web shop that updates 3,000 orders one record per call uses 3,000 credits. The same updates sent in batches of 100 use 30 calls at 10 credits each, or 300 credits. Sending 500 emails a day through the Send Mail API, at 20 credits each, uses 10,000 credits, a sixth of the daily allowance. Small design choices decide whether you need add-on credits.

What are concurrency and sub-concurrency limits?

Concurrency is the number of calls your organization can have active at once, per app: from 5 on Free to 25 on Ultimate. Heavy calls also share a sub-concurrency limit of 10 across all editions. Zoho lists these as get records with cvid or sort_by, convert lead, insert/update/upsert of more than 10 records, send mail, search records from a function, the Query API and the Composite API.

When a sub-concurrency limit is reached, Zoho returns a TOO_MANY_REQUESTS error. In practice this hits integrations that fire many parallel writes, such as a web shop pushing a sale burst. The fix is a queue with a small worker pool and retry with back-off, not more credits.

Remember that the main concurrency limit is shared by every app connected to your organization. If an ERP sync, a marketing tool and a reporting connector all run on the hour, they compete for the same slots. Stagger schedules so heavy jobs do not overlap, and give real-time syncs priority over nightly batch work.

Do Deluge functions, Zoho Flow and webhooks count against API limits?

Deluge integration tasks do. Zoho's docs say tasks such as zoho.crm.searchRecords consume the same credits as the matching API, and the API Dashboard shows usage under Credits by Application/Functions. Integration tasks also have org-level concurrency limits that match the edition figures. If you write custom functions, our Deluge scripting examples show patterns that keep calls low.

Zoho Flow and third-party connectors call the API on your behalf, so their reads and writes draw from the same pool. Workflow webhooks have their own daily caps on Zoho's comparison page; on Enterprise, for example, it lists 500,000 calls a day or 500 per user license, whichever is lower. Functions have a separate credit pool that Zoho's comparison page lists by edition.

How should you plan a Zoho CRM integration around API limits?

Estimate usage before you build, then design for the peak day, not the average. Use this sequence.

1. 1List every system that will read or write CRM data, including Flow, extensions and AI tools.
2. 2For each, estimate calls per day and their credit cost from Zoho's table.
3. 3Replace polling with Notification APIs or workflow webhooks, so CRM tells you when records change.
4. 4Use Bulk Read for exports and backups; Zoho says it runs as an async job and returns a CSV, which avoids thousands of page reads.
5. 5Batch writes to 100 records per call and upsert on a unique key to avoid duplicates.
6. 6Queue requests and cap parallel workers below your concurrency limit.
7. 7Read X-API-CREDITS-REMAINING and alert when usage passes a threshold you set.
8. 8Review the API Dashboard monthly and remove integrations nobody owns.
9. 9Document each integration's owner, credit estimate and failure alert in one shared register.

Plan sync direction too. Native integrations such as Zoho CRM with Zoho Books handle much of this for you, while custom ERP or warehouse syncs need the design above. Test against a sandbox or trial account first; Zoho says trial editions carry the same API limits as the matching paid edition, so load tests there give a fair picture.

How can Flowpeak help plan and build your integration?

Flowpeak is a registered Zoho partner with Zoho-certified consultants, delivering remotely from Chennai. We estimate your credit use, choose between native connectors, Zoho Flow and custom code, and build integrations with queues, retries and failure alerts. Fixed-price AI integrations include OpenAI (ChatGPT) with Zoho CRM at USD 1,180, Claude at USD 1,330 and Google Gemini at USD 1,020. Other integrations are quoted in writing; see our Zoho integration services.

Frequently asked questions