Banxa applies API rate limits to ensure platform stability and fairness across all clients. Requests are continuously monitored, and excessive traffic will be throttled.
- Limit: 500 requests per minute per IP address (applies across all endpoints).
- Error code: If limits are exceeded, the API returns an HTTP
429 Too Many Requestsresponse.
If you consistently encounter rate limiting under normal test or production usage, contact your Customer Success Manager or Banxa Support.
Monitor for 429 errors
- Occasional 429s are expected.
- If you see them repeatedly, review your architecture and API usage.
Retry responsibly
- Avoid blind retries.
- Use exponential backoff when retries are required.
- For periodic checks, let the next scheduled call handle it instead of retrying.
Use webhooks wherever possible
- Webhooks push updates to your system.
- This avoids unnecessary polling and reduces load on both Banxa and your infrastructure.
Call endpoints only when needed
- Example: Call
GET /priceonly when a user is actively viewing a quote, rather than polling continuously.
Batch operations
- For reconciliation or reporting, use batch processes instead of sending many parallel calls.