Rate limit response
When you exceed the rate limit, the API returns429 Too Many Requests:
Handling rate limits
Back off and retry with exponential delay:Best practices
- Batch where possible. Fewer large requests beat many small ones.
- Cache responses that don’t change frequently (e.g., party details, wallet balance).
- Implement exponential backoff on
429responses.
Related
- Error Handling — Error response format
- Idempotency — Safe retries after rate limiting