Rate Limiting
To ensure fair usage and system stability, the ClarityCall API implements rate limiting on all endpoints.
Rate Limits
| Endpoint Category | Limit | Window |
|---|---|---|
| Standard endpoints | 100 requests | Per minute |
| Upload endpoints | 10 requests | Per minute |
| AI/Chat endpoints | 20 requests | Per minute |
Rate Limit Headers
All API responses include headers to help you track your rate limit status:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the current window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Handling Rate Limits
When you exceed the rate limit, you'll receive a 429 Too Many Requests response.
The response includes a Retry-After header indicating how long to wait before retrying.
Best Practices
- Implement exponential backoff when retrying failed requests
- Cache responses where possible to reduce API calls
- Use webhooks instead of polling for real-time updates
- Batch operations where the API supports it
Need Higher Limits?
If your use case requires higher rate limits, contact us at api@claritycall.app to discuss enterprise options.