/booking/destinations

POST /api/booking/destinations

Price: 1 credit

Get a Booking.com destination with the neighborhoods, landmarks, brands and places inside it

How to use it

Get everything a Booking.com destination can be narrowed down by, addressed by the destination id and type from the 'destinations/search' endpoint. Returns how many properties the destination holds and its neighborhoods, nearby landmarks, hotel brands, cities and top sub-destinations - each with its own id, name and property count. Feed those ids into the matching 'hotels/search' fields (district_ids, landmark_ids, brand_ids, city_ids, sub_destination_ids) to search one part of the destination; cities and sub-destinations are returned for regions and countries, neighborhoods and landmarks for cities.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• destination_id integer required — Booking.com destination id, as returned by the 'destinations/search' endpoint
• destination_type string required — Type of the destination id, as returned by the 'destinations/search' endpoint (one of: "CITY", "REGION", "DISTRICT", "COUNTRY", "AIRPORT", "LANDMARK", "HOTEL", "THEME", "LATLONG")
• 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")

Response

• @type string (default: "BookingDestinationProfile")
• id integer required
• destination_type string required
• property_count integer nullable
• neighborhoods array (default: [])
  • @type string (default: "BookingDestinationFacet")
  • id integer required
  • name string required
  • property_count integer nullable
• landmarks array (default: [])
  • @type string (default: "BookingDestinationFacet")
  • id integer required
  • name string required
  • property_count integer nullable
• brands array (default: [])
  • @type string (default: "BookingDestinationFacet")
  • id integer required
  • name string required
  • property_count integer nullable
• cities array (default: [])
  • @type string (default: "BookingDestinationFacet")
  • id integer required
  • name string required
  • property_count integer nullable
• sub_destinations array (default: [])
  • @type string (default: "BookingDestinationFacet")
  • id integer required
  • name string required
  • property_count integer 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 — Destination 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.