Skip to Content

Rate Limits

API requests are subject to rate limiting to ensure service stability.

Limits

EnvironmentRate Limit
Sandbox100 requests/minute
Production1000 requests/minute

Response Headers

Rate limit information is included in response headers:

X-RateLimit-Limit: 1000 X-RateLimit-Remaining: 999 X-RateLimit-Reset: 1678886400
HeaderDescription
X-RateLimit-LimitMaximum requests allowed per minute
X-RateLimit-RemainingRemaining requests in current window
X-RateLimit-ResetUnix 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

  1. Implement exponential backoff - When you receive a 429, wait before retrying
  2. Respect headers - Use X-RateLimit-Remaining to avoid hitting limits
  3. Cache responses - Reduce API calls by caching data where appropriate
  4. Batch requests - Combine multiple operations when possible

Tip: Use exponential backoff and respect the X-RateLimit-Reset header when retrying.

Last updated