Our API implements multiple layers of rate limiting to ensure fair usage and system stability:
Infrastructure Level
- 1,000 requests per IP per 60 seconds - Global rate limit applied at the infrastructure level
Application Level Rate Limits
Different endpoint types have specific rate limits based on their resource requirements:
| Endpoint Type | Limit | Time Window | Description |
|---|---|---|---|
| Public write API | 120 requests | 1 minute | Public-facing endpoints |
| Standard | 1,000 requests | 1 minute | General API endpoints and public-facing read endpoints |
| Heavy Operations | 10 requests | 1 minute | Resource-intensive operations and auth endpoints |
| File Upload | 20 requests | 5 minutes | File upload operations |
| Polling | 30 requests | 1 minute | Real-time polling endpoints |
Rate Limit Headers
When you make requests, check these response headers to monitor your usage:
- X-RateLimit-Limit - Your rate limit ceiling for the current window
- X-RateLimit-Remaining - Number of requests remaining in current window
- X-RateLimit-Reset - UTC epoch seconds when the rate limit resets
Handling Rate Limits
If you exceed a rate limit, you'll receive a 429 Too Many Requests response. Implement
exponential backoff in your client to handle these gracefully.