Rate Limits

The API uses rate limits to ensure fair usage and maintain service stability.

Rate limit information is returned with every response through HTTP headers.

Response Headers

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed within the current window
`X-RateLimit-Remaining`	Requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp in milliseconds when the limit resets

If a route-specific rate limit is exceeded, the API returns:

429 Too Many Requests

Example response:

{
  "message": "You are being rate limited",
  "retry_after": 2500
}

Field	Description
`message`	Error message
`retry_after`	Number of milliseconds before another request may be made

In addition to route-specific limits, all API tokens are subject to a global limit of:

20 requests per second

When the global limit is exceeded, the API returns:

{
  "message": "You are being rate limited",
  "global": true
}

Field	Description
`message`	Error message
`global`	Indicates that the global rate limit was exceeded