Catalog

Booking.com API

Booking.com data through one normalized API - per-request USD pricing and no subscriptions.

Endpoints1Providers1From · search$4.86/1k results · OctopusFull breakdownRead docs
Uptime
100.00%
30d · 6 calls
Requests
6
30d · weekly, last 12 wks
Response
3.8s
median · 30d

Measured performance

What the Booking.com API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (6 calls)
Succeeded on first lane 100.0%
Response time (6 calls)
Typical (p50)
3.8s
Half of requests finish within 3.8s
p99 response time
6.1s
p99 response time: 99% of requests finish within 6.1s

FAQ

About the Booking.com API

The AnyAPI Booking.com API returns Booking.com data as normalized JSON across 1 endpoint: search. You call one endpoint per job with a single key, and AnyAPI returns one normalized schema whichever source serves it. Pricing is in US dollars, $4.86 per 1,000 results, and never more than $0.102 for a single request, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Booking.com calls through AnyAPI succeeded, with a median response time of 3.8 seconds across 6 measured calls.

Pricing is in US dollars, $4.86 per 1,000 results, and never more than $0.102 for a single request, with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

One endpoint: search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Booking.com endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Booking.com calls through AnyAPI succeeded, with a median response time of 3.8 seconds across 6 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.