Rate Limiting
Rate limit policies and response headers for the Mesta API.
Rate Limiting
The Mesta API enforces rate limits to ensure fair usage and system stability.
Rate Limit Headers
Rate limit information is included in the response headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed in the window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Rate Limit Exceeded
When you exceed the rate limit, the API returns a 429 Too Many Requests response:
{
"statusCode": 429,
"message": "Rate limit exceeded. Please retry after the reset time.",
"error": "Too Many Requests"
}Best Practices
- Monitor rate limit headers in every response to track your usage.
- Implement exponential backoff when receiving 429 responses.
- Cache responses where possible to reduce the number of API calls.
- Use webhooks instead of polling for real-time updates.
- Batch operations where possible to minimize the number of requests.
Need Higher Limits?
If your integration requires higher rate limits, contact our Support Team to discuss your needs.
Updated 8 days ago