/booking/hotels

POST /api/booking/hotels

Price: 5 credits

Get a Booking.com property profile by its URL or country code and alias

How to use it

Get the full Booking.com profile of one property, addressed either by its booking.com URL or by the '{country_code}/{alias}' pair from that URL (for example 'us/millennium-broadway'). Returns the property id, name, description, accommodation type, star rating, guest review score and review count together with the per-category guest scores (cleanliness, location, staff, value and so on), full and short address with city, latitude/longitude and city-center flags, the destination the property belongs to, the hotel brands it belongs to, sustainability, LGBTQ+-friendly and work-friendly flags, spoken languages, the full photo gallery, the categorised amenity list and every room type the property offers. It also returns the topics guests talk about in the reviews of this property, each with the id the 'hotels/reviews' endpoint accepts in 'topic_ids' - request both endpoints in the same language, because the topic ids differ per language. Pass the same hotel reference to the 'hotels/reviews' endpoint for guest reviews, and use 'hotels/search' to find properties with live prices for a stay.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• checkin string nullable — Check-in date (YYYY-MM-DD). Prices and availability are returned for this stay (format: date)
• checkout string nullable — Check-out date (YYYY-MM-DD) (format: date)
• adults integer — Number of adults in the stay (default: 2; min: 1; max: 30)
• children_ages array — Age of each child in the stay, one entry per child (default: []; maxItems: 10)
• rooms integer — Number of rooms requested (default: 1; min: 1; max: 30)
• currency string — Currency prices are converted to (default: "USD"; one of: "AED", "AMD", "ARS", "AUD", "AZN", "BDT", "BGN", "BHD", "BRL", "BYN", "CAD", "CHF", "CLP", "CNY", "COP", "CZK", "DKK", "EGP", "EUR", "FJD", "GBP", "GEL", "GHS", "HKD", "HUF", "IDR", "ILS", "INR", "ISK", "JOD", "JPY", "KGS", "KRW", "KWD", "KZT", "LAK", "LKR", "MAD", "MDL", "MXN", "MYR", "NAD", "NGN", "NOK", "NZD", "OMR", "PHP", "PKR", "PLN", "QAR", "RON", "RSD", "RUB", "SAR", "SEK", "SGD", "THB", "TND", "TRY", "TWD", "UAH", "USD", "UZS", "VND", "XOF", "XPF", "ZAR")
• language string — Language of the returned texts (default: "en-us"; one of: "ar", "bg", "ca", "cs", "da", "de", "el", "en-gb", "en-us", "es", "es-ar", "es-mx", "et", "fi", "fr", "he", "hi", "hr", "hu", "id", "is", "it", "ja", "ko", "lt", "lv", "ms", "nl", "no", "pl", "pt-br", "pt-pt", "ro", "ru", "sk", "sl", "sr", "sv", "th", "tl", "tr", "uk", "vi", "zh-cn", "zh-tw")
• hotel string required — Booking.com property URL, or a '{country_code}/{alias}' pair taken from the property URL (examples: "us/millennium-broadway", "https://www.booking.com/hotel/nl/anantara-ghkrasnapolsky.html"; minLength: 3)

Response

• @type string (default: "BookingHotel")
• id integer required
• alias string required
• country_code string required
• name string required
• url string required
• description string nullable
• accommodation_type string nullable
• accommodation_type_id integer nullable
• star_rating number nullable
• star_rating_symbol string nullable
• review_score number nullable
• review_count integer nullable
• address string nullable
• address_short string nullable
• city string nullable
• destination_id integer nullable
• destination_name string nullable
• destination_type string nullable
• latitude number nullable
• longitude number nullable
• is_city_center boolean nullable
• is_old_town boolean nullable
• currency string nullable
• chain_ids array (default: [])
• brands array (default: [])
  • @type string (default: "BookingHotelBrand")
  • id integer required
  • name string required
• is_travel_proud boolean nullable
• is_sustainable boolean nullable
• is_work_friendly boolean nullable
• is_non_trader boolean nullable
• is_preferred boolean nullable
• allows_children boolean nullable
• facility_count integer nullable
• spoken_languages array (default: [])
• image string nullable
• category_scores array (default: [])
  • @type string (default: "BookingHotelCategoryScore")
  • name string required
  • score number required
  • label string nullable
• review_topics array (default: [])
  • @type string (default: "BookingHotelReviewTopic")
  • id integer required
  • name string required
• photos array (default: [])
  • @type string (default: "BookingHotelPhoto")
  • id integer required
  • image string required
  • alt_text string nullable
• facilities array (default: [])
  • @type string (default: "BookingHotelFacility")
  • id integer required
  • slug string nullable
  • group_id integer nullable
  • group string nullable
  • name string nullable
• rooms array (default: [])
  • @type string (default: "BookingHotelRoom")
  • id integer required
  • name string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Property not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.