Rate Limits
Phase 2
This documentation is a preview. The API is currently in development.
Default Limits
| Plan | Requests per Minute | Requests per Day |
|---|---|---|
| Standard | 60 | 10,000 |
| Enterprise | 300 | 100,000 |
Rate Limit Headers
Every API response includes rate limit information in the headers:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1679000000
| 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 rate limit resets. |
Exceeding Limits
If you exceed the rate limit, you will receive a 429 Too Many Requests response:
{
"success": false,
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Rate limit exceeded. Retry after 30 seconds.",
"retry_after": 30
}
}
Best Practices
- Cache responses where data does not change frequently (e.g., location details, hours of operation).
- Use webhooks for real-time data instead of polling the API.
- Batch operations where the API supports them to reduce the total number of requests.
- Implement exponential backoff when retrying after a rate limit error.
- Monitor your usage through the rate limit headers included in every response.
Next Steps
- API Overview -- Review the full list of planned endpoints.
- Authentication -- Learn about API key management.