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
88.79%
30d · 981 calls
Requests
981
30d · weekly, last 12 wks
Response
3.8s
median · 30d
POST

Search

Most used
/v1/run/booking.searchbooking.search
Search Booking.com stays by destination and dates with optional guest and room occupancy and get hotel results (name, price, review score, location) as normalized JSON.
981 /mo
▲3533.3%
88.79%
3839ms p50
1
price$4.86/1k resultsup to $0.102 / request
Octopus

About the Booking.com API

Open an endpoint for its live route, a copy-paste cURL and a sample response.

Measured performance

What the Booking.com API actually does

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

88.8%
of calls succeeded (981 calls)
Succeeded on first lane 88.1%Recovered by failover 0.7%Failed 11.2%
Response time (871 calls)
Typical (p50)
3.8s
Half of requests finish within 3.8s
p99 response time
38.5s
p99 response time: 99% of requests finish within 38.5s

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, 88.8% of Booking.com calls through AnyAPI succeeded, with a median response time of 3.8 seconds across 981 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 and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

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, 88.8% of Booking.com calls through AnyAPI succeeded, with a median response time of 3.8 seconds across 981 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.