How It Works
Generous limits: Our rate limits are set well above typical integration needs, allowing you to build robust applications without worrying about hitting limits during normal operation. Fair usage: Rate limiting protects all users by preventing excessive requests that could degrade performance for everyone. We focus on identifying and limiting abusive patterns rather than restricting legitimate usage. Automatic reset: Rate limit windows reset automatically, so temporary spikes in usage won’t permanently impact your integration.When Limits Apply
Rate limits are applied per API key and are designed to catch:- Runaway scripts or infinite loops
- Bulk operations without proper throttling
- Unusually high request volumes that exceed normal business patterns
Rate Limit Exceeded
When limits are exceeded, you’ll receive a429 Too Many Requests
response with a Retry-After
header indicating how long to wait:
Best Practices
Respect Retry-After: When you receive a429
response, use the Retry-After
header value to determine how long to wait before retrying.
Implement exponential backoff: For retries without a Retry-After
header, use exponential backoff with jitter to avoid thundering herd problems.
Batch operations: For bulk operations, process items in batches with delays between requests rather than sending all requests simultaneously.
Cache responses: Cache API responses when appropriate to reduce the number of requests needed.