Guides
Rate limits
Each API key can make 120 requests per minute. Response headers tell you how much of that is left.
The limit
The limit is 120 requests per minute, counted per API key. Two keys do not share a count, and every request made with a key counts towards that key's limit.
Rate limit headers
| Header | Meaning |
|---|---|
X-RateLimit-Limit | The number of requests the key may make in one window. |
X-RateLimit-Remaining | The number of requests left in the current window. |
X-RateLimit-Reset | The number of seconds until the current window ends and the count starts again. |
Retry-After | Only on a 429 response: the number of seconds to wait before trying again. |
When you go over the limit
A request over the limit is not carried out. It gets a 429 response with the code rate_limited and a Retry-After header.
HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 12{
"error": {
"code": "rate_limited",
"message": "Too many requests. Slow down and try again.",
"request_id": "2f9d6c1e-7a4b-4d3c-8e5f-1a2b3c4d5e6f"
}
}Backing off
- On a
429, wait for the number of seconds inRetry-After, then send the request again. - If the retry is also rate limited, wait longer before each further attempt instead of retrying at once.
- Watch
X-RateLimit-Remainingand slow down before it reaches zero, rather than sending requests in bursts. - When you read many pages, use a larger
page_sizeso you need fewer requests. See Pagination.