Nuitée (LiteAPI) · Rate Limits

Nuitee Rate Limits

LiteAPI applies per-account rate limiting to protect the platform, with sandbox keys subject to tighter limits than live keys. Specific requests-per-second/minute thresholds are not published in the public documentation and are not reconciled in this artifact; the rates search endpoint also exposes a request-level timeout (commonly 6-12 seconds) to bound long-running availability searches.

Nuitee Rate Limits is the machine-readable rate-limit profile for Nuitée (LiteAPI) on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and seconds.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Travel, Hotels, Booking, Distribution, and Hospitality.

2 Limits Throttle: 429
TravelHotelsBookingDistributionHospitalityRate LimitingQuotasThrottling

Limits

Per-Account Request Rate account
requests
see provider documentation
Per-account throttling; sandbox keys are more tightly limited than live keys.
Rates Search Timeout request
seconds
configurable (commonly 6-12s)
The timeout field on POST /hotels/rates bounds availability search duration.

Policies

Sandbox vs. Live
Sandbox API keys carry lower limits and simulated data; live keys raise limits for production traffic.
Backoff Strategy
Clients should implement retries with exponential backoff and honor 429 responses.

Sources