Rate Limit Overview
API requests are rate limited to ensure fair usage and system stability. Limits are enforced at two levels: per IP address and per user account.Current Limits
When either limit is exceeded, the API returns HTTP status
429 Too Many Requests with a Retry-After header. The per-account limit is set by your access group, so it may differ from the default shown above — contact support for higher limits.Rate Limit Exceeded Response
When a rate limit is exceeded, the API responds with:Handling Rate Limits
Implement Exponential Backoff
Best Practices
- Implement exponential backoff with jitter for retries
- Cache responses when possible to reduce redundant requests
- Batch operations where supported (e.g. batch document removal)
- Implement client-side request queuing to smooth out traffic spikes
- Monitor request volume and log
429responses for observability
Storage and Resource Quotas
Storage allowances are tied to your subscription. Check Billing in the console for your current plan, or contact support if you expect unusually large uploads.
Requesting Higher Limits
To request higher rate limits, contact support with:- Current usage patterns and peak request volume
- Expected future usage
- Use case description
Next Steps
API Overview
Return to API overview
Error Handling
Handle rate limit errors