Rate Limiting

Banxa strives to offer a stable and secure platform at all times. Accordingly, API call traffic is continuously monitored to identify patterns that might affect the network. API rate limits assure that a single client cannot overload the system for other clients.

Error responses with HTTP status code 429 indicate that rate limits have been temporarily exceeded.

For all partners, the rate limit is capped at 500 per minute for all endpoints combined which is tied to a single IP.

If normal test or production operations repeatedly result in rate limiting, you can contact your Customer Success Manager or Banxa Support.

Best Practices

Monitor rate limit errors - If you receive 429 errors more than a handful of times a day - something is probably not done properly. Consider what change in the solution architecture can reduce the number of API calls you are making.

Retry API calls reasonably - If you are calling an API periodically - consider not retrying and relying on the next time it will be checked. Additionally, an exponential backoff retry strategy is recommended when it is required to try again.

Use Webhooks to monitor applications - Using push notifications and webhooks will dramatically reduce the number of API calls you need to make for standard operations. It will reduce the load on both your internal system and the Banxa backed.

Call endpoints only when required - Rather than calling the Get Quotes or Get Order(s) endpoint at high frequency, we recommend that you only call this endpoint when a customer has selected to view a Banxa quote or order.

Use batch operations - If you need to reconcile orders, rather than using many parallel processes, batch operations can reduce the number of calls you need to make.