Rate Limiting

API rate limits protect the platform from being overloaded by a single client, keeping the system stable and secure for everyone.

If you exceed your rate limit, you'll receive an HTTP 429 error response.

Rate limits are set at the API user level. If you're consistently hitting 429 errors, you can:

• Slow down the rate of your requests

• Spread requests out across minute intervals

• Spread requests across multiple API users

Common mistakes that lead to rate limit errors

• Not monitoring for 429 errors on the client

• Retrying failed calls blindly, without checking the error type

• Running too many parallel processes for batch operations

• Polling for transaction updates instead of using webhooks

• Generating a new token for every call instead of reusing it

Note: A 429 response means your rate limit has been temporarily exceeded, it isn't a permanent block. Slow the request rate and retry.