Usage limits

Requests to the Zendesk Support API may be subject to the following usage limits:

Notwithstanding the limits specified in this document, the system might still limit requests if it detects an unusual spike in requests from all sources for the account, including internal product requests. For example, this can happen in a denial-of-service attack. See Account limit.

Monitoring your request activity

You can compare your request activity in the last 24 hours against your rate limit. See Tracking API activity against your rate limit.

You can use the following response headers to confirm the account's current rate limit and monitor the number of requests remaining in the current minute:

X-Rate-Limit: 700
X-Rate-Limit-Remaining: 699

See Best practices for avoiding rate limiting.

If the rate limit is exceeded, the API responds with a HTTP 429 Too Many Requests response code and a body that details the reason for the rate limiter kicking in. The response has a Retry-After header that tells you for how many seconds to wait before retrying. You should anticipate this in your API client for the smoothest possible experience.

Plan rate limits

As an API consumer, you should expect to be able to make the following number of requests per minute per Zendesk Support account:

Plan Requests per minute
Essential 10
Team 200
Professional 400
Enterprise 700
High Volume API Add-On (Professional or Enterprise) 2500

The Add-On increases a qualifying plan's limit to 2500 requests per minute. It doesn't add an additional 2500 requests to the plan's limit. Subject to Zendesk’s prior written consent, Zendesk may allow you to increase API usage limits beyond 2500 requests per minute for an additional fee.

The rate limits for the Help Center API are the same as for the Support API and also depend on the Support plan. However, requests to the Help Center API don't count against the rate limit of the Support API, and conversely.

Endpoint rate limits

Some endpoints have their own rate limit. For example, the Update Ticket endpoint has a rate limit of 30 updates to the same ticket by the same agent within a 10-minute period. Zendesk reserves the right to adjust the rate limit for given endpoints to provide a high quality of service for all clients.

Name Path Rate limit
List Tickets GET /api/v2/tickets.json?page={num} 50 per minute where num is over 500
Update Ticket PUT /api/v2/tickets/{id}.json 30 per 10 mins per user

100 per min per account
Incremental Exports global limit GET /api/v2/incremental/* 10 per 1 min
Incremental Exports with High Volume add-on GET /api/v2/incremental/* 30 per 1 min
Exporting Views GET /api/v2/views/{id}/export.json 100000 per 1 hour

Endpoint volume limits

Starting November 5, 2020, the rate limit for certain endpoints will change after reaching a certain number of pages in a paginated response. If the new limit is exceeded, the API responds with a 429 error with a Retry-After header specifying how many seconds to wait before retrying.

Name Path Rate limit
List Tickets GET /api/v2/tickets After page 500, 50 requests per min
List Users GET /api/v2/users/{id}.json
GET /api/v2/groups/{id}/users
GET /api/v2/organizations/{id}/users
After page 10,000, 100 requests per min
List Tags PUT /api/v2/tickets/{id}.json After page 500, 50 requests per min

Job limit

Some endpoints such as the Update Many Tickets endpoint queue background jobs to do the work. You can have up to 30 queued or running jobs at once. If you exceed the limit, you will receive a "TooManyJobs" error. Example:

{
  "error":"TooManyJobs",
  "description":"Too many UserBulkUpdateJobV2 jobs are currently queued or running. Try again later.",
  "current_job_ids":["14b1939441cb2e96d0c0835ede22ce03", ...]
}

Apps rate limit

API requests made by Zendesk apps are subject to an additional rate limit of 100 requests per minute per user per app. See Rate limits in the Apps framework docs.

Account limit

Zendesk might limit requests if it detects an unusual spike in requests from all sources for the account, including internal product requests. For example, this can happen in a denial-of-service attack. The account-wide limit is 100,000 requests per minute.

CPU-time limit

Zendesk also tracks the CPU time an account consumes over time. If you're fetching large volumes of records and get a 429 error even though you're within the documented rate limits, it may be due to a CPU-time limit.