Skip to main content
Rate limits use a token bucket algorithm. Authenticated requests are limited per credential; unauthenticated endpoints are limited per client IP address. The default limits are 1000 requests per minute per credential across the API and 300 requests per minute per credential on any one endpoint.

Rate limit headers

Responses include the current limit state. The sandbox does not enforce rate limits and omits these headers. A 429 response also includes a Retry-After header giving the number of seconds to wait before retrying.

Rate limit response

When you exceed the rate limit, the API returns 429 Too Many Requests:

Handling rate limits

Back off and retry with exponential delay:

Best practices

  • Batch where possible. Fewer large requests beat many small ones.
  • Cache responses that don’t change frequently (e.g., party details, wallet balance).
  • Implement exponential backoff on 429 responses.