Booking Holdings · Rate Limits

Booking Holdings Rate Limits

Rate limits for the Booking.com Demand API v3 (Booking Holdings' primary public developer API). Limits are enforced per partner account on a requests-per-minute basis against any v3 endpoint. Production limits are partner-specific and must be confirmed with the partner's Account Manager; the Sandbox environment enforces a fixed, non-configurable 50 requests-per-minute ceiling. The high-volume cars/search endpoint carries its own documented 3000 requests-per-minute limit. Exceeding a limit returns HTTP 429 and temporarily restricts access (typically for one minute) before the request counter resets.

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

It captures 3 rate-limit definitions, measuring requests_per_minute.

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

Tagged areas include Rate Limiting, Travel, Demand API, and Accommodations.

3 Limits Throttle: 429 Quota: 429
Rate LimitingTravelDemand APIAccommodations

Limits

Demand API v3 requests (production) account
requests_per_minute
partner-specific — contact Account Manager
Applies to any v3 Demand API endpoint. The exact RPM ceiling is configured per partner account and is not publicly published.
Demand API v3 requests (sandbox) account
requests_per_minute · minute
50
Fixed, non-configurable limit in the sandbox environment.
Car rentals search (cars/search) account
requests_per_minute · minute
3000
Endpoint-specific documented limit for the high-volume cars/search operation.

Policies

Exponential backoff on 429
After a 429 response, implement an exponentially increasing delay between retries (e.g. 1s, 2s, 4s, 8s). Access is temporarily restricted for roughly one minute, after which the request counter resets.
Cap retries and total delay
Limit the maximum number of retry attempts and cap the total accumulated delay to avoid unbounded backoff loops; monitor and adjust based on observed throttling.
Per-account scoping
Limits are bound to the partner account (Affiliate ID), not per-IP or per-key. All traffic for an account counts against the same per-minute budget.
Sandbox vs production separation
Develop and test against the sandbox (fixed 50 RPM) before requesting or relying on a production RPM allocation from the Account Manager.

Sources