Booking Com Rate Limits
Booking.com publishes rate limiting as prose in the Demand API development guide. Two limits are stated as concrete numbers - sandbox 50 requests per minute, and cars/search 3000 requests per minute - while the production per-account limit is deliberately unpublished and set per partner by an Account Manager. Only the Reconciliation API declares a runtime signal in its contract: a Retry-After header on 429.
Booking Com Rate Limits is the machine-readable rate-limit profile for Booking.com on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions.
Limit state is signalled in the published, request_quota_headers, retryAfter, and retryAfter_scope response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and throttled_label.
Tagged areas include Rate Limiting, Travel, and Hospitality.
publishedrequest_quota_headersretryAfterretryAfter_scope
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.