What we do
Tools
Industries
Department
How we workLet's talk →
Home/Zendesk/Zendesk API
Zendesk developer reference

The Zendesk API: Authentication, Endpoints, Pagination, Rate Limits and Webhooks

The Zendesk API is a REST API for tickets, users, organizations, search and most of what agents do by hand. Everything below is what you need at the keyboard. The big change right now is authentication: API tokens are being removed, and OAuth is the way in. Deciding what to connect rather than how? Our Zendesk integrations hub covers that.

The essentials

Base URL: https://{subdomain}.zendesk.com/api/v2/, JSON in and out.

Auth: an OAuth access token sent as Authorization: Bearer {token}. Create the OAuth client in Admin Center, then request tokens with the client_credentials or authorization_code grant.

Admin Center Apps and integrations APIs

API tokens ({email}/token:{api_token} over Basic auth) are deprecated. No new ones can be created, unused tokens are being switched off, and every remaining token stops on April 30, 2027.

Move an existing integration from an API token to OAuth

Both can run side by side until April 30, 2027, so move one integration at a time.

  1. 1

    Find every token still in use

    Admin Center Apps and integrations APIs API tokens

    Check each token's last-used date and description, and run Zendesk's usage report to see which tokens and IP addresses are still calling. That's your list of scripts, middleware and third-party tools to move.

    Watch for: a monthly or quarterly job. If it ran rarely, its token may already have been switched off as unused.

  2. 2

    Create an OAuth client for each integration

    One client per integration keeps access separate and lets you revoke one without breaking the rest. Request only the scopes the job needs, such as read for a reporting pull.

  3. 3

    Swap the header and handle expiry

    Replace the Basic header with Authorization: Bearer {access_token}. Don't store one token forever: build the code to request a new token or refresh it when the old one expires.

  4. 4

    Check what calls Zendesk from inside Zendesk

    Webhooks that call your own Zendesk account with an API token stop working at the cutoff. Built-in Zendesk actions in action flows don't need a token, but custom actions that call Zendesk endpoints do, and must move to OAuth too.

Which endpoint for which job

Job Endpoint Watch for
Create a ticket from another system POST /api/v2/tickets Set custom fields as custom_fields: [{ id, value }]. Get the IDs from GET /api/v2/ticket_fields, because names aren't accepted.
Update status or add a comment PUT /api/v2/tickets/{id} A comment goes in a comment object. Max 30 updates per user per ticket in 10 minutes.
Create many tickets at once POST /api/v2/tickets/create_many Up to 100 per call. It returns a job to poll, not the tickets, and an account can have 30 jobs queued or running.
Find a specific slice of records GET /api/v2/search?query= Results are capped, so it's for finding records, not exporting them. Use the export search endpoint for large result sets.
Pull everything that changed since last run GET /api/v2/incremental/tickets/cursor?start_time= 10 requests a minute across the account, 30 with High Volume. Store the cursor and resume from it.
Keep customers in step with your CRM POST /api/v2/users/create_or_update 5 requests a minute per user. Match on external_id or email so you don't create duplicates.
Attach a file POST /api/v2/uploads Returns a token. Put it in the comment's uploads array on the ticket create or update.

Zendesk API rate limits by plan

Per minute, for the Support and Help Center APIs. Chat has its own limit of 200 a minute.

Plan Requests per minute Notes
Suite Team / Support Team 200 The High Volume add-on isn't available here.
Suite Growth, Suite Professional, Support Professional 400 High Volume add-on raises it to 2,500, with at least 10 agent seats.
Suite or Support Enterprise 700 High Volume add-on raises it to 2,500.
Suite Enterprise Plus 2,500 No add-on needed.

Where Zendesk API builds go wrong

Treating a 429 as a failure and moving on

How you'll know: A sync finishes "successfully" but the counts don't match Zendesk.

Fix: On 429, wait the seconds in the Retry-After header and retry the same request. Watch X-Rate-Limit-Remaining to slow down before you hit the wall, and log any request that still fails.

Offset pagination on a big list

How you'll know: Requests start returning 400 after page 100.

Fix: Offset paging stops at 100 pages or 10,000 records. Add page[size] to switch to cursor paging, follow links.next, and stop when meta.has_more is false.

Hard-coding custom field IDs

How you'll know: A field gets renamed or replaced in Admin Center and tickets arrive with blanks.

Fix: Look IDs up from the ticket fields endpoint on start, map them by a stable key, and alert when an expected field is missing.

Trusting every webhook to arrive once

How you'll know: Duplicate records downstream, or an event that never showed up.

Fix: Zendesk webhooks are best-effort: the same event can arrive twice, and calls can be dropped while the circuit breaker is tripped by a failing endpoint. Make the receiver idempotent and reconcile with the incremental export on a schedule.

Before a Zendesk webhook goes live

  • Verify the signature

    Each request carries X-Zendesk-Webhook-Signature and X-Zendesk-Webhook-Signature-Timestamp. Compute HMAC-SHA256 over the timestamp plus the raw body with the signing secret, base64 it, and compare.

  • Answer fast and work later

    Return a 2xx as soon as the request is stored, and do the real processing in a queue. Slow responses are timed out and retried, which is where duplicates come from.

  • Decide what fires it

    A webhook can be called by a trigger or automation, or subscribed to Zendesk events such as user or organization changes. Pick one route per job so the same change doesn't send twice.

  • Keep it off API tokens

    If the webhook calls back into your own Zendesk, give it OAuth now. Token-based self-calls stop at the April 2027 cutoff.

Builds on the Zendesk API, and the parts it doesn't reach

Two jobs come up again and again. One is turning an outside event into a ticket that's already complete: a business whose order system flagged shipping exceptions had n-frames build the call that opens the ticket with the order number, customer tier and carrier filled in, so agents never start from a blank. The other is reporting without extra seats: a nightly pull through the incremental export into a database the company's reporting tool already reads, so leadership sees volume and resolution trends.

For something that runs inside the agent's screen, such as a custom sidebar panel, use the Zendesk Apps Framework instead of the bare API. A few account and billing screens have no endpoint at all, and those need a browser automation step. Planning what to connect in the first place is on the Zendesk hub, Zendesk's own rules are on Zendesk ticket automation, and receivers for outside events are covered under Zapier webhooks.

Questions people ask

What is the Zendesk API?

A REST API for working with Zendesk data from code: creating and updating tickets, managing users and organizations, searching, and exporting changes in bulk. Most integrations and custom automations talk to Zendesk through it.

Do I need a specific plan to use the Zendesk API?

No. Paid plans include API access. The plan sets the rate limit: 200 requests a minute on Team, 400 on Growth and Professional, 700 on Enterprise, and 2,500 on Enterprise Plus or with the High Volume add-on.

Is there a Zendesk SDK?

Yes, several. There are messaging SDKs for iOS, Android and the Web Widget, and the Zendesk Apps Framework has a client SDK for apps inside the agent workspace. For server-side calls most teams use plain HTTP or a community library.

What's the difference between the Ticket API and the Search API?

The Ticket API creates and changes individual tickets you already know about. The Search API finds tickets, users and organizations that match a query. Search results are capped, so for bulk data use the incremental export instead.

What if something isn't available through the Zendesk API?

A handful of admin and billing screens have no endpoint. n-frames automates that browser step directly, so the rest of the workflow still runs end to end without someone doing it by hand.

Are Zendesk API tokens going away?

Yes. New tokens can no longer be created, unused tokens are being switched off, and all remaining tokens stop working on April 30, 2027, with no extension. Move every integration to OAuth before then.

How do I verify a Zendesk webhook?

Take the X-Zendesk-Webhook-Signature-Timestamp value, append the raw request body, compute an HMAC-SHA256 with the webhook's signing secret, base64-encode it and compare it with X-Zendesk-Webhook-Signature.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.