Limites de taux API
Comprenez les limites de taux par plan et comment gérer les réponses limitées.
Rate Limit Overview
API rate limits protect the platform and ensure fair usage. Limits are applied per API key and vary by plan.
Limits by Plan
| Plan | Requests / Hour | Requests / Day |
|---|---|---|
| Essential | 100 | 1,000 |
| Professional | 500 | 5,000 |
| Agencies | 2,000 | 20,000 |
| Enterprise | Custom | Custom |
Rate Limit Headers
Every API response includes rate limit information in the headers:
X-RateLimit-Limit: 500 X-RateLimit-Remaining: 487 X-RateLimit-Reset: 1705312800
X-RateLimit-Limit: Maximum requests per hourX-RateLimit-Remaining: Requests remaining in the current windowX-RateLimit-Reset: Unix timestamp when the limit resets
When You Exceed the Limit
If you exceed your rate limit, the API returns a 429 Too Many Requests response:
{
"error": "rate_limit_exceeded",
"message": "You have exceeded your rate limit. Please retry after 2025-01-15T11:00:00Z.",
"retry_after": 120
}Best Practices
- Implement exponential backoff when you receive a 429
- Cache API responses where possible
- Use webhooks instead of polling for real-time updates
- Monitor your rate limit headers to stay within bounds