Rate Limiting
The API enforces rate limits to ensure fair usage. Rate limit information is returned in response headers.
Rate limit headers
Every response includes these headers:
X-RateLimit-Limit— Maximum requests per windowX-RateLimit-Remaining— Requests remaining in current windowX-RateLimit-Reset— Unix timestamp when the window resets
Exceeding the limit
If you exceed the rate limit, the API returns a 429 Too Many Requests status code:
json
{
"error": {
"code": "rate_limit_exceeded",
"message": "Too many requests. Please retry after 30 seconds."
}
}
Retry strategy
Use exponential backoff when retrying rate-limited requests. Start with a 1-second delay and double it on each retry.