Rate Limits
API requests are subject to rate limiting to ensure service stability.
Limits
| Environment | Rate Limit |
|---|---|
| Sandbox | 100 requests/minute |
| Production | 1000 requests/minute |
Response Headers
Rate limit information is included in response headers:
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 999
X-RateLimit-Reset: 1678886400| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per minute |
X-RateLimit-Remaining | Remaining requests in current window |
X-RateLimit-Reset | Unix timestamp when the limit resets |
Exceeded Limits
When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
{
"error": {
"code": "rate_limit_exceeded",
"message": "Rate limit exceeded. Please try again later.",
"retry_after": 60
}
}Best Practices
- Implement exponential backoff - When you receive a 429, wait before retrying
- Respect headers - Use
X-RateLimit-Remainingto avoid hitting limits - Cache responses - Reduce API calls by caching data where appropriate
- Batch requests - Combine multiple operations when possible
Tip: Use exponential backoff and respect the
X-RateLimit-Resetheader when retrying.
Last updated