Rate limits

Rate Limiting Overview

For polling operations (checking request status), leave at least 1 second between requests
When a rate limit response occurs, implement exponential backoff
Check response headers to monitor rate limit information

The API returns the following headers to provide information about rate limits:

Header	Description
`X-RateLimit-Limit`	Maximum number of requests in a given period
`X-RateLimit-Remaining`	Number of requests remaining in the current period
`X-RateLimit-Reset`	Unix timestamp when the current rate limit window resets

When the rate limit is exceeded, an HTTP 429 Too Many Requests response is returned:

{
  "statusCode": 429,
  "errorId": "rate_limit_exceeded",
  "message": "Too Many Requests"
}

Use the Retry-After value in the response header to determine retry time
Implement an exponential backoff algorithm to gradually increase retry intervals
If necessary, review how you use the API