Rate limits
Overview
The API enforces rate limits to ensure fair usage and system stability.
| Limit | Value |
|---|---|
| Requests per minute | 500 per API key |
| Request timeout | 60 seconds |
Response headers
Every response includes rate limit headers:
| Header | Description | Example |
|---|---|---|
X-RateLimit-Remaining | Requests remaining in the current window | 487 |
X-RateLimit-Reset | When the rate limit window resets (RFC 1123) | Sun, 02 Mar 2026 15:30:45 UTC |
When a request is rate limited (HTTP 429), the response also includes:
| Header | Description |
|---|---|
Retry-After | When to retry the request (RFC 1123) |
Handling rate limits
When you receive a 429 Too Many Requests response:
- Read the
Retry-Afterheader to determine when to retry - Back off and retry after the indicated time
- Do not retry immediately—repeated 429s will not reset the window
{
"title": "Too many requests",
"id": "too_many_requests",
"detail": "Too many requests",
"status": 429
}Best practices
- Batch related data into a single query. GraphQL lets you request multiple fields in one request—use this to reduce your request count.
- Monitor
X-RateLimit-Remaining. Proactively slow down before hitting the limit rather than reacting to 429s.
Need help?
If you run into any issues or have questions, please reach out to our Support Engineering team by opening a ticket via the Dashboard: https://dashboard.meter.com/support