Booking.com API by APISH

Get public Booking.com data as clean, consistent JSON: one Booking.com hotel, booking.com hotel reviews, booking.com hotel search. 3 endpoints, one response shape, numbers parsed, absolute URLs.

How to use

1. Pick an Endpoint. Each option shows what it returns and its price in credits.
2. Enter its Parameters as JSON, for example {"url":"https://www.booking.com/hotel/us/the-plaza.html"}. All parameters are listed below.
3. Run. Each call becomes one row in the dataset. Use Batch to run the same endpoint for many inputs and Pages per input to follow pagination.

Pricing

Pay per event: you pay per APISH credit the call used. The price of each endpoint is in the table below. Calls that fail on our side (server errors, timeouts, blocks) are free.

Endpoints

Endpoint	Returns	Required parameters	Credits
/booking/v1/hotel	One Booking.com hotel	url	4
/booking/v1/hotel-reviews	Booking.com hotel reviews	url	1
/booking/v1/search	Booking.com hotel search	q	1

Output

Each dataset row has endpoint, params, status, credits_used and the endpoint's data. Add "raw": 1 to the parameters to also get the site's original record, or "fields": "a,b.c" to return only the fields you need.

Endpoint details

One Booking.com hotel

Endpoint /booking/v1/hotel · 4 credits per successful call.

A Booking.com hotel: description, address, coordinates, rating, facilities, rooms, photos, policies, Q&A and featured reviews. With checkin/checkout, the page for those dates is read: room_cards lists its rooms (size, occupancy, beds, availability blocks; prices when Booking includes them in the page) and room_offers the classic availability table when the page has one. Every response includes credits_used: the credits this call cost.

Parameters:

• url (required): Booking hotel page URL.
• checkin: Check-in date (YYYY-MM-DD). With checkout, the response includes room_offers (rooms, prices, conditions) for those dates.
• checkout: Check-out date (YYYY-MM-DD).
• adults: Adults (default 2).
• children: Children ages, comma-separated (e.g. 5,9).
• rooms: Rooms (default 1).
• currency: Price currency (ISO code, e.g. EUR).

Example parameters: {"url":"https://www.booking.com/hotel/us/the-plaza.html"}

Booking.com hotel reviews

Endpoint /booking/v1/hotel-reviews · 1 credit per successful call.

Every review of a Booking.com hotel, 25 per page, from Booking's own review list: score, title, liked/disliked text, language, date, guest (name, country, traveler type), stay (room, dates, nights), the hotel's reply and photos. Sort and filter like the site; available_filters lists each filter's values with counts. Pages after the first are one small request. Every response includes credits_used: the credits this call cost.

Parameters:

• url (required): Booking hotel page URL.
• sort — one of most_relevant, newest, oldest, highest, lowest: Order: most_relevant (default), newest, oldest, highest, lowest.
• offset: Reviews to skip; pass next_offset back. 25 per page.
• limit: Reviews per page (1-25, default 25).
• q: Text search inside reviews.
• customer_type: families, couples, groups, solo, business (or a value from available_filters.customer_type).
• languages: Review languages, comma-separated (e.g. en,fr); values in available_filters.languages.
• time_of_year: A value from available_filters.time_of_year (e.g. MAR_MAY).
• score: A value from available_filters.score (score range).
• topics: Topic ids, comma-separated, from available_filters.topics.
• room_type: A room type id from available_filters.room_type.
• details: true: also read the hotel page on page 1 (featured reviews, Q&A, subscores). Otherwise the summary comes from cache.

Example parameters: {"url":"https://www.booking.com/hotel/us/the-plaza.html"}

Booking.com hotel search

Endpoint /booking/v1/search · 1 credit per successful call.

Pagination: result offset. Pass next_offset from the previous response.

Parameters:

• q (required)
• offset: Result offset. Pass next_offset from the previous response.
• adults: Adults (default 2).
• rooms: Rooms (default 1).
• currency: Price currency, e.g. USD.

Example parameters: {"q":"Paris"}

Support

Questions, bugs or a missing field? Open an issue in this Actor's Issues tab and we will reply there.

Public data only: nothing behind a login. You are responsible for how you use the data you collect.