Limits

This page covers the API rate limits (requests per minute). For per-transaction amount limits by method, see Payment method limits.

Default rate limits

If you exceed these limits, the API responds with HTTP 429 Too Many Requests.

Rate limit headers

The API includes these headers in every response so you can track your status:

Handling the 429 error

When you exceed the limit, the API returns HTTP 429 with a body indicating when to retry:

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests",
    "retry_after": 60
  }
}

The retry_after field indicates the seconds to wait before retrying.

Best practices

• Wait at least the retry_after seconds before retrying after a 429.
• Implement exponential backoff for server errors or rate limits.
• Cache responses to avoid repeating requests for the same information (especially GET).
• Control concurrency so parallel requests don't exceed the limit.

Next steps