APIs & Integrations
Rate Limits
Understand Optra API throttling policies and how to handle rate limit responses gracefully.
Rate limits protect the platform and ensure fair usage across all integrations. Limits are applied per API key, per minute.
Default Limits
| Tier | Requests / min | Burst |
|---|---|---|
| Standard | 120 | 20 |
| Professional | 600 | 100 |
| Enterprise | Custom | Custom |
Rate Limit Headers
Every response includes headers so you can track your current usage:
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1747058460 # Unix timestamp when the window resets
Handling 429 Responses
When you exceed your limit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait:
HTTP/1.1 429 Too Many Requests
Retry-After: 23
Content-Type: application/json
{
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Too many requests. Retry after 23 seconds."
}
}
Best Practices
- Implement exponential backoff with jitter when retrying after a 429.
- Cache responses where possible to reduce redundant calls.
- Use bulk endpoints (e.g.
GET /deviceswith filters) rather than looping over individual resource IDs. - Contact support if your integration consistently requires higher limits.