Rate Limiting
The Partner API enforces a rate limit of 1000 requests per minute per API key. Requests are counted across all endpoints and reset on a rolling 60-second window.
When you exceed the limit the API responds with HTTP 429 Too Many Requests. Every response (successful or not) includes headers describing your current usage so you can pace your requests:
| Header | Description |
|---|---|
| X-RateLimit-Limit | Maximum requests permitted in the current window (typically 1000). |
| X-RateLimit-Remaining | Requests remaining in the current window. |
| X-RateLimit-Reset | UTC timestamp (ISO 8601) at which the current window resets. |
| Retry-After | Present on 429 responses only. Seconds to wait before retrying. |
Recommendations for partners:
- Batch and cache responses where practical (e.g. trip and departure lookups).
- Implement exponential backoff on 429 and 5xx responses.
- Monitor the X-RateLimit-Remaining header and slow request cadence as it approaches zero.
- Contact your Intrepid partner manager if your integration legitimately requires a higher throughput