zoho
Zoho CRM API Limits in 2026: How to Budget Your Credits
Zoho CRM API limits run on credits, not call counts. See the per-edition credit maths, the operations that cost most, and how to design integrations that fit.
5 Nov 2026 · 10 min read · Abhijeet Singh

On this page 9 sections
Most Zoho CRM integrations that break in production break for the same reason: nobody budgeted the API. Zoho CRM API limits are not a simple cap on calls per day. They are a credit system in which operations cost wildly different amounts, plus a separate concurrency ceiling that fails in a completely different way. Get either wrong and your nightly sync stops silently at two in the morning, which is exactly the failure our guide to catching silent n8n workflow failures is about.
This is the model I work through before building a Zoho integration, using the figures Zoho publishes in its v8 developer documentation, the latest API version Zoho documents as of November 2026.
Zoho CRM API limits are a credit budget, not a call count
Every API call costs at least one credit, and your org gets a daily credit allowance. The detail most teams miss is that the allowance runs on a rolling 24-hour window that starts when each call is made. There is no midnight reset to wait for. If you burn the allowance with a careless backfill at three in the afternoon, you stay constrained until those individual calls age out one by one.
Zoho's limits documentation also states there are no per-minute call limits at all. Only simultaneous active calls are restricted. That one sentence should change how you build. You do not need to throttle requests per second. You need to control how many are in flight at once.
How many credits you actually get
The allowance is a base figure plus a per-user amount, with a ceiling per edition. Per Zoho's v8 limits page, Free is fixed at 5,000 credits. Paid editions start from a base of 50,000 and add an allocation for every user license.
Standard and Starter add 250 credits per user and cap at 100,000. Professional adds 500 per user with a ceiling of 3,000,000. Enterprise and Zoho One add 1,000 per user with a ceiling of 5,000,000. Ultimate and CRM Plus add 2,000 per user and the documentation lists no ceiling. Purchased add-on credits sit on top, and trial editions get the same limits as their paid equivalents.
So a Standard org with ten users gets 52,500 credits a day, which sounds generous until you price the operations below. The same documentation notes that once usage passes half the daily limit, responses carry a credits-remaining header. That is the cheapest monitoring signal you will ever get, so read it and log it.
The credit costs that quietly wreck budgets
Most calls cost one credit. The exceptions are where integrations die.
Reads are mostly cheap. A COQL query costs one credit for a LIMIT up to 200, two from 201 to 1,000, and three from 1,001 to 2,000. Fetching records through a custom view ID costs three, the IDs of deleted records cost two, and a related-records count costs two per related list.
Writes are priced per batch, which rewards batching. Insert, update and upsert cost one credit per ten records, and since a single call accepts at most 100 records, a full call costs ten credits. Adding or removing tags costs one credit per fifty records up to 500 records. A mass delete by record ID costs one credit per hundred records.
Then the expensive tier. Sending mail costs twenty. Converting a lead costs five, but a mass conversion costs 200. Merging records, a mass owner change, a module record count, a mass delete by custom view and a Bulk Read initialize all cost fifty each. A Bulk Write initialize, transferring records while deleting a user, and creating a custom module each cost 500. Custom field changes cost ten per field, and data sharing rule changes cost 250 each.
Two consequences follow. A schema migration that creates thirty custom fields spends 300 credits before it touches a single record. And, the one that catches people out, Zoho states that integration tasks invoked from inside Deluge functions consume the same credits as the equivalent API. Your internal workflow automation draws from the same budget as your external integration, and nobody tells you until the budget is gone.
Concurrency is a separate limit and it fails differently
Credits are a daily budget. Concurrency is instantaneous, applied per org and per application. Zoho documents five concurrent calls on Free, ten on Standard and Starter, fifteen on Professional, twenty on Enterprise and Zoho One, and twenty-five on Ultimate and CRM Plus.
A sub-concurrency limit of ten also applies to every edition regardless of what you pay. It governs the heavier operations: fetching records with a custom view ID or sort order, converting a lead, inserting or updating more than ten records at once, sending mail, calling Search Records from inside a function, the Query API and the Composite API. Zoho notes it does not apply to integration tasks.
Breaching either ceiling returns a too-many-requests error, and it looks random in logs because it depends on what else was running at that instant. If your integration platform fans out parallel branches, cap its concurrency below your edition's number and leave headroom for the people using the CRM in a browser at the same time.
Functions and integration tasks have their own quota
Functions are metered separately, and the numbers are far smaller than the API allowance. Per Zoho's functions limits documentation, each Deluge execution deducts one credit, while Java, Node.js and Python functions are charged by execution time at one credit per ten seconds.
Standard and Professional both get 5,000 free credits plus 200 per user license, capped at 15,000 and 20,000 respectively, and can only reach Functions through Extensions at all. Enterprise and Zoho One get 20,000 free plus 500 per user plus add-ons, to a maximum of 400,000. CRM Plus and Ultimate get 20,000 free plus 1,000 per user.
The per-function ceilings matter just as much. A function gets a 10 MB response size and 200,000 lines of execution per invocation, counted as lines the runtime actually executes including loops and child functions. Execution time depends on the trigger: ten seconds from a related list, button, validation rule or REST API call, thirty seconds from workflow, blueprint or approval automation, and fifteen minutes for scheduled functions. Anything slower is forcibly terminated.
That thirty-second automation ceiling is why I push heavy logic out of Deluge into an external workflow engine. It is not room enough to call three services and handle their failures properly.
Four design rules that keep an integration inside the limits
Replace polling with notification channels. Our walkthrough on connecting Zoho CRM to n8n shows the webhook side of this pattern. The biggest credit waster I see is a job that reads the CRM every five minutes to find what changed. Zoho's Notification APIs push near real-time alerts to a URL you nominate when records are created, updated or deleted, with a separate channel per module carrying its own ID. From version 6 you can narrow a channel with a notification condition so it only fires on specific field changes, such as a deal stage moving. Each channel carries an expiry you set, so build renewal into your own scheduler and monitor it, because a silently expired channel looks exactly like a quiet sales week.
Pick the right read API for the volume. Zoho's own Kaizen developer series makes the comparison directly: standard record reads page in small batches, while a Bulk Read job exports very large data sets without materially denting your allowance. It runs asynchronously, returns a ZIP of CSV files, and supports a callback URL so you are not burning credits polling for job status. For a few thousand records a paged query is fine. For tens of thousands, one fifty-credit Bulk Read job is dramatically cheaper.
Batch every write, and never write per record. Because inserts and updates are priced per ten records inside a 100-record call, a loop that updates one record at a time costs ten times the batched version. For genuinely large loads, Bulk Write accepts up to 25,000 records in a single call. The 500-credit initialize fee looks expensive right up until you compare it with the per-record alternative.
Cache what does not change. Module metadata, field definitions, users, roles and picklist values all cost credits and rarely change during a sync run. Fetch them once, hold them in memory, and stop re-reading them inside loops.
Watch the dashboard before it watches you
Zoho CRM includes an API dashboard showing credits used and unused across a chosen period plus your average calls per day. You can break usage down by module, calling IP address, HTTP method, user and time, and the graph view shows which applications are making the calls. Critically, it also names the functions that consumed integration tasks and how many credits they used, which is how you find the runaway Deluge script.
Two caveats. Credit statistics refresh on roughly a fifteen-minute delay, although raw call counts update immediately, so do not debug a live spike from this screen. And usage data older than thirty days is deleted periodically, so export it yourself if you want long-run trends.
Zoho's guidance also notes that the org super admin is emailed at 80, 90 and 100 percent of available credits, and those thresholds can be customised. Make sure that is a monitored inbox rather than a founder's personal account. If you consistently run over, extra credits can be bought from the dashboard on a pay-as-you-go basis, so price that option before buying an edition upgrade purely for API headroom.
Where the documentation contradicts itself
One honest warning, because you will hit it. As of November 2026, Zoho's API limits page prices COQL queries in bands up to a LIMIT of 2,000 records, and the v8 COQL overview also gives 2,000 as the maximum. The v8 page for getting records through a COQL query states a maximum of 200 records per call, with pagination to 100,000 in total. Older Zoho community posts quote different figures again.
Do not design around the larger number because a blog said so, including this one. Test the real page size against your own org and edition before sizing a sync window, and treat every limit here the same way. That page also caps a query at two joins, five formula fields, five aggregate fields and a hundred values in an in clause, and multi-select lookup fields can only be queried through their linking module.
How this works out in practice
In the Zoho CRM integration and automation work we run at AbhijeetBuilts, API budgeting is a sizing exercise done before the build, not a fire fought afterwards. We count expected daily record volume, price it against the client's actual edition and user count, then choose the pattern that fits the budget rather than the one that is quickest to wire up. That usually means notification channels instead of polling, bulk jobs for anything resembling a migration, batched writes everywhere, and heavy orchestration in an external workflow engine where the time limits are ours to set rather than Zoho's. The client gets a number, and knowing a sync will consume a fifth of a daily allowance is the difference between an integration you can extend next quarter and one that falls over the first time the business grows.
If you are planning a Zoho CRM integration, migrating a large data set in, or trying to work out why a working sync started failing intermittently, get in touch through the website. A short sizing conversation up front is considerably cheaper than rebuilding an integration that outgrew its credit budget.
Related resources
Keep building the automation map
Move from the guide into the services and proof pages connected to this topic.
Related services
Service
Explore Zoho CRM Consulting
Zoho CRM setup, custom modules, client scripts, Deluge functions, workflow rules, and cross-module automation.
Service
Explore n8n Workflow Development
Custom n8n workflow automation for lead capture, CRM sync, AI enrichment, approvals, and notifications — built to keep running when nobody is watching.
Service
Explore Custom CRM Implementation
Custom CRM architecture for sales pipelines, operations handoff, service workflows, invoicing, and reporting dashboards.
Further reading
Article
Read: How to Connect Zoho CRM to n8n: Setup, Webhooks and Duplicates
Connect Zoho CRM to n8n the reliable way: the right data centre, OAuth setup, webhooks for new records, duplicate checks, and the updates that wipe data.
Article
Read: Does Zoho CRM Send Your Data to OpenAI? 2026 Privacy Guide
Does Zoho CRM data go to OpenAI? See which AI models Zia uses, how bring-your-own-key works, data center storage and GDPR checks before switching AI on.
Article
Read: WhatsApp Lead Follow-Up in Zoho CRM: 3 Options for 2026
WhatsApp lead follow-up in Zoho CRM: compare Cadences, Zia Agents and n8n with Meta Cloud API or Twilio, with USD costs after Meta's October 2026 change.
Proof pages
Case study
See case study: Custom Zoho CRM with Auto-Pipeline for a Freight Forwarder
A freight CRM that carries an enquiry through contacts, accounts, deals, quotes, jobs, cost sheets, and invoicing — with client scripts and Deluge automation removing the re-typing between every stage.
Case study
See case study: Complete Zoho Stack for a B2B Packaging Manufacturer
One Zoho operating system for a B2B packaging manufacturer — sales, service, inventory, accounting, ticketing, and analytics — replacing the legacy Excel and Salesforce files the business used to run on.