Rate Limits

API keys are rate-limited to 60 requests per minute by default. Every response includes headers showing your current usage.

Rate limit headers

These headers are included in every API response:

HTTP/1.1 200 OK
X-RateLimit-Limit:     60
X-RateLimit-Remaining: 47
X-RateLimit-Reset:     1742860800

Header	Description
`X-RateLimit-Limit`	Maximum requests per minute for your key
`X-RateLimit-Remaining`	Requests remaining in the current minute
`X-RateLimit-Reset`	Unix timestamp when the rate limit window resets

Handling rate limit errors

When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header telling you how many seconds to wait:

HTTP/1.1 429 Too Many Requests
Retry-After: 34

{
  "data": null,
  "meta": null,
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. You are allowed 60 requests per minute."
  }
}

Best practices

Check X-RateLimit-Remaining before making batch requests
Implement exponential backoff when you receive a 429
Use the Retry-After header to know exactly how long to wait
Cache responses where possible to reduce API calls
Contact support if you consistently need higher limits