Rate Limiting

Swaps is committed to providing a stable and secure platform for all users. Accordingly, We continuously monitor API traffic to detect any patterns that could impact network stability. Rate limits ensure that no single client overloads the system, maintaining stability for all users.

If you encounter HTTP status code 429, it means the rate limit has been temporarily exceeded.

The rate limit for all partners is capped at 500 requests per minute across all endpoints, tied to a single IP address.

If your testing or production operations frequently hit rate limits, please contact your Customer Success Manager or Swaps Support.

Best Practices

Monitor rate limit errors: If you receive multiple 429 errors per day, it may indicate an issue with your solution architecture. Review how you can reduce the number of API calls. Consider what change in the solution architecture can reduce the number of API calls you are making.

Retry API calls reasonably: If you are making periodic API calls, avoid immediate retries. Instead, rely on the next scheduled call. Use an exponential backoff strategy if retries are necessary. Additionally, an exponential backoff retry strategy is recommended when it is required to try again.

Use Webhooks: Utilizing push notifications and webhooks can significantly reduce the number of API calls required for standard operations, lowering system load. It will reduce the load on both your internal system and the Banxa backed.

Call endpoints only when required: Avoid frequent polling of the Get Quotes or Get Orders endpoints. Instead, call these endpoints only when the user actively requests a quote or order.

Use batch operations: To reconcile orders, consider using batch operations instead of multiple parallel processes, which can reduce the number of API calls.