Yes. Zendesk publishes a Support API, also called the Ticketing API, for tickets, users and organisations, plus separate APIs for Help Center, messaging, voice and custom data. It authenticates with OAuth access tokens, and requests per minute depend on your plan, from 200 on Team up to 2500 on Enterprise Plus, as of Nov 2026.
A map of the APIs
The API reference is organised by what you want to do:
- Ticketing: the Support API, for tickets, users, organisations and related objects, and the JIRA Integration API.
- Help Center: articles and the knowledge base.
- AI Agents.
- Messaging: the Conversations API.
- Voice: the Talk API.
- Custom data: the Custom Objects API.
There's also a Postman collection covering all the APIs except Sell and Sunshine Conversations, which is the quickest way to try calls before writing code.
Which API fits a common job
For most small businesses the job decides the API. Creating tickets from your own website form, or syncing customers from a CRM, is Support API work. Keeping help articles in step with another system belongs to the Help Center API. If you're building chat into an app, that's the Conversations API, and call logging is the Talk API. Custom Objects suits data that doesn't fit tickets or users, such as orders or subscriptions you want agents to see.
Authenticating
Zendesk supports OAuth access tokens for API requests, and it's the route the docs point you to. An OAuth token gives access to a single Zendesk instance. If you're building an app, integration or bot that will be used by several Zendesk customers, it must use global OAuth tokens.
For a business building something for its own account, a standard OAuth token is the route. For an agency or software vendor building one integration for many clients, plan for global OAuth from the start, because retrofitting it later means you'll be rebuilding the sign-in flow.
Requests per minute, as of Nov 2026
| Plan | Support and Help Center API requests per minute |
|---|---|
| Suite Team, Support Team | 200 |
| Suite Growth, Suite Professional, Support Professional | 400 |
| Suite Enterprise, Support Enterprise | 700 |
| Suite Enterprise Plus, or a qualifying plan with the High Volume API add-on | 2500 |
| Support Essential (legacy) | 10 |
Chat API requests are listed at 200 per minute across Suite plans. Zendesk may still limit requests during an unusual spike from all sources on an account, so don't treat the plan number as a guarantee at peak times; it's a ceiling, not a promise.
Plan for your own limit, not the headline
The Zendesk Developer Docs make two points worth building around. Integrations distributed to several customers must use global OAuth, and API tokens aren't supported for those requests. And the per-minute limit varies sharply by plan, with a fivefold jump from Team to Enterprise Plus. A sync that runs comfortably for a client on Enterprise Plus can hit the ceiling straight away on Team. Check the plan of every account your integration will touch before you design a polling job.
Handling a 429 and retrying safely
When you go over the limit, the API responds with 429 Too Many Requests and a Retry-After header telling you how many seconds to wait. Headers such as X-Rate-Limit and X-Rate-Limit-Remaining show the limit and how many requests are left in the current minute, so you can slow down before you hit it.
Retries need care when you're creating tickets. A retry after a timeout could create the same ticket twice. Ticket creation supports an idempotency key that lets you retry a request without creating duplicate records, so send one with every create call.
If you're choosing between polling and event-driven updates, this explainer on APIs and webhooks helps, and my list of API documentation tools is useful if you're publishing docs for your own integration.
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.
How Freshdesk compares
Freshdesk publishes API v2 documentation with endpoints under /api/v2/, including custom object schemas and records. For a wider comparison of the help desks themselves, see my round-up of Zendesk alternatives.
My advice before you build
Use the Postman collection to try your calls first. Pick OAuth, or global OAuth if more than one customer will use it. Read X-Rate-Limit-Remaining on every response and pause on 429 for the Retry-After time. Add an idempotency key to every ticket create, and design for the smallest plan you'll support, not the biggest.
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 can the Zendesk Support API do?
It works with tickets, users, organisations and related objects.
How do I authenticate to the Zendesk API?
Zendesk supports OAuth access tokens; distributed apps must use global OAuth tokens.
What is Zendesk's API rate limit?
On Suite, as of Nov 2026: 200 requests per minute on Team, 400 on Growth and Professional, 700 on Enterprise and 2500 on Enterprise Plus.
What happens if I exceed the limit?
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 a qualifying plan's limit to 2500 requests per minute.
