To ensure fair use of resources, Nuitee Connect enforces rate limits on API requests. If you exceed the rate limits, you will receive a "429 Too Many Requests" response.
This page is the authoritative source for default Nuitee Connect API rate limits. Other guides (including Performance, Reliability & Rate Limiting) should point here instead of restating different numbers.
Scope: Limits apply per API key (sandbox key and production key are counted separately). They apply across API endpoints that use that key.
Default limits:
- Sandbox API keys: 5 requests per second
- Production API keys: 250 requests per second
Higher limits may be granted by contract. Contact support if you need a custom limit.
When exceeded:
- HTTP 429 Too Many Requests
- Typical body:
{
"error": {
"code": 429,
"message": "Too many requests. Please try again later."
}
}Honor a Retry-After header when the server sends one. Otherwise use exponential backoff with jitter (see the Performance guide).
Best Practices:
- Implement exponential backoff when retrying 429 responses.
- Monitor usage in the Nuitee Connect dashboard.
- Do not treat a search-body
limitfield (hotel rates) as this account throttle.