Getting started

Rate limiting

Each service token is subject to a per-minute request quota. The default is 600 requests per minute per token. Contact your account manager if you need a higher limit.

Response headers

Every response includes the current rate limit state:

  • X-RateLimit-Limit — the maximum number of requests allowed in the current window
  • X-RateLimit-Remaining — requests remaining in the current window
  • X-RateLimit-Reset — Unix timestamp when the window resets
response headers
HTTP/1.1 200 OK
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 437
X-RateLimit-Reset: 1718800000

429 response

When the limit is exceeded the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying.

HTTP 429
{
  "status": 429,
  "message": "Too Many Requests",
  "details": "Rate limit exceeded. Retry after 12 seconds."
}

Best practices

  • Watch X-RateLimit-Remaining and slow down before you hit zero.
  • Use exponential backoff with jitter when retrying after a 429.
  • Batch reads via pagination rather than firing many parallel requests.
  • Cache responses where possible — most read endpoints support standard HTTP caching.