The Zendesk API rate limit for Support and Help Center depends on your plan: 200 requests per minute on Suite Team, 400 on Growth and Professional, 700 on Enterprise and 2500 on Enterprise Plus. Go over and the API returns 429 Too Many Requests with a Retry-After header. Some endpoints have much tighter limits of their own.
Your plan sets the headline number
Zendesk ties its main API limit to your plan. These are the numbers on Zendesk's developer docs as of Nov 2026, and Zendesk may change them, so check the page before you build around them.
| Item | Limit | Applies to |
|---|---|---|
| Support and Help Center API | 200 requests per minute | Suite Team and Support Team |
| Support and Help Center API | 400 requests per minute | Suite Growth and Professional; Support Professional |
| Support and Help Center API | 700 requests per minute | Suite and Support Enterprise |
| Support and Help Center API | 2500 requests per minute | Suite Enterprise Plus, or High Volume API add-on |
| Update Ticket | 30 updates per 10 minutes per user per ticket | PUT /api/v2/tickets/{id} |
| Incremental Exports | 10 requests per minute (30 with High Volume add-on) | GET /api/v2/incremental/* |
| Queued or running jobs | 30 at once | Bulk endpoints such as Update Many Tickets |
The legacy Support Essential plan is listed at 10 requests per minute. The Chat API is limited to 200 requests per minute on all listed Suite plans. And Help Center API requests don't count against the Support API limit, or the other way round, so a knowledge base sync won't eat into your ticket automation.
Raising the limit
The High Volume API add-on raises a qualifying plan to 2500 requests per minute. It needs a minimum of 10 agent seats. It also lifts Incremental Exports from 10 to 30 requests per minute.
The endpoint limits that bite first
Zendesk's developer docs on rate limits show that some endpoints sit far below the plan number. Update User and Update Organization each allow only 5 requests per minute per user or organisation. Update Ticket allows 30 updates to the same ticket by the same agent within 10 minutes. A bulk job can hit a 429 on one of these while the plan limit has barely been touched.
Background jobs have their own ceiling too. You can have up to 30 queued or running at once, and beyond that you'll get a TooManyJobs error. If you use bulk endpoints such as Update Many Tickets, wait for jobs to finish before queuing more.
A pacing pattern that respects all of this looks like:
- Queue user and organisation updates so no single record gets more than 5 a minute.
- Group several ticket changes into one update instead of 30 small ones.
- Keep bulk jobs under 30 at a time and wait for them to finish.
- Run Incremental Exports on a slow schedule, not in a tight loop.
Reading the headers
Two response headers tell you where you stand. X-Rate-Limit shows your account's current limit, and X-Rate-Limit-Remaining shows how many requests you've got left in the current minute. When you go over, you get 429 Too Many Requests with a Retry-After header giving the seconds to wait.
Zendesk also says it may still limit requests if it spots an unusual spike from all sources on your account. So even inside the numbers, sudden bursts from several tools at once can get throttled. Spreading work out over the minute is safer than firing it all at the start.
How Freshdesk and Intercom handle it
Freshdesk's API rate limit is a number of calls per minute based on plan, applied account-wide regardless of agents or IPs. Intercom private apps have a default limit of 10,000 API calls per minute per workspace, with 25,000 per workspace across all apps. If you're weighing up a move, my roundup of Zendesk alternatives covers the wider field.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for teams automating Zendesk
Look up your plan's number, then look up the limit on every endpoint you call, because that's usually the real constraint. Read X-Rate-Limit-Remaining as you go, honour Retry-After, and batch user and organisation updates rather than looping through them. If you're often near the ceiling and have the agent seats, the High Volume add-on is the clean fix. For a lighter help desk with simpler limits, my list of Help Scout alternatives is worth a look.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What is the Zendesk API rate limit?
It depends on plan, from 200 to 2500 requests per minute on Suite, as of Nov 2026.
What happens when I exceed it?
You get a 429 Too Many Requests response with a Retry-After header.
Can I raise the limit?
The High Volume API add-on raises qualifying plans to 2500 per minute and needs at least 10 agent seats.
Do Help Center calls count against Support calls?
No. They have separate counts.
How do I see how many requests are left?
Read the X-Rate-Limit-Remaining header.
