429 RATE_LIMITED.
Limits per plan
The limit depends on your organization’s plan:
A sandbox always has the sandbox limit, whatever the plan of the organization that created it. An organization on Solo that kept API access when API access moved to Team has 120 requests per minute.
If sajn has agreed a custom limit with your organization, it replaces the limit of your plan. To discuss a higher limit, contact [email protected].
We recommend reading your limit from the response headers rather than hard-coding these numbers, so your client adapts when your plan changes.
Rate-limit headers
Every authenticated response from the REST API carries the following headers:
For example, a Team organization’s response has headers similar to the following:
Limit responses
A request over the limit returns an HTTP429 Too Many Requests status code, a Retry-After header, and the usual error body with the code RATE_LIMITED. In API version 2026-09, the code is TOO_MANY_REQUESTS.
Retry with backoff
How to retry depends on the error:429 RATE_LIMITED: wait the number of seconds inRetry-After, and then retry. It’s usually a few seconds.500 INTERNAL_ERROR,503 UPSTREAM_UNAVAILABLE, and network errors: retry with exponential backoff and jitter.
Idempotency-Key header on every attempt. For more information, see Idempotency.
The following samples retry a request up to five times:
code and requestId.
Stay within the limits
To use fewer requests:- Subscribe to webhooks instead of polling for changes.
- Request up to 100 items per page with
limit. - Sync with
updatedAfterso each run reads only what changed. For more information, see Sync changes incrementally. - Spread scheduled jobs over time instead of starting them all at the same minute.
403 LIMIT_EXCEEDED, which a retry doesn’t fix; see Errors.
