Rate limiting
Please take note that requests will be rate limited based on an hourly quota. The quota will allow for burst requests of up to 6x the hourly average quota. For example, if your quota is 500 requests / hour, then you cannot exceed 50 requests / minute. The hourly quota is rolling, so if you made 500 requests between 07:30 and 07:45, then you must wait until 08:30 before you can continue to use the API.Handling rate limits
When you exceed your rate limit, you’ll receive a429 Too Many Requests
response. Implement exponential backoff to handle this gracefully:
Best practices for rate limiting
- Implement exponential backoff - Start with a 1-second delay and double it with each retry
- Respect the rolling window - Track your request timing to avoid hitting limits
- Cache responses where appropriate to reduce API calls
- Batch operations when possible instead of making many individual requests
- Monitor for
429
responses and adjust your request frequency accordingly
Understanding your quota
Your specific rate limit depends on your partnership agreement and use case. Common quotas include:- Sandbox environment: Lower limits for testing (typically 100-200 requests/hour)
- Production environment: Higher limits based on your integration needs
- Burst allowance: Up to 6x your hourly average in a short period