Booking.com Hotel & Travel Data APIs

Search accommodation using a known destination query such as city:20088325 for New York, with explicit checkin_date, checkout_date, adults, rooms, and currency_code. The observed success body contains status=true, message=Success, currentPage, resultsPerPage, totalResultCount, and a data array. Hotel rows include id, name, ufi, countryCode, checkinDate, checkoutDate, reviewScore, coordinates, blockIds, and priceBreakdown.grossPrice with currency and value. A request for page_size=10 returned 20 rows; use returned pagination metadata instead of assuming that setting is enforced. Destination autocomplete is unavailable, so retain a known query rather than depending on name discovery. Prices and reported match counts can change.

Search with a user-confirmed location string plus explicit check-in/check-out dates, guests, rooms, and currency. Optional price bounds, category identifiers, bed count, page, and sort refine the documented request. This text-oriented route was not live-validated and is not a proven replacement for unavailable accommodation autocomplete. Verify returned property geography and actual response fields before displaying matches for ambiguous location names.

Search with an existing dest_id and its matching dest_type, plus stay dates, guest counts, rooms, and currency. The documented New York pair is dest_id=20088325 with dest_type=city; it is not the prefixed query used by stays-search. Accommodation autocomplete is unavailable, so obtain a known destination pair independently. This destination-ID route was not live-validated. Inspect its response and property IDs before handing a selected hotel to detail operations.

Search around latitude and longitude with a radius measured in kilometers. The documented radius defaults to 10 and ranges from 10 to 500. Add explicit stay dates, adults, child ages, rooms, and currency; optional budget/category controls refine the query. This radial-search response was not live-validated, so verify returned geography and distance behavior before treating the circle as a strict result boundary.

Search a viewport with ne_lat, ne_lon, sw_lat, and sw_lon plus a consistent stay and occupancy. Supply checkin_date and checkout_date explicitly: the documented omitted-date defaults are inconsistent for this route and must not define a reproducible stay. Optional price bounds, categories_filter, page, and sort refine the request. The bounding-area response and geographic edge behavior were not live-validated.

Request filter metadata for a known dest_id/dest_type and the same dates, occupancy, rooms, and currency as the hotel search. Documentation identifies data.filters.options.genericId for category tokens and price sliderOptions.min/max for budget controls. These are documented handoffs, not live-validated response fields. Leave categories_filter blank initially, inspect the returned options, then reuse only identifiers supported by that destination and stay.

Retrieve documented ordering choices for a known dest_id/dest_type and search context. Documentation points to option names in the response for hotel sort values; it lists price, bayesian_review_score, distance, property-class orderings, and other choices. This sorter route was not live-validated. Render only returned options applicable to the current hotel destination workflow, not tokens copied from flight or property-list sorting.

Retrieve a known numeric hotel_id with optional stay dates, adult count, child ages, room count, currency, and language. Hotel 180769 returned Hyatt Grand Central New York with status=true and message=Success. Observed data includes hotel_id, hotel_name, city_trans, countrycode, url, address, arrival_date, departure_date, currency_code, rooms, facilities_block.facilities, block, and composite_price_breakdown. Room blocks include block_id, occupancy, price breakdowns, and cancellation/prepayment policy text. Omitted dates used the documented current date through four days later; set both dates for reproducible comparisons. A nonexistent ID returned HTTP 200 with status=false, message=NO DATA!, status_code=400, and data=null. Check business status before reading hotel fields; NO DATA alone does not establish why another request failed.

Request room options for a known hotel_id and carry checkin_date, checkout_date, adults, children_age, rooms, and currency_code from the selected stay. Optional units and temperature_unit control documented display preferences. This dedicated room-list route was not live-validated; do not assume it has the same schema as the tested hotel-details response. Inspect returned room identities, amounts, occupancy, and conditions before building a room selector. Retrieval does not hold or purchase a room.

Inspect the documented calendar for a numeric hotel_id, optionally starting at checkin_date and supplying rooms, children_age, currency_code, and language_code. This endpoint does not expose an adults or checkout_date input; do not add either by analogy with hotel details. Its live response, calendar horizon, day status fields, and price coverage have not been validated. Treat returned dates as candidates for a subsequent date-specific hotel or room read, not as held inventory.

Retrieve descriptive hotel content for hotel_id, optionally selecting currency_code and language_code. This description-only endpoint was not live-validated; inspect returned text structure, language, and omissions before publishing it. Descriptive content is separate from date-dependent room rates, and its reuse remains subject to applicable content rights.

Inspect documented facilities for hotel_id with optional checkin_date, checkout_date, currency_code, and language_code. Omitted dates are documented as the current date through four days later; send explicit dates to align with a selected stay. This dedicated facilities response was not live-validated and should not be assumed to match facilities_block in the tested hotel-details response.

Request photo information for a numeric hotel_id. No date, currency, language, or pagination input is exposed on this endpoint. The dedicated photo response was not live-validated, so image URL fields, sizes, count, and reuse permissions are not guaranteed. Inspect actual returned references and content rights before building or caching a hotel gallery.

Retrieve documented property-level policy information for hotel_id with optional currency_code and language_code. This response was not live-validated, so policy sections, completeness, and exact field names must be inspected. Keep general property rules separate from cancellation and prepayment conditions tied to a specific dated room block; this endpoint has no stay-date or room-block inputs.

Inspect documented surroundings information for hotel_id with optional language_code and currency_code. The surroundings response was not live-validated; validate actual categories, place references, and any distance labels before displaying them. This is a property-context read, not a route planner, live-transit feed, or guaranteed walking-time calculation.

Read documented property Q&A for hotel_id with optional language_code and currency_code. This GET operation has no question text or submission input and cannot post a new question. Its live response was not validated; inspect the actual question/answer structure, coverage, and rights before using it in a traveler-support knowledge base.

Make a read-only follow-up for hotel_id and one or more comma-separated blockIds obtained from data.block[].block_id in hotel details. Preserve the original dates, adults, child ages, rooms, and currency. The process-information response was not live-validated, so no checkout fields or confirmation identifiers are promised. Despite the operation name, this GET request does not create, pay for, or confirm a hotel reservation.

Request review pages for hotel_id using page, page_size, and sort, with optional traveler-type, review-language, time-of-year, and topic filters. Documentation describes comma-separated filter values and defaults of page=1, page_size=25, and sort_most_relevant. Discover supported filter and sorter identifiers through the matching review-metadata operations. This review response was not live-validated; review row fields, totals, and paging behavior must be inspected rather than inferred from hotel search.

Retrieve documented review-score information for a numeric hotel_id with optional currency_code and language_code. This score-specific response was not live-validated; inspect its category names, numerical scales, sample counts, and missing fields before making property comparisons. Timestamp collected snapshots yourself rather than describing the endpoint as a native historical-score feed.

Inspect the sparsely documented review-feature endpoint for hotel_id with optional language_code and currency_code. No live response or detailed feature schema was supplied for this route. Treat its output as exploratory review metadata until actual fields are validated; the operation name alone does not establish sentiment analysis, extracted themes, summaries, or any particular rating structure.

Inspect documented combined review-filter metadata for hotel_id, optionally selecting language_code and currency_code. Use the matching hotel context to validate traveler, language, season, or topic controls before requesting review pages. The combined response was not live-validated; do not assume it duplicates every dedicated filter route or has the same field nesting.

Request documented traveler segments metadata for hotel_id with optional language_code and currency_code. Inspect supported identifiers before passing them to filter_customer_type in get-hotel-review. This dedicated metadata response was not live-validated; option labels, counts, and completeness must be checked in actual data. It retrieves filter choices, not the corresponding review pages.

Request documented review languages metadata for hotel_id with optional language_code and currency_code. Inspect supported identifiers before passing them to filter_language in get-hotel-review. This dedicated metadata response was not live-validated; option labels, counts, and completeness must be checked in actual data. It retrieves filter choices, not the corresponding review pages.

Request documented time-of-year segments metadata for hotel_id with optional language_code and currency_code. Inspect supported identifiers before passing them to filter_time_of_year in get-hotel-review. This dedicated metadata response was not live-validated; option labels, counts, and completeness must be checked in actual data. It retrieves filter choices, not the corresponding review pages.

Request documented review topics metadata for hotel_id with optional language_code and currency_code. Inspect supported identifiers before passing them to filter_topic in get-hotel-review. This dedicated metadata response was not live-validated; option labels, counts, and completeness must be checked in actual data. It retrieves filter choices, not the corresponding review pages.

Retrieve documented review sorting metadata for hotel_id with optional language_code and currency_code. Documentation references categories[].id values for the sort input in get-hotel-review, including relevance, recency, and score orderings. These handoffs were not live-validated. Inspect actual supported identifiers before enabling newest-first collection or presenting a score-based ordering choice.

Inspect hotel details using query as a numeric hotel ID, a Booking.com property URL, or a supported hotel-name value. Optional dates, guests, rooms, currency, and display preferences describe the stay. Documentation supports these input forms, but this flexible lookup route was not live-validated and must not inherit the tested get-hotel-details schema by assumption. Accommodation autocomplete is unavailable; use an independently known property and verify the returned identity.

Request documented room options using query as a known hotel ID, property URL, or supported hotel-name value. Carry explicit stay dates, adults, child ages, rooms, and currency from the traveler's selection. This query-based rooms route was not live-validated; check property identity, room structure, price units, and conditions before presenting choices. Retrieval does not reserve a room.

Inspect the documented availability calendar using query as a known hotel ID, property URL, or supported hotel-name value. Optional checkin_date, rooms, children_age, currency_code, and language_code define this calendar request; adults and checkout_date are not exposed here. This flexible calendar route was not live-validated, including URL/ID parity, date horizon, and calendar price coverage.

Inspect facilities using query as a known hotel ID, property URL, or supported hotel-name value, with optional check-in/check-out dates, currency, and language. The documented date defaults are the current date through four days later; use explicit dates for a selected stay. This flexible facilities route was not live-validated, so verify the resolved property and actual amenity fields before display.

Search the documented property-list workflow with location and required checkin_date/checkout_date. Optional adults, children, children_age, rooms, min_bedrooms, min_bathrooms, min_beds, category filters, currency, language, page, and sort support accommodation research. Keep the exact categories-filter parameter name for this family. This location-based property response was not live-validated; inspect returned geography, property identities, and capacity semantics before using it for family stays.

Search the property-list workflow with known dest_id, dest_type, checkin_date, and checkout_date. Optional adults, child count/ages, rooms, minimum bedrooms/bathrooms/beds, categories-filter, currency, language, page, and sort refine the documented request. Accommodation autocomplete is unavailable, so start with an independently known destination pair. This property-list response was not live-validated and must not be assumed to match stays-search pagination or identifiers.

Search the documented property workflow with required northeast/southwest coordinates and both stay dates. Optional bed_rooms, bath_rooms, adults, children_age, rooms, currency, language, price bounds, page, page_size, sort, and categories-filter refine the request. Note this route uses bed_rooms/bath_rooms rather than the location list's min_bedrooms/min_bathrooms. Its viewport response, filter behavior, and page-size enforcement were not live-validated.

Use this documented read-only POST with a user-provided Booking.com search-results url and optional page, currency_code, and language_code query parameters. The url remains a query input; no request-body field is exposed. Remove session and tracking values before sharing links, and review embedded dates and guests. This URL-import response was not live-validated; inspect which search conditions and pagination values are actually preserved.

Retrieve documented property-list filter metadata using a known dest_id/dest_type and required stay dates. Keep adults, child count/ages, rooms, currency, language, and any existing categories-filter aligned with the intended property search. Documentation references data.filters.options.genericId for filter values. The live metadata response and available facet coverage were not validated; inspect actual choices before assembling a property-list filter request.

Inspect documented ordering metadata for the property-list family using dest_id, dest_type, and required check-in/check-out dates. Optional guest, room, category, currency, language, page, and sort inputs retain search context. This metadata response was not live-validated. Use only supported returned property-list sorter identifiers; do not copy tokens from hotel destination search or flight search without validating compatibility.

Retrieve documented property information with detail_id and optional stay dates, currency_code, and language_code. detail_id belongs to the properties workflow and is documented as coming from a detailId value; it is not interchangeable with numeric hotel_id. Accommodation autocomplete is unavailable, so use an independently known detail_id. This route was not live-validated; inspect returned property identity, stay dates, and price fields before enrichment.

Evaluate a documented read-only POST using a Booking.com property url as a required query parameter. This endpoint exposes no separate date, occupancy, language, currency, or body input; inspect any context embedded in the URL and avoid sharing session or tracking values. Its live response and handling of dated or localized property links were not validated. Returned details do not create a reservation.

Inspect documented property facilities using detail_id with optional language_code. This route has no numeric hotel_id, stay-date, or currency inputs. Retain the properties-workflow identifier provenance and do not substitute an unrelated hotel or city ID. Its live response was not validated; inspect actual facility fields and omissions before attaching amenities to a property record.

Request documented property photo information with detail_id and optional language_code. No pagination, image-size, date, or currency input is exposed. The dedicated detail_id photo response was not live-validated; inspect actual image references and property association before use, and review permission to display or cache imagery separately from API access.

Find flight city and airport suggestions with a text query. The verified London response contained status=true, message=Success, and a data array with type, name, code, country, and countryName. Airport rows also carried city/cityName, parent, distanceToCity, and other geographic context. Results included CITY LON and AIRPORT LHR, LGW, and STN, alongside similarly named places in other countries. Select by type and geography; flight-search documentation calls for AIRPORT codes. Successful suggestion lookup does not validate downstream flight prices or searches.

Search documented one-way flights with leavingFrom and goingTo airport codes, an explicit departureDate, and consistent passengers and cabinClass. Optional airline, stop, duration, departure/arrival-time, page, and sort inputs refine the request. Departure defaults to the current date plus one day if omitted. Documentation references data.flightOffers[].token for a later flights-detail request; this is a documented handoff, not a validated live response schema. Flight search and prices were not live-validated.

Search documented return itineraries using leavingFrom, goingTo, departureDate, and returnDate with a consistent cabin and passenger configuration. Optional outbound/return time bands, airline, stops, duration, sorting, and paging constrain the request. Documented defaults are departure tomorrow and return five days after departure; use explicit dates instead. Documentation references flight-offer tokens for detail lookup, but live return-flight fields and pricing were not validated.

Search documented multi-city itineraries using comma-separated leavingFrom, goingTo, and multiStopDates lists. Align each origin, destination, and date by leg; use explicit dates rather than the old documentation examples. Optional passengers, cabin, airline, time bands, directFlightsOnly, stops, sort, and page retain itinerary constraints. Live multi-city responses and offer availability were not validated; inspect actual flightOffers and any detail token before use.

Evaluate the documented minimum-price variant for a one-way airport pair with departureDate, passengers, cabin, airline, stop, duration, time-band, page, and sort preferences. A missing departure date is documented as tomorrow. This variant was not live-validated: no single-minimum output field, comparison coverage, or returned-offer schema is promised. Treat it as current date-specific search research, not an all-time or historical lowest-fare service.

Evaluate the documented minimum-price return-trip variant using leavingFrom, goingTo, explicit departureDate/returnDate, and consistent passengers and cabin. Optional outbound and return time bands, airline, stop, duration, page, and sort inputs constrain the request. This variant was not live-validated; do not promise a single lowest-fare field, guaranteed savings, or booking availability. Compare only matching route/date/passenger contexts.

Evaluate the documented minimum-price multi-city variant with aligned comma-separated leavingFrom, goingTo, and multiStopDates lists. Keep traveler ages, adults, cabin, and route constraints consistent across candidate requests. The live response, fare aggregation, leg coverage, and any minimum-price field were not validated. Inspect actual itinerary structure and prices before comparing multi-leg totals; no historical-fare or booking guarantee is implied.

Inspect the documented flight-detail route with a token from a selected flight-search offer and optional languageCode. Documentation locates the token in data.flightOffers[].token of ordinary one-way, round-trip, or multi-city search. Treat it as opaque search context, not an account login credential, and never publish or hard-code a captured value. This detail response, token lifetime, price fields, and availability were not live-validated. It does not reserve or purchase flights.

Resolve a rental-location text query with optional language_code. Documentation describes downstream use of data.id, data.name, and data.coordinates.latitude/longitude for ID-, name-, or coordinate-based rental searches. Those are documented handoffs rather than observed live fields: this autocomplete response was not validated. Confirm airport, city, terminal, and country context before selecting pickup and return locations.

Search documented rentals with required pickup and drop-off coordinates, dates, and times. Driver age is documented as 30 to 65; optional transmission, supplier, car_type, air conditioning, language, and sort refine the request. Documentation identifies data.search_key and search_results.vehicle_info.v_id for later vehicle reads, plus returned filter identifiers. Rental results, prices, location handling, and all follow-up routes were not live-validated.

Search the documented rental workflow with pickUpId from car location autocomplete and required pickup/return dates and times. Optional driver_age, transmission, hasAirConditioning, and language_code refine the request. Do not replace pickUpId with an airport code, hotel ID, or manually guessed value. This ID-oriented search response and its relationship to coordinate-based rental results were not live-validated.

Search documented rental candidates using pickUpLocation and an optional dropOffLocation name. Set explicit pickup/return dates and times for comparison; documentation otherwise uses the current date for pickup and five days later for return. Optional driver_age, supplier, transmission, air conditioning, language, and sort refine the request. Use confirmed location names from rental discovery. The live name-resolution response and rental prices were not validated.

Inspect documented vehicle specifications and offer context using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

Inspect documented package choices associated with a selected rental vehicle using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

Inspect documented supplier information attached to a selected vehicle offer using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

Inspect documented collection-location information attached to a selected rental vehicle using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

Inspect documented supplier review information for a concrete rental offer using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

Resolve an attraction destination with query and optional currency_code/language_code. Documentation identifies cityUfi as the destination value used by attraction-search and attraction-get-filters. This suggestion route was not live-validated; inspect returned city identities, geography, and actual field structure before constructing a visit search. Keep attraction destination identity separate from hotel and flight identifiers.

Search documented attraction products using a known city_ufi with optional start_date/end_date, currency, language, page, page_size, and returned category, label, city, or price-filter tokens. Documentation references data.products[].slug/id for detail and availability handoffs and filterOptions groups for refinements. These fields were not live-observed: attraction search and downstream availability were not validated. Check actual products, dates, and conditions before presenting excursion choices.

Inspect documented attraction facets using city_ufi with the same optional start/end dates, currency, language, and selected filter context as the activity search. Documentation references typeFilters, ufiFilters, labelFilters, and priceFilters tagname values in filterOptions. The live response and facet coverage were not validated. Refresh choices when the destination or visit window changes rather than assuming tokens are universal.

Request documented attraction details with a product slug from attraction search and optional currency_code/language_code. A display title is not a substitute for the returned slug. This detail response was not live-validated; inspect actual descriptions, conditions, product identity, and any price fields before presentation. Use the separate product_id-based operations for date availability rather than inferring it from detail text.

Inspect documented availability with a selected product_id and required date in YYYY-MM-DD format, plus optional currency_code/language_code. Documentation identifies product_id as the attraction-search product id, not its slug or the city_ufi. The live availability response, timeslots, prices, and capacity were not validated. Treat any returned choices as informational candidates, not purchased admission or held capacity.

Inspect the documented availability calendar for a selected product_id with optional currency_code/language_code. This request exposes no date-range or visit-date input; do not invent one. Its live response, calendar horizon, daily prices, and status meanings were not validated. Inspect returned date candidates before asking for a separate product-and-date availability response.

Resolve a transfer pickup or drop-off text query with optional language_code. Documentation identifies googlePlaceId as the value for taxi-search pick_up_place_id and drop_off_place_id. This place-suggestion response was not live-validated. Confirm airport, hotel, entrance, and geographic context before constructing a transfer request; do not substitute a hotel ID or flight airport code for a place identifier.

Search documented transfer candidates using required pick_up_place_id, drop_off_place_id, pick_up_date, and pick_up_time. Use place identifiers selected through transfer place discovery and optional language_code/currency_code. The live response, vehicle types, quote fields, and availability were not validated. This is a read-only search: it does not reserve a vehicle, dispatch a driver, or track flight delays.

Inspect documented supported currency values, optionally filtering with name. Other currency-aware endpoints reference the returned code value for currency_code or baseCurrency. This reference response was not live-validated, so inspect actual code/name fields and filter behavior before building a selector. This is a supported-currency lookup, not an exchange-rate or guaranteed conversion endpoint.

Inspect documented supported language values, optionally filtering with name. Other endpoints reference the returned code for language_code or languageCode, using each operation's exact spelling. This reference response and optional filter were not live-validated. Do not assume every display locale is also a valid hotel-review content-language filter or that requesting a locale guarantees translated content.

Inspect the documented exchange-rate reference route with optional baseCurrency, whose documented default is USD. Use a supported currency code and record retrieval time if evaluating a trip-cost conversion table. The live response, rate-field layout, timestamp, supported currency coverage, and update frequency were not validated. A converted estimate is not a guaranteed hotel or transaction exchange rate.

Inspect the documented location-coordinate lookup with location and optional limit. Accommodation search documentation references centroid.lat and centroid.lon from this lookup as candidate search coordinates. The live geocoder response, ambiguity handling, and limit enforcement were not validated. Confirm the place and geography before using a selected coordinate in radius-based hotel search.

Make the documented no-parameter connectivity request. Its live response body and success fields were not validated, so no particular pong or data schema is promised. Even a successful connectivity response cannot prove that hotel prices, reviews, destination lookup, or other travel operations are healthy; use a meaningful property-data control for that purpose.