Hotelbeds · Rate Limits

Hotelbeds Rate Limits

Hotelbeds (HBX Group) APItude enforces per-API-key quotas that differ sharply between the evaluation and production environments. Evaluation keys are capped at a small number of requests per day; exceeding the quota returns HTTP 403. Production limits (queries per second / per day, plus availability and booking throughput) are raised during certification and set per partner under contract. Specific production values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests.

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

Tagged areas include Travel, Hotels, Bedbank, Accommodation, and Booking.

4 Limits Throttle: 403
TravelHotelsBedbankAccommodationBookingRate LimitingQuotasThrottling

Limits

Evaluation Requests Per Day api-key
requests
50
Evaluation keys are limited to roughly 50 requests per day; exceeding the quota returns HTTP 403.
Production Queries Per Second (QPS) api-key
requests
see partner agreement
Raised through certification; negotiated per partner and product suite.
Production Requests Per Day api-key
requests
see partner agreement
Daily ceiling set per commercial agreement.
Availability Throughput api-key
requests
see partner agreement
Availability search throughput is governed separately from booking calls.

Policies

Certification Gating
Quotas increase only after the integration passes Hotelbeds certification and a commercial agreement is in place.
Backoff Strategy
Clients should implement exponential backoff with jitter and avoid hammering availability endpoints; cache static content via the Content API.

Sources