Booking.com · Rate Limits

Bookingcom Rate Limits

Booking.com does not publish per-second or per-minute API rate limits on its public developer site; rate-limit terms are communicated to certified Connectivity and Demand API partners under contract. Consumers should expect HTTP 429 throttling on overuse and apply exponential backoff. Reconcile against the partner-specific technical specification once available.

Bookingcom Rate Limits is the machine-readable rate-limit profile for Booking.com on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring varies.

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

Tagged areas include Accommodations, Affiliates, Connectivity, Hospitality, and Hotels.

2 Limits Throttle: 429
AccommodationsAffiliatesConnectivityHospitalityHotelsReservationsTravelRate Limiting

Limits

Demand API request rate partner
varies
see partner technical specification
Per-partner negotiated; not publicly published.
Connectivity API request rate partner
varies
see partner technical specification
Per-partner negotiated; not publicly published.

Policies

Backoff Strategy
Apply exponential backoff with jitter on 429 and 5xx responses; honor Retry-After when present.
Partner-Bound Quotas
Effective request budget is set in the partner contract and onboarding spec, not via a public tier page.
Fair Use
Sustained traffic that materially impacts shared infrastructure is reviewed and may trigger throttling regardless of contract.

Sources