Booking COM: the complete guide to every endpoint

This is the one document that explains every endpoint of the API: what it is for, what to send, where each value comes from, and what you get back. Read it top to bottom to learn the whole API, or jump to an endpoint from the contents.

How to read this guide

• Base URL: https://booking-com30.p.rapidapi.com/api/v1. Every request carries two headers: X-RapidAPI-Key: YOUR_KEY and X-RapidAPI-Host: booking-com30.p.rapidapi.com.
• Every response is HTTP 200 with status (true or false), message and data. A wrong parameter gives Validation failed with an errors list, and uses no quota.
• Values are passed on. A destination token, a hotel id, an offer token or a search key always comes from an earlier response. The "Where the inputs come from" line of each endpoint says which one.
• Parameter tables say whether a value is required and what is allowed. Where a value is a fixed list, the list is given.
• Each endpoint has the same parts: What it does, Where the inputs come from, Request, then its parameters and rules, What you get back and Fields.

Contents

Hotels and stays

• Stays Autocomplete
• Stays Suggestions (popular destinations)
• Stays Map Markers
• Stays Page Metadata
• Stays Search
• Stays Map
• Stays Search Filters (dynamic, live counts)
• Stays Search Sort Options (dynamic)
• Stays Property Details (the stay detail page)
• Stays Description
• Stays Description Sections
• Stays Highlights (feature badges only)
• Stays Badges
• Stays House Rules
• Stays Important Info
• Stays Policies
• Stays Rooms (room list)
• Stays Room Types (available and sold out)
• Stays Facilities
• Stays Property Facilities
• Stays Food and Drink
• Stays Photos
• Stays Photo List
• Stays Review Photos
• Stays Review Scores
• Stays Review Score Comparison
• Stays Featured Reviews
• Stays Review Filters
• Stays Reviews
• Stays Questions
• Stays Surroundings
• Stays Things To Do

Shared lookups

• Common Languages (shared by every module)
• Common Currencies (shared by every module)
• Common Exchange Rates (shared by every module)

Attractions and things to do

• Attractions Autocomplete
• Attractions Destinations
• Attractions Suggestions
• Attractions Search
• Attractions Search Filters
• Attraction Product
• Attraction Comparison
• Attraction Review Snippets
• Attraction Reviews
• Attraction Availability Calendar
• Attraction Availability
• Attraction Live Availability
• Attraction Legal Consent

Flights

• Flights Autocomplete
• Flights Fly Anytime ("I'm flexible")
• Flights Search
• Flights Details
• Flights Fare Quote
• Flights Fare Quote Extras
• Flights Seat Map

Car rental

• Cars Countries
• Cars Autocomplete
• Cars Search
• Cars Vehicle
• Cars Supplier
• Cars Supplier Reviews
• Cars Supplier Location
• Cars Terms
• Cars Price Summary

Taxi and airport transfers

• Taxi Autocomplete
• Taxi Airports
• Taxi Flights
• Taxi Search
• Taxi Supplier
• Taxi Public Transport
• Taxi Uber Rates

Hotels and stays

1. Stays Autocomplete

What it does. Destination suggestions for a search box: type "Mum", get cities, airports, landmarks and hotels.

Where the inputs come from. Nothing from an earlier call: this is where a hotel journey starts. query is the text your user typed.

Request

GET /api/v1/stays/autocomplete?query=Mum
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Always HTTP 200. status says whether it worked.

{
  "status": true,
  "message": "Destinations found",
  "data": {
    "Booking.com": { "serverVersion": 180, "clientVersion": 180, "mfeId": "b-accommodation-disambiguation-saba-mfe/autocomplete" },
    "suggestions": [ { ...see fields below... } ]
  }
}

Suggestion fields

Suggestions are de-duplicated by id + type (Booking.com repeats the first result in a "return button" action).

Example suggestion (city)

{
  "id": -2092174,
  "type": "city",
  "name": "Mumbai",
  "subtitle": "Maharashtra (Mumbai Region ), India",
  "labels": [
    { "type": "city", "name": "Mumbai" },
    { "type": "region", "name": "Maharashtra (Mumbai Region )" },
    { "type": "country", "name": "India" }
  ],
  "countryCode": "in",
  "coordinates": { "latitude": 18.9689769744873, "longitude": 72.8189697265625 },
  "hotelsCount": 1975,
  "imageUrl": ".../city/square150/1000023.jpg?k=…&o=",
  "images": {
    "thumbnail": ".../city/square150/1000023.jpg?k=…&o=",
    "medium": ".../city/square550/1000023.jpg?k=…&o=",
    "large": ".../city/max1024x768/1000023.jpg?k=…&o="
  },
  "searchContext": { "searchText": "Mum", "index": 0 },
  "providerMetadata": { "autocompleteSource": "brick", "roundTripVariable": "GhBk…==", "metaMatches": [] }
}

Sample result for query=Mum (5 items, in order): Mumbai (city), Chhatrapati Shivaji International Airport Mumbai (airport), Mumbai Central (landmark), The Taj Mahal Palace, Mumbai (hotel), Navi Mumbai (city).

2. Stays Suggestions (popular destinations)

What it does. Themed lists of popular destinations for a home-page / empty search box: "Hill stations and mountains", "Goa and Kerala beaches", "Swiss Alps and lakes", and so on. Complements autocomplete, which needs typed text. This is also a valid source of a search destination, exactly like autocomplete — every destination card here carries its own destination token (see the Fields table below), copyable straight into /stays/search, /stays/search-filters or /stays/search-sort-options. A layman user can tap any popular-destination card shown here, with no typing, and go straight to search.

Where the inputs come from. Nothing from an earlier call. It needs no destination: it returns popular destinations to show before the user types anything. Only languageCode is optional.

Request

GET /api/v1/stays/suggestions?limit=6
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Suggestions found",
  "data": {
    "clusterCount": 10,
    "destinationCount": 60,
    "clusters": [
      {
        "index": 0,
        "name": "Heritage cuisine trails",
        "count": 6,
        "destinations": [
          {
            "id": -2106102,
            "type": "city",
            "destination": "city:-2106102",
            "name": "New Delhi",
            "subtitle": null,
            "labels": [],
            "countryCode": "in",
            "countryName": "India",
            "coordinates": null,
            "hotelsCount": null,
            "imageUrl": "https://r-xx.bstatic.com/xdata/images/city/square150/990313.jpg?k=…&o=",
            "images": {
              "thumbnail": "https://r-xx.bstatic.com/xdata/images/city/square150/990313.jpg?k=…&o=",
              "medium":    "https://r-xx.bstatic.com/xdata/images/city/square550/990313.jpg?k=…&o=",
              "large":     "https://r-xx.bstatic.com/xdata/images/city/max1024x768/990313.jpg?k=…&o="
            },
            "themeId": null,
            "image": { "id": 990313, "genericUrl": "/xdata/images/city/<SIZE>/990313.jpg?k=…&o=", "extras": null },
            "extras": null
          }
        ],
        "extras": null
      }
    ],
    "Booking.com": { "durationMs": 72, "startTime": 1792308704766, "endTime": 1792308704838, "extraExtensions": null, "extraOutput": null }
  }
}
  ...

Fields

Left out on purpose: service's __typename tags (DestinationCard, MainImage, Recommendations, DestinationMultiCardsOutput, RecommendationPlatformQueries), which only name internal types. Order is preserved, nothing is de-duplicated, and a destination appearing in two clusters appears twice.

Same destination keys as autocomplete

A destination here has the same keys as an autocomplete suggestion (id, type, name, subtitle, labels, countryCode, coordinates, hotelsCount, imageUrl, images), so one client model reads both. Fields a Booking.com does not send are null ([] for labels). Differences: suggestions add countryName, themeId, image and extras; autocomplete adds searchContext and providerMetadata and has no countryName. The list wrapper differs: autocomplete is a flat suggestions[], suggestions is clusters[].destinations[].

3. Stays Map Markers

What it does. The map pins that are not properties: the cities, districts, landmarks, airports, beaches and ski resorts inside a map area, each with its name, coordinates and, where there is one, the destination token that you can pass straight to a search.

Where the inputs come from. Part 1 (Find where to search) in the journey overview, next to GET /stays/map: ask for the properties and for these pins with the same map corners.

Request

GET /api/v1/stays/map-markers?northEast=40.92,-73.70&southWest=40.55,-74.30&types=airports,landmarks&limit=5
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Map markers found",
  "data": {
    "boundingBox": { "northEast": { "latitude": 40.92, "longitude": -73.7 }, "southWest": { "latitude": 40.55, "longitude": -74.3 } },
    "markerCount": 7,
    "markers": {
      "airports": [ { "id": 39, "destination": "airport:39", "name": "LaGuardia Airport", "latitude": 40.7742, "longitude": -73.8719, "photoUrls": [], "cityName": "New York", "countryName": "United States", "iata": "LGA" } ],
      "landmarks": [ { "id": 11045, "destination": "landmark:11045", "name": "Empire State Building", "latitude": 40.74843, "longitude": -73.98567, "photoUrls": ["https://r-xx.bstatic.com/xdata/images/landmark/270x200/278346.jpg?k=…"] } ]
    }
  }
}

Fields

4. Stays Page Metadata

What it does. The public booking.com page of any destination and its SEO text: the link, the title, a short description, the keywords and a 200 px image. It works for every kind of destination GET /stays/autocomplete returns: hotel, city, district, airport, landmark, region and country.

Where the inputs come from. Take a destination token from GET /stays/autocomplete (or hotel:<id> for a property found in /stays/search). See the journey overview.

Request

GET /api/v1/stays/page-metadata?destination=city:20088325&languageCode=en-gb
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Page metadata found",
  "data": {
    "title": "3239 hotels in New York, USA. Book your hotel now! - Booking.com",
    "description": "Great savings on hotels in New York, USA online. Good availability and great rates. Read hotel reviews and choose the best hotel deal for your stay.",
    "url": "https://www.booking.com/city/us/new-york.en-gb.html",
    "keywords": ["3 star hotel", "4 star hotel", "..."],
    "imageUrl": "https://cf.bstatic.com/xdata/images/city/square200/....jpg?k=...&o=",
    "extras": null
  }
}

Fields

5. Stays Search

What it does. Find stays (hotels, apartments, hostels, ...) for a destination and dates, 20 results per page, with readable details: price, taxes, discount, review, distance from the centre, perks, deal badges, images.

Where the inputs come from. Part 2 of the journey overview (the search list); Part 1 gets you a destination, the same list on a map is GET /stays/map. Next step after this call: pick a property from data.properties[] and pass its id as hotelId to the Part 3 endpoints: the whole page in one call (property-details), or by topic - about it (description, description-sections, highlights, badges, house-rules, important-info, policies), rooms and prices (rooms, room-types), facilities and food (facilities, property-facilities, food-and-drink), photos (photos, photo-list, review-photos), reviews and questions (review-scores, review-score-comparison, featured-reviews, review-filters, reviews, questions) and around the property (surroundings, things-to-do). See the journey overview for the whole flow.

Request

GET /api/v1/stays/search?destination=city:-2092174&checkin=2026-12-01&checkout=2026-12-02&adults=2&rooms=1&currencyCode=INR&languageCode=en-us&page=1
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Auth, subscription and monthly quota work as for the other stays endpoints (one search = one request).

Validation errors use the usual shape: {"status":false,"message":"Validation failed","errors":[{"field","message"}]}.

Flexible dates ("I'm flexible")

Instead of exact dates you can ask for a stay of N nights that starts on a weekday, in up to 3 months, like the app's "I'm flexible" tab. Booking.com then finds, for every property, its cheapest matching window, and each property shows its own dates and the price for exactly that window.

GET /api/v1/stays/search?destination=city:20088325&flexibleMonths=2026-11,2026-12&flexibleNights=2&flexibleStartWeekday=friday&adults=2&currencyCode=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Rules (each broken rule is a Validation failed answer, because Booking.com would otherwise silently run an ordinary search):

• flexibleMonths, flexibleNights and flexibleStartWeekday must all be given, and not together with checkin/checkout.
• At most 3 months, each YYYY-MM, none in the past (the current month is fine: only its days after today are used), none more than 500 days ahead. Repeats are removed and the months are sorted.
• 1–90 nights.
• The stay starts tomorrow at the earliest (today is never used, even on the chosen weekday). Only the check-in has to be in a chosen month; the check-out can fall in the next month.
• Everything else works as in an ordinary search: adults, rooms, childrenAges, pets, filters, currencyCode, languageCode, sortBy (price sorts by the flexible price) and page. A month with no matching day left (or too far ahead) simply returns status false, no properties.
• /stays/search-filters and /stays/search-sort-options do not accept flexible dates; call them with an ordinary date range.

What comes back:

• properties[].stay is new and always present: { checkin, checkout, nights, label }, the dates the property's price is for. In an ordinary search it is the searched range; in a flexible search every property has its own (its cheapest window in your months). label is the same range as the app writes it, in your language (Fri 20 Nov – Sun 22 Nov, Sa., 21. Nov. – Di., 24. Nov.); it no longer also appears in badges.
• search.mode is fixed, plusMinusDays or flexibleMonths. In the months mode search.checkin and search.checkout are null and search.flexible says what was asked: { months: [{ year, month, name, value }], nights, startWeekday: { number, name } }; search.nights is the stay length.
• The price of a property is the total for its own window, exactly what an ordinary search of those dates shows (checked on 18 hotels). Two properties in the same list can have different windows; compare them by stay, not by position.

{
  "search": { "mode": "flexibleMonths", "flexibleDays": 0, "checkin": null, "checkout": null, "nights": 2,
              "flexible": { "months": [ { "year": 2026, "month": 11, "name": "November", "value": "2026-11" } ], "nights": 2, "startWeekday": { "number": 5, "name": "friday" } } },
  "properties": [
    { "id": 1106729, "name": "HI New York City Hostel", "stay": { "checkin": "2026-11-20", "checkout": "2026-11-22", "nights": 2, "label": "Fri 20 Nov – Sun 22 Nov" },
      "price": { "amount": 292, "currencyCode": "USD", "formatted": "US$292" } }
  ]
}

Plus/minus days (flexibleDays)

On the Calendar tab the app can search exact dates or ± 1, 2, 3 or 7 days. Send your checkin and checkout as usual and add flexibleDays:

GET /api/v1/stays/search?destination=city:20088325&checkin=2026-11-10&checkout=2026-11-12&flexibleDays=3

• Every property shows its cheapest window whose check-in is within 3 days either side of checkin, for the same number of nights (here 2). properties[].stay has that property's own dates and price is the total for exactly those dates (the same price an exact-dates search of that window gives). The exact dates are often not the cheapest: in the test, with ± 3 days none of 16 compared hotels was cheapest on the searched date's neighbours-only basis, the chosen check-ins were 3, 2 and 1 day before and 1 day after.
• Only 0, 1, 2, 3 and 7 are accepted (the app's own five choices); 4, 5, 6, 10, 14 and others are rejected, because Booking.com answers them with an error.
• search.mode is plusMinusDays, search.flexibleDays the number, and search.checkin / search.checkout stay as you sent them. search.nights is the stay length.
• It cannot be combined with flexibleMonths / flexibleNights / flexibleStartWeekday (they are the app's two separate modes). Everything else (guests, filters, sorting, paging, currency, language) works as usual. The same options exist on the map: GET /stays/map.

What you get back

{
  "status": true,
  "message": "Properties found",
  "data": {
    "search": { "destination": "city:-2092174", "destinationId": -2092174, "destinationType": "city", "checkin": "2026-12-01", "checkout": "2026-12-02",
                "adults": 2, "rooms": 1, "childrenAges": [0, 3], "pets": false, "currencyCode": "INR", "languageCode": "en-us", "page": 1,
                "nights": 1, "sortBy": "popularity", "resolvedSortBy": "popularity", "searchId": "7e9db4bb-…", "pageViewId": "0dba3c04…" },
    "pagination": { "page": 1, "pageSize": 20, "count": 20, "totalResults": 957, "totalResultsText": "957 properties",
                    "totalPages": 48, "maxPage": 50, "hasNextPage": true },
    "propertyTypes": [ { "name": "Hotels", "count": 703, "countText": "703 properties", "filter": "property_type::204" } ],
    "map": { "boundingBox": { "northEast": { "latitude": 19.358, "longitude": 73.163 }, "southWest": { "latitude": 18.657, "longitude": 72.782 } } },
    "properties": [ { "…": "see below" } ],
    "Booking.com": { "serverVersion": 180, "clientVersion": 180, "mfeId": "b-saba-mfe-appsearch/saba", "extras": null }
  }
}

Page-level fields:

• search: what was searched, plus mode (fixed or flexible; with flexible dates checkin/checkout are null and flexible describes the request), nights, sortBy (an echo of the request — always present), resolvedSortBy (Booking.com's own raw sort key it actually applied) and ids from Booking.com (searchId, pageViewId). resolvedSortBy and pageViewId are only present on page 1 and only when sortBy is left at the default — asking Booking.com to sort at all (even popularity explicitly) makes it stop returning this, ; omitting the parameter for the default case keeps it populated, since the result is identical either way.
• pagination.totalResults / totalPages / totalResultsText: page 1 only (null on later pages; keep the value from page 1). hasNextPage is false on the last page or page 50.
• propertyTypes: Hotels / Apartments / Hostels / Guest houses with counts and Booking.com's filter value (for the filters to come). Page 1 of city/region searches only; empty otherwise and for latlong/airport/hotel.
• map.boundingBox: the rectangle containing the results (page 1).

A property

{
  "id": 10679861,
  "name": "Aurika, Mumbai International Airport - Luxury by Lemon Tree Hotels",
  "position": 7,
  "starRating": 5,
  "isPreferred": true,
  "review": { "score": 8.5, "label": "Very Good", "count": 1637 },
  "location": { "latitude": 19.103475, "longitude": 72.862584, "countryCode": "in", "cityId": -2092174,
                "summary": "Western Suburbs • 3.4 km from downtown", "area": "Western Suburbs",
                "distanceFromCenterKm": 3.4, "distanceFromCenterText": "3.4 km from downtown" },
  "highlights": [ { "icon": "beach_palm", "text": "Beachfront", "distanceKm": null } ],
  "perks": [ "Breakfast included" ],
  "urgency": [ "We have 3 left at this price" ],
  "roomsLeft": 3,
  "stay": { "checkin": "2026-12-01", "checkout": "2026-12-02", "nights": 1, "label": null },
  "badges": [ { "text": "Late Escape Deal", "variant": "constructive", "identifier": "Late Escape Campaign", "explanation": "Late Escape Deal" } ],
  "roomSummary": "Hotel room: 2 beds",
  "price": { "amount": 8228, "currencyCode": "INR", "formatted": "₹ 8,228", "taxesIncluded": false,
             "taxesAndFees": { "amount": 2451.94, "currencyCode": "INR" }, "totalAmount": 10679.94,
             "chargesInfo": "+₹ 2,452 taxes and fees", "originalAmount": 12100, "originalFormatted": "₹ 12,100",
             "discountPercent": 32, "taxExceptions": [], "extras": null },
  "checkInTime": { "from": "14:00", "until": "00:00" },
  "checkOutTime": { "from": "00:00", "until": "12:00" },
  "imageUrl": ".../square60/530661047.jpg?k=…&o=",
  "mainPhotoId": 530661047,
  "images": { "thumbnail": ".../square150/…", "medium": ".../square550/…", "large": ".../max1024x768/…" },
  "blockIds": [ "1067986109_441325494_2_0_0_1447906" ],
  "extras": { "wishlistName": "Mumbai", "isFirstPage": true, "currency": "INR", "optOutFromGalleryChanges": 0, "qualityClass": 0 }
}

Price

Prices are for the whole stay and all rooms you asked for.

• amount / formatted: the main price shown by Booking.com, in currencyCode.
• taxesIncluded: false when taxes and fees are charged on top (taxesAndFees gives them, totalAmount = amount + taxes); true when amount already contains them (taxesAndFees is null, totalAmount = amount). Which form comes back depends on Booking.com/market, so read this flag instead of assuming.
• originalAmount / originalFormatted / discountPercent: the struck-through price on discounted stays (null otherwise). The percent is computed as 1 - amount / originalAmount.
• chargesInfo: Booking.com's own wording ("+₹ 2,452 taxes and fees", "Includes taxes and charges").

6. Stays Map

What it does. The properties on the map: the same search as GET /stays/search, but you can ask for the visible map area (a bounding box) as well as for a destination, and you get up to 100 properties per call, each with its coordinates, price, review, its own stay dates and the room-level offers.

Where the inputs come from. Part 2 (The search list) in the journey overview, next to GET /stays/search. Use it to draw a map: send the corners of the area the user sees (northEast, southWest), and again whenever the map moves or zooms. The pins that are not properties (airports, landmarks, beaches ...) are in GET /stays/map-markers.

Request

GET /api/v1/stays/map?northEast=40.8327,-73.9109&southWest=40.6433,-74.0245&checkin=2026-11-10&checkout=2026-11-12&adults=4&rooms=2&childrenAges=0,3&currencyCode=INR&limit=100
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Properties found",
  "data": {
    "search": { "mode": "fixed", "destination": null,
                "boundingBox": { "northEast": { "latitude": 40.8327, "longitude": -73.9109 }, "southWest": { "latitude": 40.6433, "longitude": -74.0245 } },
                "checkin": "2026-11-10", "checkout": "2026-11-12", "flexible": null, "flexibleDays": 0, "nights": 2, "firstWindow": null,
                "adults": 4, "rooms": 2, "childrenAges": [0, 3], "filters": [], "pets": false, "sortBy": "popularity",
                "currencyCode": "INR", "languageCode": "en-us", "searchId": "780280b2-...", "destinationName": "New York", "destinationCountryCode": "us" },
    "pagination": { "page": 1, "limit": 100, "offset": 0, "count": 100, "hasNextPage": true },
    "map": { "boundingBoxes": [ { "type": "SMART_AV", "northEast": { "latitude": 40.8485, "longitude": -73.9216 }, "southWest": { "latitude": 40.6897, "longitude": -74.0223 } } ] },
    "properties": [
      { "id": 1106729, "name": "West Side YMCA", "position": 0, "accommodationTypeId": 203,
        "starRating": 3, "qualityRating": null, "isPreferred": false, "isPreferredPlus": false, "isSponsored": false, "sponsored": null,
        "review": { "score": 6.6, "label": "Pleasant", "count": 14063 },
        "location": { "latitude": 40.7708451, "longitude": -73.9806124, "address": "5 West 63rd Street", "city": "New York (New York)", "countryCode": "us", "cityId": 20088325,
                      "area": "Upper West Side", "distanceFromCenterText": "350 m from centre", "distanceFromSearchPointKm": 0.33, "distanceText": "350 m",
                      "locationScore": 9.4, "locationScoreLabel": "Location", "displayLocation": null, "skiLiftDistance": null, "skiLiftDistanceDescription": null },
        "stay": { "checkin": "2026-11-10", "checkout": "2026-11-12", "nights": 2, "isOwnWindow": false },
        "price": { "amount": 34348.56, "currencyCode": "INR", "formatted": "Rs. 34,349", "taxesIncluded": true, "taxesAndFees": null, "totalAmount": 34348.56,
                   "chargesInfo": "Includes taxes and charges", "originalAmount": 40800.66, "originalFormatted": "Rs. 40,801", "discountPercent": 16,
                   "averagePricePerNight": null, "hasIncalculableCharges": false, "taxExceptions": [], "rewardsBenefits": [], "extras": null },
        "badges": [ { "text": "Late Escape Deal", "style": "constructive", "name": "Late Escape Campaign" } ],
        "labels": [], "mealPlan": null, "freeCancellation": false, "noPrepayment": false, "roomSummary": null, "units": { "commonConfiguration": { "beds": [ { "count": 3 } ], "nbUnits": 3 } },
        "rooms": [ { "roomId": 110672904, "mealPlanId": 0, "occupancy": 2, "packageId": "0", "policyGroupId": "91476666", "price": { "amount": 11449.52, "currencyCode": "INR" }, "originalPrice": { "amount": 120.58, "currencyCode": "USD" }, "freeCancellationUntil": null, "onlyXLeft": null, "surfaceSize": 8 } ],
        "soldOut": { "isSoldOut": false, "messages": [] }, "genius": null,
        "checkInTime": { "from": "15:00", "until": null }, "checkOutTime": { "from": null, "until": "11:00" },
        "imageUrl": ".../square200/204079362.jpg?k=…&o=", "mainPhotoId": 204079362, "images": { "thumbnail": "...", "medium": "...", "large": "..." }, "extras": { "bundleRatesAvailable": true, "visibilityBoosterEnabled": true } }
    ],
    "sortOptions": [ { "name": "popularity", "caption": "Top picks for families", "selected": true, "tooltip": null } ],
    "filterGroups": [ { "field": "class", "title": "Property rating" } ],
    "appliedFilters": [], "recommendedFilters": [],
    "Booking.com": { "appSearchMetaData": "last_x_property_ids=...,hotels_cc1=us,search_id=..." }
  }
}

Fields

7. Stays Search Filters (dynamic, live counts)

What it does. The live, per-search filter list with real counts — what the app's "Filter by" screen shows (e.g. "Pets allowed (41)"). Counts, and which filters are even offered, depend on the destination, dates, guests, and whatever filters are already applied. This is also the only way to discover which key::value pairs /stays/search's own filters parameter accepts — call this endpoint with no filters applied.

Where the inputs come from. The same destination, dates and guests you send to GET /stays/search (the destination comes from autocomplete or suggestions). Call it to build the filter menu, then pass the chosen filter strings to the search.

Request

GET /api/v1/stays/search-filters?destination=city:-2092174&checkin=2026-12-01&checkout=2026-12-02&filters=class::5
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Same auth, subscription and quota as /stays/search (one call = one request).

No page — this isn't paginated.

What you get back

{
  "status": true,
  "message": "Filters found",
  "data": {
    "destination": { "id": -2092174, "countryCode": "in", "name": "Mumbai" },
    "totalResults": 1386,
    "totalResultsExactDates": 1109,
    "nights": 1,
    "quickFilters": {
      "popular": [ { "id": "class::5", "label": "5 stars", "count": 60 } ],
      "yourPreviousFilters": [ { "id": "facility::4", "label": "Pets allowed", "count": 125 } ]
    },
    "families": [
      {
        "field": "class",
        "title": "Property rating",
        "subtitle": "Find high-quality hotels and holiday rentals",
        "style": "checkbox",
        "options": [
          { "id": "class::0", "label": "Unrated", "count": 336, "selected": false, "extras": null },
          { "id": "class::5", "label": "5 stars", "count": 60, "selected": true, "extras": null }
        ],
        "collapsed": false,
        "extras": null
      },
      {
        "field": "price",
        "title": "Your budget (for 1 night)",
        "style": "slider",
        "options": [],
        "priceRange": { "min": 10000, "max": 400000, "step": 10000, "currency": "INR", "histogram": [ 42, 57, 57, "…50 buckets" ], "selectedMin": null, "selectedMax": null }
      },
      {
        "field": "unit_config_grouped",
        "style": "stepper",
        "options": [ "…25 raw options, superseded by steppers below" ],
        "steppers": [
          { "field": "entire_place_bedroom_count", "title": "Bedrooms", "min": 0, "max": 5, "default": 0, "selected": 0, "labels": [] },
          { "field": "num_beds", "title": "Beds", "min": 0, "max": 5, "default": 0, "selected": 0, "labels": [ "0 or more beds", "1 or more beds", "…" ] },
          { "field": "min_bathrooms", "title": "Bathrooms", "min": 0, "max": 15, "default": 0, "selected": 0, "labels": [ "0 or more bathrooms", "…" ] }
  ...

Fields

Dropped as pure telemetry: service's own __typename tags, and Booking.com's trackOnClick/trackOnView/trackOnSelectPopular/etc. A/B-test fields — present on every single filter and option, confirmed empty of real data after stripping (checked on a live response: zero non-telemetry leftovers anywhere). The cleaned response is about 21 KB against Booking.com's ~165 KB.

8. Stays Search Sort Options (dynamic)

What it does. The live, per-search sort option list — what builds the app's "Sort by" screen. Also the one way to discover every valid sortBy value for /stays/search.

Where the inputs come from. The same destination, dates and guests you send to GET /stays/search. Call it to build the sort menu, then pass the chosen value as sortBy.

Request

GET /api/v1/stays/search-sort-options?destination=city:-2092174&checkin=2026-12-01&checkout=2026-12-02
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Exactly the same required/optional parameters as /stays/search-filters — same Booking.com request shape, so the same schema is reused server-side. No page, latlong not supported.

What you get back

{
  "status": true,
  "message": "Sort options found",
  "data": {
    "options": [
      { "value": "homesAndApartmentsFirst", "label": "Entire homes & apartments first", "selected": false, "providerValue": "upsort_bh" },
      { "value": "popularity", "label": "Our top picks", "selected": true, "providerValue": "popularity" },
      { "value": "distance", "label": "Near city centre first", "selected": false, "providerValue": "distance" },
      { "value": null, "label": "Distance from closest beach", "selected": false, "providerValue": "closest_beach_distance" },
      { "value": "classDescending", "label": "Property rating (5 to 0)", "selected": false, "providerValue": "class_descending" },
      { "value": "classAscending", "label": "Property rating (0 to 5)", "selected": false, "providerValue": "class_ascending" },
      { "value": "reviewScore", "label": "Best reviewed first", "selected": false, "providerValue": "bayesian_review_score" },
      { "value": "price", "label": "Price (lowest first)", "selected": false, "providerValue": "price" },
      { "value": "priceDescending", "label": "Price (highest first)", "selected": false, "providerValue": "price_from_high_to_low" }
    ]
  }
}

9. Stays Property Details (the stay detail page)

What it does. Everything the app shows on a hotel's page for the dates and guests you choose: the name, type, address and coordinates, the facilities, every room (description, size, beds, facilities, photos, child and bed rules) and every rate you could book (price breakdown with taxes and charges, cancellation and prepayment terms, meal plan, how many are left), plus the important information and, for homes, the host.

Where the inputs come from. Pick a property from GET /stays/search, pass its id as hotelId together with the same dates and guests. It is the "whole detail page in one call" of Part 3 in the journey overview. The other property endpoints each keep their own job: facilities and Q&A ids are in /stays/property-facilities, photos have their own endpoint (/stays/photos); reviews, scores and policies are in /stays/review-scores, /stays/reviews and /stays/policies. Every room type and every rate (not only the recommended ones) is in /stays/rooms; the IDs are explained in ids.md. Attractions near the property are in /stays/things-to-do: pass latlong:<location.latitude>,<location.longitude> or city:<location.destinationId> from this response as its destination.

Request

GET /api/v1/stays/property-details?hotelId=237786&checkin=2026-12-01&checkout=2026-12-03&adults=4&rooms=2&childrenAges=0,3&currencyCode=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Dates: what depends on them

Booking.com itself requires dates for this call, so when you send none we use tomorrow and the day after and say so with availability.datesAreDefault: true. Tested on three hotels with several dates:

So: if you only want to show what the property is, the dates can be left out. If you want what it costs or whether it is available, send checkin and checkout, and check availability.datesAreDefault before you trust "sold out". For the list of every room type with sold-out ones marked use /stays/room-types, for every rate /stays/rooms (both require dates). All endpoints and their date rules: dates-and-guests.md.

What you get back

{
  "status": true,
  "message": "Property page found",
  "data": {
    "hotelId": 237786,
    "property": { "id": 237786, "name": "InterContinental Marine Drive Mumbai, an IHG Hotel", "accommodationType": "Hotels", "accommodationTypeId": 204, "url": "https://www.booking.com/hotel/in/...", "defaultLanguage": "en-gb", "timezone": "Asia/Kolkata", "isPreferred": true, "isPreferredPlus": false, "isClosed": false, "chains": [ "..." ], "...": "..." },
    "location": { "fullAddress": "...", "street": "...", "city": "Mumbai", "district": "...", "zip": "...", "country": "India", "countryCode": "in", "latitude": 18.93, "longitude": 72.82, "distanceToCityCentreKm": 4.1, "isCityCentre": false, "destinationId": -2092174, "districtIds": [ 1 ] },
    "reviews": { "reviewCount": 529, "breakfast": { "rating": 0, "reviewCount": 0, "...": "..." }, "wifi": { "rating": 9.4 } },
    "facilities": { "facilityIds": [ 3, 4, 5 ], "popular": { "name": "Most popular facilities", "type": "popular", "facilities": [ { "name": "Free WiFi", "icon": "wifi" } ] }, "topBenefits": [ "..." ], "highlights": [ "..." ], "family": [ "Family rooms" ], "languagesSpoken": [ "en-gb", "hi" ], "roomsSummary": { "hasRefundable": true, "hasNonrefundable": false, "hasKitchen": false, "hasSeating": false, "commonKitchenFac": [] } },
    "availability": { "checkin": "2026-12-01", "checkout": "2026-12-03", "datesAreDefault": false, "requestedCurrencyCode": "USD", "propertyCurrencyCode": "INR", "soldOut": false, "availableRooms": 3, "totalRates": 28, "rateCount": 2, "urgencyRoomText": "2 x Classic King Room with Bay View", "scarcityMessages": { "roomPage": [ { "id": "23778639_95438172_1_2_0", "value": "We have 6 left" } ], "...": "..." }, "stayLengthLimits": { "maxAllowedLos": 90, "defaultLos": 45, "extendedLos": 90, "...": "..." }, "maxRoomsPerBooking": 6, "cantBook": false },
    "pricing": { "priceBreakdown": { "grossAmount": { "value": 0, "currency": "USD", "amountRounded": "US$0" }, "allInclusiveAmount": { "...": "..." }, "includedTaxesAndChargesAmount": { "...": "..." }, "chargesDetails": { "...": "..." }, "items": [ "..." ], "...": "..." }, "transparencyMode": "transparent", "isPriceTransparent": false, "averageRoomSizeM2": 40.1 },
    "policies": { "importantInformation": [ { "sentenceId": 3, "phrase": "...", "executingPhase": 0 } ], "paymentDetail": { "model": "hybrid2.0" }, "creditCardRequired": true, "cvcRequired": true, "...": "..." },
    "recommendation": { "title": "Enjoy some extra space with 3 rooms for 4 adults, 2 children (< 1 and 3 years old)", "guestsPerRoom": { "adults": 2, "children": [ 3 ] }, "childrenStayFree": [ { "blockId": "23778639_95438172_1_2_0", "title": "Free stay for both of your children", "content": "Your children (<1 and 3 years old) can sleep here for no additional charge.", "class": "CHILD_STAYS_FREE" } ], "rooms": [ "..." ] },
    "roomCount": 2,
    "rooms": [
      { "id": "23778621", "description": "...", "facilities": [ { "id": 74, "name": "Laptop safe", "facilitytypeId": 8, "altFacilitytypeId": 12, "altFacilitytypeName": "Kitchen" } ], "bedConfigurations": [ { "bedTypes": [ { "name": "Double bed", "count": 1, "description": "131-150 cm wide" } ] } ], "highlights": [ { "translatedName": "Free WiFi", "icon": "wifi" } ], "photos": [ { "photoId": 1, "urlSquare60": "...", "urlMax750": "...", "urlMax1280": "...", "ratio": 1.5 } ], "childrenAndBedsText": { "allowChildren": true, "childrenAtTheProperty": [ "..." ], "cribsAndExtraBeds": [ "..." ], "ageIntervals": [ ] }, "privateBathroomCount": 1 }
    ],
    "rateCount": 2,
    "rates": [
      { "blockId": "23778621_95438172_2_2_0", "roomId": 23778621, "name": "Classic King Room - Free cancellation", "roomName": "Classic King Room", "mealplan": "Breakfast ...", "breakfastIncluded": false, "refundable": true, "refundableUntil": "2026-11-30 23:59:59 -0400", "maxOccupancy": "2", "nrAdults": 2, "nrChildren": 0, "roomSurfaceInM2": 33, "productPriceBreakdown": { "grossAmount": { "value": 0, "currency": "USD", "amountRounded": "US$0" }, "items": [ "..." ], "chargesDetails": { "...": "..." }, "...": "..." }, "paymentterms": { "cancellation": { "type": "free_cancellation", "description": "...", "info": { "dateBefore": "...", "refundable": true } }, "prepayment": { "type": "no_prepayment", "description": "..." } }, "blockText": { "policies": [ { "class": "POLICY_CANCELLATION", "content": "..." } ] }, "...": "..." }
    ],
    "extras": { "pageviewId": "...", "...": "..." }
  }
}

(Heavily shortened - a real response is 50–60 KB for a property with availability. Field values above are illustrative; the field names are exact.)

Groups

Booleans (true/false) replace Booking.com's 0/1; empty strings are null; nothing else is removed or renamed beyond snake_case → camelCase.

10. Stays Description

What it does. The text of a property: the "About this property" description and the check-in rules / important information, in any language. It is what GET /stays/property-details leaves empty (its hotel_text). - See also: GET /stays/description-sections has the sectioned overview (Prime Location, Dining Options ...) that this text does not.

Where the inputs come from. Part 3 (About the property) in the journey overview. Pick a property from GET /stays/search and pass its id as hotelId. The fine print as structured fields (legal and trader details, licences) is in GET /stays/important-info.

Request

GET /api/v1/stays/description?hotelId=6966158&languageCode=en-us
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Description found",
  "data": {
    "hotelId": 6966158,
    "description": "Stay in the heart of New York.\nRiu Plaza Manhattan Times Square has a fitness centre, terrace, a restaurant and bar in New York. ...",
    "importantInformation": "Guests are required to show a photo identification and credit card upon check-in. ...",
    "count": 2,
    "descriptions": [
      { "typeId": 6, "type": "description", "languageCode": "en", "text": "Stay in the heart of New York.\n...", "extraLines": null, "extras": null },
      { "typeId": 7, "type": "importantInformation", "languageCode": "en", "text": "Guests are required to show a photo identification ...", "extraLines": { "importantInfo": "In the event of an early departure, the property will charge you the full amount for your stay.\n\n...", "extras": null }, "extras": null }
    ]
  }
}

Fields

11. Stays Description Sections

What it does. The property's description in the language you ask for, plus Booking.com's sectioned overview of the property: a short text with headings such as Prime Location, Comfortable Accommodations, Dining Options, Convenient Services and Nearby Attractions, already split into {title, text}.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId. See the journey overview.

Request

GET /api/v1/stays/description-sections?hotelId=6966158
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Description found",
  "data": {
    "description": "Riu Plaza Manhattan Times Square has a fitness centre, terrace, a restaurant and bar in New York. ...",
    "markupDescription": "<h2>Prime Location</h2>\n\nRiu Plaza Manhattan Times Square in New York City offers a central location ...",
    "hasOverview": true,
    "sections": [
      { "title": "Prime Location", "text": "Riu Plaza Manhattan Times Square in New York City offers a central location with Radio City Music Hall a 7-minute walk away, ..." },
      { "title": "Comfortable Accommodations", "text": "Rooms feature air-conditioning, private bathrooms, free WiFi, ..." },
      { "title": "Dining Options", "text": "The family-friendly restaurant serves American cuisine with vegetarian and gluten-free options. ..." }
    ]
  }
}

Fields

12. Stays Highlights (feature badges only)

What it does. The feature badges at the top of a property's page (this is only a summary strip, not the full detail - see the property endpoints linked below): "Pet friendly", "Breakfast", "Parking", "Wellness", "Accessibility", and so on, each with the specific facilities behind it (e.g. "Pet friendly" → "Pets welcome", "Charges may apply").

Where the inputs come from. Call GET /stays/search first; each item in its data.properties[] is a hotel. Take that hotel's own id and pass it here as hotelId — this is only the short badge strip at the top of a property page, NOT the full detail. For the rest of the property page see GET /stays/photos (all photos), GET /stays/important-info (fine print, legal) and GET /stays/property-details — same hotelId. For every photo of the property, see GET /stays/photos.

Request

GET /api/v1/stays/highlights?hotelId=59304
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Same auth, subscription and quota as /stays/search (one call = one request).

Deliberately not accepted here, unlike every other search-family endpoint: checkin, checkout, adults, rooms, childrenAges, currencyCode. All six were tested live and measured to have zero effect on this specific response — accepting-but-ignoring them would be misleading, so they are left out of the schema entirely rather than kept as optional no-ops.

What you get back

{
  "status": true,
  "message": "Highlights found",
  "data": {
    "categoryCount": 5,
    "categories": [
      {
        "id": 11,
        "icon": "food_coffee",
        "name": "Breakfast",
        "facilities": [
          { "id": 4000, "name": "Good breakfast", "extras": null }
        ],
        "extras": null
      },
      {
        "id": 12,
        "icon": "pawprint",
        "name": "Pet friendly",
        "facilities": [
          { "id": 5000, "name": "Pets welcome", "extras": null },
          { "id": 5001, "name": "Charges may apply", "extras": null }
        ],
        "extras": null
      },
      {
        "id": 9,
        "icon": "parking_sign",
        "name": "Parking",
        "facilities": [
          { "id": 2000, "name": "Private", "extras": null },
          { "id": 2001, "name": "Parking garage", "extras": null }
        ],
        "extras": null
      },
      {
        "id": 4,
        "icon": "spa",
        "name": "Wellness",
        "facilities": [
  ...

Fields

13. Stays Badges

What it does. The sustainability certifications of a property (Green Key, GSTC, LEED ...) and whether it carries the "Travel Proud" mark (Booking.com's LGBTQ+ welcoming programme).

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId. See the journey overview.

Request

GET /api/v1/stays/badges?hotelId=1150083
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Field names are Booking.com's own, under data.propertyDetails.

{
  "status": true,
  "message": "Badges found",
  "data": {
    "propertyDetails": {
      "propertySustainability": {
        "isSustainable": true,
        "certifications": [
          { "name": "Green Key Global Eco-Rating", "logoUrl": "https://q-xx.bstatic.com/xdata/images/xphoto/max2048/336195245.webp?k=...", "issuerDetails": [ { "name": "company_name_1", "value": "Control Union" } ] }
        ]
      },
      "travelProud": { "isTravelProud": true }
    }
  }
}

Fields

14. Stays House Rules

What it does. The check-in and check-out time windows of one property and its accepted payment methods (the credit cards it takes), as the app's "House rules" block shows them.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. See the journey overview.

Request

GET /api/v1/stays/house-rules?hotelId=1150083
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Field names are Booking.com's own, under data.houseRules.

{
  "status": true,
  "message": "House rules found",
  "data": {
    "houseRules": {
      "checkinCheckoutTimes": {
        "checkinTimeRange":  { "from": "15:00", "fromFormatted": "3:00 PM", "until": null, "untilFormatted": null },
        "checkoutTimeRange": { "from": null, "fromFormatted": null, "until": "12:00", "untilFormatted": "12:00 PM" }
      },
      "paymentMethods": {
        "acceptedCreditCards": [
          { "id": 1, "name": "American Express", "nameEn": "American Express" },
          { "id": 2, "name": "Visa", "nameEn": "Visa" },
          { "id": 3, "name": "Mastercard", "nameEn": "Euro/Mastercard" }
        ],
        "isExclusive": false,
        "isPropertyBookingManagedPayAtProperty": false
      }
    }
  }
}

Fields

IDs: a card id (1 American Express, 2 Visa, 3 Mastercard, 5 Diners Club, 7 JCB, 11 Discover, 44 UnionPay credit card) has no separate lookup; the name is in the same object. See ids.md.

15. Stays Important Info

What it does. The "Important information" part of a property page: fine print (deposit, ID at check-in, charges), the property's own extra notes, who legally runs the property (trader / company details), licence numbers, and the Polish consumer-authority text where it applies.

Where the inputs come from. Call GET /stays/search first; take a property's id and pass it here as hotelId, same as GET /stays/highlights, GET /stays/photos and GET /stays/property-details, GET /stays/review-filters, GET /stays/policies. See the journey overview for the full order.

Request

GET /api/v1/stays/important-info?hotelId=183564
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Important info found",
  "data": {
    "propertyDetails": {
      "propertyGallery": {
        "main": { "id": 753139154, "altText": "a building with flags in front of it at ...", "square60": { "absoluteUrl": "https://cf.bstatic.com/xdata/images/hotel/square60/753139154.jpg?k=..." } },
        "all": [ { "id": 753139154, "altText": "...", "square60": { "absoluteUrl": "..." } } ]
      },
      "finePrints": [
        "Guests are required to show a photo identification and credit card upon check-in. ...",
        "A damage deposit of US$250 is required on arrival. ..."
      ],
      "translation": { "finePrint": null },
      "legalInfo": {
        "traderInfo": {
          "isTrader": true,
          "legalEntityId": 186337,
          "contactDetails": {
            "address": { "addressLine1": "333 Ludlow Street", "addressLine2": "3rd Floor South Tower", "countryCode": "us", "city": "Stamford", "state": "CT", "postalCode": "06902" },
            "registrationNumber": "26-3069031",
            "tradeRegisterName": "Shared Mutual Services LLC Club Quarters",
            "companyLegalName": "Shared Mutual Services LLC",
            "firstName": null, "middleName": null, "lastName": null,
            "email": "crs@clubquarters.com",
            "phoneNumber": "+12039052083",
            "regulatorySubjectType": "BUSINESS"
          }
        }
      },
      "licenseData": { "numbers": [], "phrases": [] },
      "uokikSplitOfObligations": null
    }
  }
}

Fields

16. Stays Policies

What it does. A property's house rules: whether children are allowed and what cots / extra beds cost by age, group-booking rules, internet, parking, pets, the minimum check-in age, curfew, and the "Booking.com takes your payment" note.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as /stays/highlights, /photos, /property-details, /important-info, /review-filters and /reviews. See the journey overview.

Request

GET /api/v1/stays/policies?hotelId=59304
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Policies found",
  "data": {
    "hotelId": 59304,
    "policyGroups": [
      {
        "id": 246420356,
        "typeId": 1,
        "name": "General",
        "hotelId": 59304,
        "policyCount": 6,
        "policies": [
          {
            "type": "POLICY_CHILDREN",
            "key": "children",
            "id": 1234567891,
            "content": [
              {
                "text": "Children of any age are allowed.\n1 child (up to and including 2 years old) stays for free when using available cots.\t\n...",
                "languageCode": "en-gb",
                "allowChildren": true,
                "childrenAtTheProperty": [ { "text": "Children of any age are welcome.", "highlight": false } ],
                "cribsAndExtraBeds": [ { "text": "Supplements are not calculated automatically in the total costs ...", "highlight": false } ],
                "ageIntervals": [
                  { "minAge": 0, "maxAge": 2, "crib": { "id": 57224089, "price": 0, "priceType": "free", "priceMode": "per_stay", "priceTypeN": 0, "priceModeN": 1, "guaranteed": false }, "typesByPrice": [["crib"], ["existing_bed"]], "groupByPrice": [ { "priceType": "free", "priceMode": "per_stay", "price": "0", "types": ["crib"], "key": "free,per_stay,0" } ] },
                  { "minAge": 3, "maxAge": 11, "extraBed": { "id": 57224088, "price": "US$35", "priceType": "fixed", "priceMode": "per_night" } }
                ]
              }
            ],
            "extras": null
          },
          { "type": "POLICY_HOTEL_PETS", "key": "hotelPets", "id": 1234567891, "content": [ { "text": "Pets are allowed on request. No extra charges.\n", "languageCode": "en-gb" } ], "extras": null },
          { "type": "POLICY_AGE_RESTRICTION", "key": "ageRestriction", "id": null, "content": [ { "text": "The minimum age for check-in is 21", "languageCode": "en-gb" } ], "extras": null }
        ],
        "extras": null
      }
    ]
  }
}
  ...

(Shortened; a real response has every policy the property has.)

Fields

The 0/1 flags (highlight, allowChildren, allowExistingBeds, allowsCribs, allowsExtraBeds, guaranteed, onlyFreeExistingBedRules) are returned as booleans.

17. Stays Rooms (room list)

What it does. Every room type and every rate of a property for the dates and guests you choose: all rooms with size, beds, facilities, highlights and photos, and all rates with price breakdown, meal plan, cancellation and prepayment terms, plus which rates the app recommends for your guests. It is the app's room list.

Where the inputs come from. Part 3 (Rooms and prices) in the journey overview. Pick a property from GET /stays/search, pass its id as hotelId with the same dates and guests. GET /stays/property-details answers with the property page and only the 1-2 rooms and rates the app recommends for the guests; this endpoint returns all of them (for hotel 6966158, 4 adults + 2 children in 2 rooms: 2 rates there, 50 rates in 7 rooms here). This endpoint returns only the room types that can be booked; to also list the sold-out ones use GET /stays/room-types. The IDs in the response are explained in ids.md.

Request

GET /api/v1/stays/rooms?hotelId=6966158&checkin=2026-10-22&checkout=2026-10-23&adults=4&rooms=2&childrenAges=0,3&currencyCode=INR
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Rooms found",
  "data": {
    "hotelId": 6966158,
    "availability": { "checkin": "2026-10-22", "checkout": "2026-10-23", "propertyCurrencyCode": "USD", "requestedCurrencyCode": "INR", "totalRates": 50, "maxRoomsPerBooking": 10, "duplicateRatesRemoved": false, "lastMatchingRateIndex": -1, "soldOutRooms": [] },
    "pricing": { "cheapestAvailablePriceEur": 1048.54, "paidMeals": [] },
    "policies": {
      "cancellation": [ { "blockId": "696615804_287466585_2_1_0_1457283", "policy": "non_refundable" } ],
      "prepayment": [ { "blockId": "696615801_287466585_2_0_0_1457283", "policy": "no_prepayment_at_all" } ],
      "displayDetails": { "legalCases": null }, "directPayment": { "isHppOnly": false }, "paymentDetail": { "model": "hybrid2.0" },
      "creditCardRequired": true, "cvcRequired": true, "noCreditCardReservation": false, "addressRequired": false, "isCpv2Property": true, "useNeutralColorForLegal": false
    },
    "recommendation": {
      "title": "2 rooms for 4 adults, 2 children (< 1 and 3 years old)",
      "rooms": [ { "blockId": "696615802_287466585_4_0_0_1457283", "adults": 4, "children": 1, "babies": 0, "totalExtraBedPrice": 0, "totalExtraBedPriceInHotelCurrency": 0 } ],
      "guestsPerRoom": { "adults": 2, "children": [ 3 ] },
      "childrenStayFree": [ { "blockId": "696615801_287466585_2_0_0_1457283", "title": null, "content": null, "class": null } ],
      "aiDescription": "This option has these additional features compared to Deluxe King .",
      "selection": {
        "roomCount": 2,
        "rooms": [
          { "blockId": "696615802_287466585_4_0_0_1457283", "roomId": 696615802, "roomName": "Deluxe Two Queen Beds", "rateName": "Deluxe Two Queen Beds - Non-refundable", "mealplan": "There is no meal option with this room.", "refundable": false, "refundableUntil": null, "maxOccupancy": 4,
            "price": { "grossAmount": { "value": 50327.37, "currency": "INR", "amountRounded": "₹ 50,327", "amountUnrounded": "₹ 50,327.37" }, "excludedAmount": { "value": 7756.33, "currency": "INR" }, "allInclusiveAmount": { "value": 58083, "currency": "INR" }, "...": "also grossAmountPerNight, strikethroughAmount, discountedAmount, includedTaxesAndChargesAmount" } },
          { "blockId": "696615801_287466585_2_0_0_1457283", "roomId": 696615801, "roomName": "Deluxe King ", "rateName": "Deluxe King  - Non-refundable", "maxOccupancy": 2, "price": { "grossAmount": { "value": 46729.57, "currency": "INR" }, "allInclusiveAmount": { "value": 53954.53, "currency": "INR" } } }
        ],
        "total": { "grossAmount": { "value": 97056.94, "currency": "INR" }, "excludedAmount": { "value": 14980.58, "currency": "INR" }, "allInclusiveAmount": { "value": 112037.53, "currency": "INR" }, "strikethroughAmount": { "value": 132659.84, "currency": "INR" }, "discountedAmount": { "value": 35602.9, "currency": "INR" } }
      }
    },
    "roomCount": 7,
    "rooms": [
      { "roomId": 696615801, "roomName": "Deluxe King ", "roomSurfaceInM2": 18, "roomSurfaceInFeet2": 193.75, "description": "The double room features air conditioning, ...", "onlyXLeftMessage": "We have 4 left", "isDormitory": false, "smoking": false, "numberOfBathrooms": 0,
        "bedConfigurations": [ { "bedTypes": [ { "bedType": 3, "name": "Extra-large double bed(s)", "count": 1, "nameWithCount": "1 extra-large double bed", "description": "181-210 cm wide" } ] } ],
        "facilities": [ { "id": 81, "name": "View", "facilitytypeId": 9, "altFacilitytypeId": 14, "altFacilitytypeName": "View" } ],
        "highlights": [ { "id": 11, "translatedName": "Air conditioning", "icon": "snowflake" } ],
        "photos": [ { "photoId": 280458367, "urlOriginal": "https://...", "urlMax1280": "https://..." } ],
        "blockIds": { "occupancyMatch": [], "nonOccupancyMatch": [ "696615801_287466585_2_0_0_1457283", "..." ], "allMatch": [], "sharedDormitories": [] } }
    ],
    "rateCount": 50,
    "rates": [
  ...

(The example is trimmed; the real response has all 7 rooms and 50 rates with the full price breakdowns.)

Fields

18. Stays Room Types (available and sold out)

What it does. Every room type of a property for your dates and guests, each marked available or sold out. If a hotel has a Suite, a Deluxe and a Special Deluxe and only the Suite can be booked tomorrow, you get all three: the Suite with its price, the other two named and marked sold out. How many individual rooms each type has is not part of it, and not available from Booking.com.

Where the inputs come from. Part 3 (Rooms and prices) in the journey overview. Pick a property from GET /stays/search, pass its id as hotelId with the dates and guests. For the rates, prices and conditions of the available types use GET /stays/rooms (the id here is that endpoint's roomId); GET /stays/rooms alone returns only the types that can be booked.

Request

GET /api/v1/stays/room-types?hotelId=6966158&checkin=2026-11-03&checkout=2026-11-04&adults=2&rooms=1&currencyCode=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Room types found",
  "data": {
    "hotelId": 6966158,
    "checkin": "2026-11-03",
    "checkout": "2026-11-04",
    "requestedCurrencyCode": "USD",
    "roomTypeCount": 7,
    "availableCount": 4,
    "soldOutCount": 3,
    "roomTypes": [
      {
        "id": 696615803, "name": "Deluxe Family King", "isAvailable": true, "photoCount": 4,
        "photos": [ { "id": 342959732, "thumbnail": "https://cf.bstatic.com/xdata/images/hotel/square60/342959732.jpg?k=...", "medium": "https://cf.bstatic.com/xdata/images/hotel/max500/342959732.jpg?k=...", "large": "https://cf.bstatic.com/xdata/images/hotel/max1024x768/342959732.jpg?k=..." }, "... (photoCount photos)" ],
        "availability": { "rateCount": 4, "cheapestPrice": { "allInclusiveAmount": 622.56, "grossAmount": 539.49, "currency": "USD" }, "leftMessage": null, "sizeM2": 20 }
      },
      { "id": 696615802, "name": "Deluxe Two Queen Beds", "isAvailable": true, "photoCount": 4, "photos": [ "..." ], "availability": { "rateCount": 4, "cheapestPrice": { "allInclusiveAmount": 633.43, "grossAmount": 548.96, "currency": "USD" }, "leftMessage": "We have 5 left", "sizeM2": 21 } },
      { "id": 696615801, "name": "Deluxe King", "isAvailable": false, "photoCount": 4, "photos": [ "..." ], "availability": null }
    ]
  }
}

Fields

19. Stays Facilities

What it does. The facility list of a property, as the app's Facilities screen shows it: the total number of facilities, the top facilities for the trip, every facility with its opening hours (restaurants), pool details, whether it is free or paid and its sub-facilities, the facility groups and the ten most popular facilities. - See also: GET /stays/food-and-drink has the restaurant details (cuisine, atmosphere, meal types), the breakfast and the other meals.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. See the journey overview.

Request

GET /api/v1/stays/facilities?hotelId=6966158
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Field names are Booking.com's own, under data.propertyDetails.

{
  "status": true,
  "message": "Facilities found",
  "data": {
    "propertyDetails": {
      "facilitiesCount": 76,
      "accommodationHighlights": [
        { "entities": [ { "type": "WifiFacilityHighlight", "icon": "internet", "title": "Free WiFi" } ] }
      ],
      "facilities": [
        { "id": 109, "icon": "weather_snowflake", "groupId": 1, "slug": "airconditioning", "groupTitle": "General",
          "instances": [ { "title": "Air conditioning", "subFacilities": [],
            "attributes": { "name": null, "isOffsite": false, "paymentInfo": { "chargeMode": "FREE" },
              "closureScheduleDuringStay": [], "scheduleEntry": [], "extendedAttributes": null } } ] },
        { "id": 3, "icon": "food", "groupId": 7, "groupTitle": "Food & Drink",
          "instances": [ { "title": "Restaurant", "subFacilities": [],
            "attributes": { "name": "Park Avenue", "isOffsite": false, "paymentInfo": null, "closureScheduleDuringStay": [],
              "scheduleEntry": [ { "from": { "hours": 7, "minutes": 0 }, "to": { "hours": 10, "minutes": 0 }, "dayOfWeek": "MONDAY" } ],
              "extendedAttributes": {} } } ] }
      ],
      "facilityGroups": [ { "id": 11, "title": "Internet", "icon": "wifi", "summary": "WiFi is available in all areas and is free of charge." } ],
      "highlights": { "entities": [
        { "type": "BaseFacility", "id": 47, "groupId": 11, "groupTitle": "Internet", "icon": "internet", "instances": [ { "title": "Internet services" } ] },
        { "type": "Meal" }
      ] }
    }
  }
}

Fields

IDs: facilities[].id and groupId are the same numbers as in /stays/property-facilities and in the room facilities of /stays/rooms; see ids.md.

20. Stays Property Facilities

What it does. The facility catalog of a property and a few id lists: the facility groups and facilities (with prices where a facility is charged, e.g. internet or parking per day), the amenity ids of each room type, the languages spoken, whether it is a Booking.com Homes listing, the Q&A question ids and the gallery photos grouped by tag. This is what GET /stays/property-details returned before 2026-10-19. That route is now the property detail page (stays-property-details.md); this data moved here unchanged. - See also: GET /stays/facilities has the same facilities plus restaurant opening hours, pool details, sub-facilities and the ten most popular facilities, but no prices; use this endpoint when you need facility prices, room amenities or languages spoken. - See also: the question and answer text behind questionsAndAnswers.questionIds is in GET /stays/questions.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. See the journey overview.

Request

GET /api/v1/stays/property-facilities?hotelId=59304
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Property details found",
  "data": {
    "languagesSpoken": ["en", "hi", "mr"],
    "isBookingHome": false,
    "facilityGroupCount": 45,
    "facilityGroups": [ { "id": 12, "title": "Internet", "icon": "wifi", "summary": "...", "extras": null } ],
    "facilityCount": 109,
    "facilities": [
      { "id": 46, "icon": "wifi", "groupId": 12, "groupTitle": "Internet",
        "instances": [ { "title": "WiFi is available in all areas and is free of charge", "summary": "...", "name": "...", "isOffsite": false, "charge": null, "extras": null } ],
        "extras": null }
    ],
    "roomCount": 8,
    "rooms": [ { "id": 5930456, "amenities": [ { "id": 11, "groupId": 3, "groupTitle": "Bathroom", "icon": "bath", "instances": [ "..." ], "extras": null } ] } ],
    "questionsAndAnswers": { "partnerOptedOut": false, "questionIds": [1915675] },
    "photoTags": [ { "tagId": 7, "photos": [ { "id": 607956163, "altText": "...", "photoType": "PROPERTY", "imageUrl": "...", "images": { "thumbnail": "...", "medium": "...", "large": "..." }, "extras": null } ] } ]
  }
}

status says whether the property resolved, not whether the groups came back non-empty: an empty result for a narrow facilityGroupIds filter is a normal answer.

Fields

21. Stays Food and Drink

What it does. Everything about eating at a property, as the app's "Food & drink" block shows it: breakfast and the other meals (included or paid, the price, buffet or à la carte, the menu, the opening time and a food score from guests), the restaurants (name, cuisine, atmosphere, meal types, buffet / à la carte, which meals it is open for), and the food facilities (bar, snack bar, minimarket, wine, fruit ...) and food amenities in the room (fridge, coffee machine ...).

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId. See the journey overview.

Request

GET /api/v1/stays/food-and-drink?hotelId=6966158&currencyCode=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Field names are Booking.com's own, under data.propertyDetails.

{
  "status": true,
  "message": "Food and drink found",
  "data": {
    "propertyDetails": {
      "accommodationType": { "type": "HOTEL", "flags": { "isSingleTypeProperty": false } },
      "foodFacilities": [ { "id": 7, "groupId": 7, "slug": "bar", "instances": [ { "title": "Bar" } ] } ],
      "foodAmenities": [ { "id": 22, "groupId": 12, "slug": "refrigerator", "instances": [ { "title": "Refrigerator" } ] } ],
      "meals": [
        { "offer": "INCLUDED", "mealType": "BREAKFAST", "price": null,
          "attributes": { "foodMenu": [], "style": ["Buffet"], "cuisine": [], "dietary": [], "drinks": [],
            "openingTime": { "startTime": "07:00", "endTime": "10:00" },
            "foodScore": { "score": 8.8, "nReviews": 134 },
            "photo": "/xdata/images/hotel/max400/342959701.jpg?k=...", "photoUrl": "https://cf.bstatic.com/xdata/images/hotel/max400/342959701.jpg?k=..." } }
      ],
      "restaurants": [
        { "id": 3, "groupId": 7, "slug": "restaurant",
          "instances": [ { "title": "Restaurant",
            "attributes": { "name": "Park Avenue",
              "extendedAttributes": { "ambiances": [ { "name": "Family friendly" }, { "name": "Modern" } ], "cuisines": [ { "name": "American" } ],
                "mealTypes": [ { "name": "Vegetarian" }, { "name": "Gluten-free" } ], "openForMeals": [ { "name": "Breakfast" } ], "isBuffet": true, "isAlacarte": false } } } ] }
      ]
    }
  }
}

Fields

22. Stays Photos

What it does. Every photo of a property: the main gallery (with tags) plus each room's own photos, each in three sizes. - See also: GET /stays/photo-list is a lighter list of the same photos with the aspect ratio (ratio), the rooms of each photo as a flat list and more sizes; the alt texts and AI tags are only here.

Where the inputs come from. Call GET /stays/search first; take a property's id and pass it here as hotelId, same as GET /stays/highlights and GET /stays/property-details. Property-details also returns photos, but only grouped by tag and with no room grouping; this endpoint is the full photo grid.

Request

GET /api/v1/stays/photos?hotelId=183564
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Same auth, subscription and quota as /stays/search (one call = one request).

Not accepted: dates, guests, currencyCode, gallery limit (see above).

What you get back

{
  "status": true,
  "message": "Photos found",
  "data": {
    "photoCount": 145,
    "photos": [
      {
        "id": 753139154,
        "altText": "a building with flags in front of it at Club Quarters Hotel World Trade Center, New York in New York",
        "photoType": "PROPERTY",
        "images": {
          "thumbnail": "https://cf.bstatic.com/xdata/images/hotel/square60/753139154.jpg?k=...&o=",
          "medium": "https://cf.bstatic.com/xdata/images/hotel/max500/753139154.jpg?k=...&o=",
          "large": "https://cf.bstatic.com/xdata/images/hotel/max1024x768/753139154.jpg?k=...&o="
        },
        "tags": [{ "id": 3, "name": "Property building" }],
        "aiTags": [],
        "extras": null
      }
    ],
    "roomCount": 18,
    "rooms": [
      {
        "id": 18356401,
        "name": "Standard Queen Room",
        "photoCount": 13,
        "photos": [
          {
            "id": 583896226,
            "altText": "Gallery image of Club Quarters Hotel World Trade Center, New York in New York",
            "photoType": "ROOM",
            "images": { "thumbnail": "...", "medium": "...", "large": "..." },
            "tags": [{ "id": 13, "name": "Bed" }, { "id": 154, "name": "TV and multimedia" }],
            "aiTags": [{ "id": 13, "name": "Bed", "confidence": 100 }],
            "extras": null
          }
        ]
      }
    ]
  }
  ...

Fields

23. Stays Photo List

What it does. A compact list of a property's photos: for every photo its aspect ratio, the rooms it shows, its tags and six image sizes. It is the light, fast sibling of GET /stays/photos (the same photos, 55 for hotel 6966158) and adds one thing that endpoint cannot give: the aspect ratio, so a gallery can reserve the right space before an image loads.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId. See the journey overview.

Request

GET /api/v1/stays/photo-list?hotelId=6966158
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Photos found",
  "data": {
    "hotelId": 6966158,
    "photoCount": 55,
    "photos": [
      { "photoId": 598995411, "ratio": 1.54428, "filters": ["room:696615817"], "roomIds": [696615817],
        "tags": [ { "id": 159, "tag": "Living room" }, { "id": 1000000001, "tag": "Property" } ],
        "images": { "square60": "https://cf.bstatic.com/xdata/images/hotel/square60/598995411.jpg?k=...",
                    "square90": "...", "max300": "...", "max500": "...", "max1024": "...", "max1280": "..." },
        "extras": null }
    ],
    "extras": null
  }
}

Fields

24. Stays Review Photos

What it does. The highlighted photos guests attached to their reviews for a property: up to five photos, each in four sizes, with the id of the review it belongs to and the date it was added. It is the photo strip the app shows in the reviews section.

Where the inputs come from. Part 3 (Photos) in the journey overview. Pick a property from GET /stays/search and pass its id as hotelId. Use the reviewId of a photo to find its review text in GET /stays/reviews; the official property photos are in GET /stays/photos.

Request

GET /api/v1/stays/review-photos?hotelId=6966158
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Review photos found",
  "data": {
    "hotelId": 6966158,
    "count": 5,
    "photos": [
      {
        "id": 551521325,
        "reviewId": 5181440717,
        "photoCreatedAt": "2025-07-16",
        "urls": [
          { "size": "max500_ao", "url": "https://r-xx.bstatic.com/xdata/images/xphoto/max500_ao/551521325.jpg?k=..." },
          { "size": "square60_ao", "url": "https://r-xx.bstatic.com/xdata/images/xphoto/square60_ao/551521325.jpg?k=..." },
          { "size": "square90", "url": "https://r-xx.bstatic.com/xdata/images/xphoto/square90/551521325.jpg?k=..." },
          { "size": "max1280x900", "url": "https://r-xx.bstatic.com/xdata/images/xphoto/max1280x900/551521325.jpg?k=..." }
        ],
        "extras": null
      }
    ]
  }
}

Fields

25. Stays Review Scores

What it does. How guests scored a property: the overall score, the scores per category (cleanliness, comfort, facilities, location, staff, value for money, WiFi), the same split by guest type (couples, families, solo travellers, ...), how many reviews fall in each score band (Superb, Good, Okay, Poor, Very poor) and how many reviews gave each whole score from 1 to 10.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. The review texts are in GET /stays/reviews; the sort/filter menus and counts are in GET /stays/review-filters. See the journey overview.

Request

GET /api/v1/stays/review-scores?hotelId=183564
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Review scores found",
  "data": {
    "hotelId": 183564,
    "overall": {
      "customerType": "total",
      "averageScore": 8.7,
      "reviewCount": 3221,
      "fromYear": 2023,
      "categories": [
        { "id": "hotel_clean", "label": "Cleanliness", "score": 8.8, "reviewCount": 3157, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_comfort", "label": "Comfort", "score": 8.9, "reviewCount": 3160, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_services", "label": "Facilities", "score": 8.6, "reviewCount": 3166, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_location", "label": "Location", "score": 9.4, "reviewCount": 3156, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_staff", "label": "Staff", "score": 9, "reviewCount": 3164, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "total", "label": "Total", "score": 8.5, "reviewCount": 3221, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_value", "label": "Value for money", "score": 8.2, "reviewCount": 3159, "comparisonToDestinationAverage": 0, "extras": null },
        { "id": "hotel_wifi", "label": "WiFi", "score": 8.3, "reviewCount": 102, "comparisonToDestinationAverage": 0, "extras": null }
      ],
      "extras": null
    },
    "guestTypes": [
      { "customerType": "family", "averageScore": 8.6, "reviewCount": 1362, "fromYear": 2023, "categories": [ "..." ], "extras": null },
      { "customerType": "couple", "averageScore": 8.7, "reviewCount": 928, "fromYear": 2023, "categories": [ "..." ], "extras": null }
    ],
    "scoreBands": [
      { "label": "Superb", "from": 9, "to": 10.1, "reviewCount": 1763, "percent": 55, "extras": null },
      { "label": "Good", "from": 7, "to": 9, "reviewCount": 1147, "percent": 36, "extras": null }
    ],
    "scoreDistribution": [
      { "score": 1, "reviewCount": 45, "percent": 1.4, "extras": null },
      { "score": 10, "reviewCount": 1025, "percent": 31.82, "extras": null }
    ],
    "extras": null
  }
}

(Shortened: a real response has all 8 categories for every group, every guest type, 5 bands and 10 scores.)

Fields

26. Stays Review Score Comparison

What it does. The review categories of a property (Cleanliness, Comfort, Facilities, Location, Staff, Value for money, Free WiFi) with the exact (unrounded) score and the range that the other properties of the same destination score in. It answers "is 9.2 for cleanliness good for this city?".

Where the inputs come from. Part 3 (Reviews, scores and questions) in the journey overview, next to GET /stays/review-scores. Pick a property from GET /stays/search, pass its id as hotelId, and the hotel's city as destination: city:<location.cityId> of the same GET /stays/search result (no extra call), or city:<location.destinationId> of GET /stays/property-details.

Request

GET /api/v1/stays/review-score-comparison?hotelId=6966158&destination=city:20088325&languageCode=en-us
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Review score comparison found",
  "data": {
    "hotelId": 6966158,
    "destinationId": 20088325,
    "categoryCount": 7,
    "categories": [
      { "id": "hotel_clean", "label": "Cleanliness", "score": 9.19564151763916, "destinationAverage": { "lowerBound": 7.640125274658203, "higherBound": 9.253375053405762 }, "extras": null },
      { "id": "hotel_comfort", "label": "Comfort", "score": 9.298111915588379, "destinationAverage": { "lowerBound": 7.688374996185303, "higherBound": 9.301799774169922 }, "extras": null },
      { "id": "hotel_services", "label": "Facilities", "score": 8.906320571899414, "destinationAverage": { "lowerBound": 7.2856245040893555, "higherBound": 8.964300155639648 }, "extras": null },
      { "id": "hotel_location", "label": "Location", "score": 9.69638442993164, "destinationAverage": { "lowerBound": 8.476824760437012, "higherBound": 9.78427505493164 }, "extras": null },
      { "id": "hotel_staff", "label": "Staff", "score": 9.137491226196289, "destinationAverage": { "lowerBound": 7.994899749755859, "higherBound": 9.368974685668945 }, "extras": null },
      { "id": "hotel_value", "label": "Value for money", "score": 8.38898754119873, "destinationAverage": { "lowerBound": 7.173224449157715, "higherBound": 8.66717529296875 }, "extras": null },
      { "id": "hotel_free_wifi", "label": "Free WiFi", "score": 9.228316307067871, "destinationAverage": { "lowerBound": 7.897200107574463, "higherBound": 9.088449478149414 }, "extras": null }
    ]
  }
}

Fields

27. Stays Featured Reviews

What it does. The review overview at the top of a property's reviews: a title ("Guests who stayed here loved") and ten featured reviews, each with the guest (name, country, guest type, how many reviews they wrote) and the review text (title, what they liked, what they did not like). For the full list with paging, sorting and filters use GET /stays/reviews; for the scores use GET /stays/review-scores.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId. To feature only the guests of one room, pass roomId (a rooms[].id from GET /stays/property-details). See the journey overview.

Request

GET /api/v1/stays/featured-reviews?hotelId=183564
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Featured reviews found",
  "data": {
    "hotelId": 183564,
    "roomId": null,
    "title": "Guests who stayed here loved",
    "count": 10,
    "reviews": [
      {
        "id": 5343489281,
        "score": 10,
        "isNonStayedReview": false,
        "guest": { "name": "Cecilia", "avatarUrl": "https://xx.bstatic.com/static/img/review/avatars/ava-c.png", "countryCode": "us", "country": "United States", "showCountryFlag": true, "isAnonymous": false, "isGenius": null, "type": "Couple", "reviewCount": 14, "joinedDate": null },
        "text": { "title": "I’ve stayed before, will stay again.", "positive": "Quiet and convenient location, easy check-in/out, comfortable beds, nice bathrooms, and spacious for just me!", "negative": "The carpets in the rooms need refreshing or replacing. Stains and stick spots.", "languageCode": "xu", "isTrivial": false },
        "translation": null
      }
    ]
  }
}

Fields

28. Stays Review Filters

What it does. The menus of a property's reviews page: how many reviews it has, the sort options (most relevant, newest, oldest, highest/lowest scores) and four filter menus - guest type, review language, time of year and topics - each option with its id and how many reviews match it. Review scores are in GET /stays/review-scores. This is the review metadata, not the review texts. The ids it returns are what GET /stays/reviews takes to sort and filter (sortBy, customerType, reviewLanguages, topicIds, timeOfYear).

Where the inputs come from. Call GET /stays/search first; take a property's id and pass it here as hotelId, same as /stays/highlights, /stays/photos, /stays/property-details and /stays/important-info. See the journey overview for the whole order.

Request

GET /api/v1/stays/review-filters?hotelId=183564
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Review filters found",
  "data": {
    "hotelId": 183564,
    "totalReviews": 3221,
    "sort": {
      "id": "user_sort",
      "title": "Sort by:",
      "options": [
        { "id": "sort_most_relevant", "label": "Most relevant", "extras": null },
        { "id": "sort_recent_desc", "label": "Newest first", "extras": null },
        { "id": "sort_recent_asc", "label": "Oldest first", "extras": null },
        { "id": "sort_score_desc", "label": "Highest scores", "extras": null },
        { "id": "sort_score_asc", "label": "Lowest scores", "extras": null }
      ],
      "extras": null
    },
    "filterCount": 4,
    "filters": [
      {
        "id": "filter_customer_type",
        "title": "Filter by:",
        "type": "radio_button",
        "defaultLabel": "All reviews",
        "defaultLabelWithCount": "All reviews (3221)",
        "optionCount": 4,
        "options": [
          { "id": "couple", "label": "Couple", "labelWithCount": "Couple (928)", "count": 928, "extras": null },
          { "id": "family_with_children", "label": "Family", "labelWithCount": "Family (1362)", "count": 1362, "extras": null }
        ],
        "extras": null
      }
    ],
    "extras": null
  }
}

(filters is shortened above; a real response has all four.)

Fields

29. Stays Reviews

What it does. One page of a property's guest reviews: score, title, what they liked and disliked, who the guest is, the room they stayed in, their photos and the hotel's reply. The short overview with featured reviews is GET /stays/featured-reviews. Overall and per-category scores are in GET /stays/review-scores. Sort and filter with the ids from GET /stays/review-filters.

Where the inputs come from. Pick a property from GET /stays/search (its id is hotelId). Call GET /stays/review-filters first if you want the review total, the sort ids and the filter options with their counts; then call this with those ids. See the journey overview for the whole order.

Request

GET /api/v1/stays/reviews?hotelId=183564&sortBy=sort_recent_desc&customerType=couple&page=1&pageSize=25
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Reviews found",
  "data": {
    "page": 1,
    "pageSize": 25,
    "count": 25,
    "hasNextPage": true,
    "sortOptions": [
      { "id": "sort_most_relevant", "label": "Most relevant", "isDefault": true, "extras": null },
      { "id": "sort_recent_desc", "label": "Date (newer to older)", "isDefault": false, "extras": null }
    ],
    "reviews": [
      {
        "id": 5354374431,
        "hash": "c271fcf0cde7b344",
        "hotelId": 183564,
        "date": "2026-10-18 02:29:59",
        "score": 3.6,
        "title": "I would go back again",
        "titleTranslated": null,
        "titleIsGenerated": false,
        "pros": "The room and the bed were better than in other CQ ...",
        "prosTranslated": null,
        "cons": "The staff member I dealt with on the day I checked out was not very nice. ...",
        "consTranslated": null,
        "languageCode": "en-us",
        "countryCode": "us",
        "travelPurpose": "leisure",
        "stayStatus": "stayed",
        "anonymous": null,
        "isIncentivised": false,
        "isModerated": false,
        "helpfulVoteCount": 0,
        "author": { "name": "Maria", "userId": 967191017, "countryCode": "us", "avatar": "https://...", "reviewCount": 0, "type": "family_with_children", "typeLabel": "Family", "city": null, "helpfulVoteCount": 0, "extras": null },
        "stayedRoom": {
          "roomId": 18356408, "roomName": "Mobility Accessible Standard Room",
          "checkin": "2026-09-05", "checkout": "2026-09-07", "nights": 2,
          "photo": { "id": 280834956, "ratio": 1.5, "images": { "square60": "...", "max300": "...", "max500": "...", "wide640x200": "..." }, "extras": null },
          "extras": null
  ...

Fields

30. Stays Questions

What it does. The guest questions of a property with the property's answers, in one language per call - the app's "Questions and answers" screen: the question, the answer, how many guests found it useful (votes), when it was asked and answered, which room it is about, and how fast the property usually answers. One call returns the questions of one language, all in one response (hotel 1169919: 1,150 in English), most-voted first. No single language holds every question of a property: that hotel has 1,589 across languages (see below).

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. See the journey overview.

Request

GET /api/v1/stays/questions?hotelId=6966158
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Questions found",
  "data": {
    "hotelId": 6966158,
    "optedOut": false,
    "collectsQuestions": true,
    "averageResponseTime": { "text": "Subject to availability at the property", "summary": "This property usually replies within a few days", "seconds": 8887804 },
    "questionCount": 199,
    "questions": [
      { "questionId": 24492748, "question": "Hi do you take visa debit?", "translatedQuestion": null,
        "answer": "Yes visa, mastercard, american express, discover ...", "translatedAnswer": null, "votes": 60,
        "roomId": 696615801, "roomName": null, "language": "en",
        "askedAt": "2022-05-12 23:07:01", "askedAtEpoch": 1652396821, "answeredAt": "2022-05-13 10:12:44", "answeredAtFormatted": "2022-05-13 10:12:44", "answeredAtEpoch": 1652436764,
        "hidden": false, "isOrCouldBeTranslated": null, "signOff": null, "naiveSentiment": 52,
        "extras": { "pxUpsortCovidQAndADsModelWouldResort": 1 } }
    ],
    "extras": null
  }
}

Fields

31. Stays Surroundings

What it does. What is around a property, as the app's "Surroundings" block shows it, in 11 lists: top landmarks, nearby landmarks, beaches, ski lifts, restaurants, cafes and bars, supermarkets, bus stops, metro stops, train stations and airports. Every item has its distance and the walking and driving time and distance.

Where the inputs come from. Pick a property from GET /stays/search and pass its id as hotelId, same as the other property endpoints. See the journey overview.

Request

GET /api/v1/stays/surroundings?hotelId=1150083&languageCode=en-gb&limit=5&maxDistanceKm=25
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

Field names are Booking.com's own, under data.propertySurroundings.

{
  "status": true,
  "message": "Surroundings found",
  "data": {
    "propertySurroundings": {
      "landmarks": {
        "top": [ { "id": "77788", "name": "Rockefeller Center", "latitude": 40.758677, "longitude": -73.978533, "distance": 1.496,
                   "commute": { "best": { "commuteType": "ByFoot", "commuteDetails": { "distanceLocalized": "1.7 km", "distanceMeters": 1744, "timeLocalized": "20 min", "timeMillis": 1255837 } }, "byFoot": { "distanceLocalized": "1.7 km", "distanceMeters": 1744, "timeLocalized": "20 min", "timeMillis": 1255837 },
                                "byCar":  { "distanceLocalized": "2.2 km", "distanceMeters": 2179, "timeLocalized": "2 min", "timeMillis": 165865 } } } ],
        "nearby": [ "..." ]
      },
      "beaches": [], "skiSurroundings": { "lifts": [] },
      "dining": { "restaurants": [ "..." ], "cafeBars": [ "..." ] },
      "supermarkets": [ "..." ],
      "publicTransport": { "bus": [], "metro": [ "..." ], "train": [ "..." ] },
      "airports": [ "..." ]
    }
  }
}

Fields

32. Stays Things To Do

What it does. The "Things to do" carousel the app shows on a property page: five bookable attractions (tours, tickets, admissions) near a city or map point, each with its name, a "From" price, "Free cancellation available", a badge such as "Bestseller", a photo and a link to book. It also returns the "See all" link and the "Good to know" footnote. The full list behind "See all", with filters, sorting and paging, is GET /attractions/search.

Where the inputs come from. Part 3 (Around the property) in the journey overview. It takes a place, not a hotelId: a city (city:<id>, from GET /stays/autocomplete) or a map point. For a property from GET /stays/search, take its coordinates (location.latitude, location.longitude) or its location.destinationId from GET /stays/property-details: latlong:<latitude>,<longitude> or city:<destinationId>.

Request

GET /api/v1/stays/things-to-do?destination=city:20088325&checkin=2026-12-01&checkout=2026-12-03&currencyCode=USD&languageCode=en-us
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Things to do found",
  "data": {
    "datesAreDefault": false,
    "checkin": "2026-10-22",
    "checkout": "2026-10-23",
    "title": "Things to do",
    "distributionId": "2OIAFHV1r6MkX8RHL8bcu",
    "seeAll": { "text": "See all", "url": "https://ch.booking.com/c?target=...", "webUrl": "https://www.booking.com/attractions/searchresults/us/new-york.en-gb.html?end_date=2026-10-23&selected_currency=INR&dest_id=20088325&start_date=2026-10-22&..." },
    "footnote": { "text": "Certain conditions apply.", "linkText": "Show details", "details": { "title": "Good to know", "points": [ "Free cancellation policy may change based on the booking dates you select." ], "dismissText": "Got it" } },
    "attractionCount": 5,
    "attractions": [
      {
        "id": "PRCMOkYUz7Um",
        "rank": 1,
        "vertical": "ATTRACTION",
        "name": "SUMMIT One Vanderbilt Tickets",
        "perks": [ "Free cancellation available" ],
        "badges": [ { "text": "Bestseller", "variant": "brand_primary" } ],
        "price": { "label": "From", "amount": "₹ 4,549", "originalAmount": null, "text": "From ₹ 4,549" },
        "image": { "url": "https://r-xx.bstatic.com/xdata/images/xphoto/300x320/662759882.jpg?k=...", "aspectRatio": 1.5 },
        "url": "https://ch.booking.com/c?target=...",
        "webUrl": "https://www.booking.com/attractions/searchresults/us/new-york.en-gb.html?...&pinned_product=PRCMOkYUz7Um&...",
        "extras": null
      }
    ]
  }
}

Fields

Shared lookups

33. Common Languages (shared by every module)

What it does. The list of language codes accepted by the languageCode parameter. It lives in the shared common module because it is not specific to stays: flights, car rentals, taxis and attractions use the same list. Today it is used by stays suggestions and stays search. Stays autocomplete has no language parameter: its results follow the language of the search text.

Where the inputs come from. Nothing: no parameters. Use the languageCode values it returns in every endpoint that has a languageCode parameter.

Request

GET /api/v1/common/languages
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Languages",
  "data": {
    "default": "en-us",
    "count": 45,
    "languages": [
      { "languageCode": "en-us", "name": "English (US)", "nativeName": "English (US)" },
      { "languageCode": "hi", "name": "Hindi", "nativeName": "हिन्दी" },
      { "languageCode": "pt-br", "name": "Portuguese (Brazil)", "nativeName": "Português (Brasil)" }
    ]
  }
}

34. Common Currencies (shared by every module)

What it does. The list of currency codes accepted by the currencyCode parameter. Like languages it lives in the shared common module because flights, cars and taxis will price in the same currencies.

Where the inputs come from. Nothing: no parameters. Use the currencyCode values it returns in every endpoint that has a currencyCode parameter. flights: true marks the codes that can be used for flight prices.

Request

GET /api/v1/common/currencies
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Currencies",
  "data": {
    "default": "USD",
    "count": 145,
    "flightsCount": 34,
    "currencies": [
      { "currencyCode": "AED", "name": "United Arab Emirates Dirham", "flights": true },
      { "currencyCode": "AFN", "name": "Afghan Afghani", "flights": false },
      { "currencyCode": "INR", "name": "Indian Rupee", "flights": true },
      { "currencyCode": "USD", "name": "US Dollar", "flights": true }
    ]
  }
}

currencyCode is the ISO 4217 code (same name and value you send as the currencyCode parameter); name is the English name. default is used when the parameter is not sent.

35. Common Exchange Rates (shared by every module)

What it does. Booking.com's own exchange rates: for one base currency, how many units of each of 189 currencies one unit of the base buys, with the day the rates are from. It sits next to GET /common/currencies because it is app-wide, not specific to stays; use it to show a price in another currency or to compare prices. - What was already available: only the list of currency codes (/common/currencies). No endpoint gave rates. (Prices in /stays/search, /stays/rooms and the others are already converted by Booking.com into the currencyCode you ask for.)

Where the inputs come from. The base currency is a currencyCode from GET /common/currencies.

Request

GET /api/v1/common/exchange-rates?baseCurrency=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Exchange rates found",
  "data": {
    "baseCurrency": "USD",
    "baseCurrencyName": "US Dollar",
    "date": "2026-10-18",
    "ageDays": 1,
    "stale": false,
    "attempts": 1,
    "rateCount": 189,
    "rates": [
      { "currencyCode": "EUR", "name": "Euro", "usableAsCurrencyCode": true, "exchangeRateBuy": 0.88865192 },
      { "currencyCode": "INR", "name": "Indian Rupee", "usableAsCurrencyCode": true, "exchangeRateBuy": 94.95371944 },
      { "currencyCode": "VEB", "name": null, "usableAsCurrencyCode": false, "exchangeRateBuy": 2000000 }
    ],
    "extras": null
  }
}

Fields

Attractions and things to do

36. Attractions Autocomplete

What it does. Destinations, points of interest and attractions that match typed text.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/autocomplete
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Autocomplete",
  "data": {
    "destinations": [
      {
        "cityName": "Statte",
        "country": "Italy",
        "productCount": 293,
        "ufi": -130183,
        "destination": "city:-130183"
      }
    ],
    "pointsOfInterest": [
      {
        "cc1": "us",
        "country": "United States",
        "cityName": "Memphis",
        "id": "DRc0CyRFL00f",
        "scopeName": "Statue of Elvis",
        "ufi": 20123619,
        "destination": "city:20123619"
      },
      {
        "cc1": "jp",
        "country": "Japan",
        "cityName": "Tokyo",
        "id": "DRwLyWfuAHaE",
        "scopeName": "Hachiko Statue",
        "ufi": -246227,
        "destination": "city:-246227"
      }
    ],
    "products": [
      {
        "cityUfi": 20088325,
        "cityName": "New York",
        "countryCode": "us",
        "productId": "PRJi4JHoYUQw",
        "productSlug": "prji4jhoyuqw-afternoon-statue-of-liberty-tour",
  ...

37. Attractions Destinations

What it does. The best-selling attraction cities of a country. Its ufi is the city id used by suggestions.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/destinations
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Destinations",
  "data": {
    "cities": [
      {
        "country": {
          "name": "United States"
        },
        "distance": null,
        "imageUrl": "https://q-xx.bstatic.com/xdata/images/city/720x405/977436.jpg?k=ee0baaf82d482fae02bcb8dda25be1abff1da43d187bbb…",
        "productCount": 2152,
        "ufi": 20088325,
        "ufiCity": "New York",
        "destination": "city:20088325"
      },
      {
        "country": {
          "name": "United States"
        },
        "distance": null,
        "imageUrl": "https://q-xx.bstatic.com/xdata/images/city/720x405/976876.jpg?k=0431a4ff8274f5ddd491d12e5cb34ce5ef2afd67b1adf1…",
        "productCount": 647,
        "ufi": 20050264,
        "ufiCity": "New Orleans",
        "destination": "city:20050264"
      }
    ]
  }
}

38. Attractions Suggestions

What it does. Attractions Booking.com suggests for a city, with the discounted ones listed in discountedProductIds.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/suggestions
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Suggestions",
  "data": {
    "discountedProductIds": [
      "PR473pyq8Tgw"
    ],
    "dealsOfTheMonth": null,
    "products": [
      {
        "cancellationPolicy": {
          "hasFreeCancellation": true
        },
        "distances": {
          "distanceFromSearchInputCoordinates": null,
          "distanceToAccommodation": null
        },
        "duration": {
          "label": "Duration: 55 minutes",
          "value": "PT55M"
        },
        "earlyBookingStats": null,
        "flags": null,
        "hasFreeGeniusUpgrades": false,
        "id": "PR473pyq8Tgw",
        "name": "NYC Statue of Liberty Express Sightseeing Cruise",
        "offers": [
          {
            "availabilityType": "date_time",
            "id": "OFY58IIqgk28",
            "items": [
              "…"
            ]
          }
        ],
        "photos": [
          {
            "caption": "the statue of liberty on the water with a cruise ship",
            "gallery": "https://q-xx.bstatic.com/xdata/images/xphoto/max1200/751560094.webp?k=da0d2572461ec21e9786ccb821c9ddea287aaa26…",
            "isPrimary": true,
  ...

Each products[] item has the same fields as an attraction of search (id, slug, name, representativePrice, photos, offers ...), under Booking.com's own names.

39. Attractions Search

What it does. Every bookable attraction (tickets, tours, activities) in a city, with the filter menus, sort options and paging the app shows behind "Things to do → See all". Each attraction has its name, short description, price (with supplier discounts), free cancellation, duration, review score, flags (Bestseller, Skip the line, Audio guide ...), photos and offers.

Where the inputs come from. The Attractions vertical (separate from Stays, like Flights, Car rental and Taxi) - see "Attractions" in the journey overview. The stays endpoint GET /stays/things-to-do is the five-card carousel on a hotel page; this is the full list behind its "See all" link. The detail, reviews and availability calls of one attraction will live here too, once captured. It takes a city (city:<id>, from GET /stays/autocomplete, or city:<location.destinationId> from GET /stays/property-details); pass a property's coordinates as latitude/longitude to get each attraction's distance from it.

Request

GET /api/v1/attractions/search?destination=city:20088325&checkin=2026-12-20&checkout=2026-12-21&filters=label::free_cancellation,rating::4.5&sortBy=lowest_price&pageSize=20&page=1&currencyCode=USD
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

What you get back

{
  "status": true,
  "message": "Attractions found",
  "data": {
    "totalCount": 1748,
    "unfilteredCount": 1748,
    "page": 1,
    "pageSize": 20,
    "hasNextPage": true,
    "isSuggestion": false,
    "defaultSorter": { "name": "Our top picks", "value": "trending" },
    "sorters": [ { "name": "Our top picks", "value": "trending" }, { "name": "Lowest price", "value": "lowest_price" }, { "name": "Best reviewed", "value": "highest_weighted_rating" } ],
    "filterGroups": [
      { "family": "label", "providerName": "labelFilters", "options": [ { "name": "Free cancellation", "productCount": 1522, "tag": "free_cancellation", "filter": "label::free_cancellation", "children": [], "extras": null } ] },
      { "family": "type", "providerName": "typeFilters", "options": [ { "name": "Tours ", "productCount": 1200, "tag": "PTCMCuXtHgrC", "filter": "type::PTCMCuXtHgrC", "children": [ { "name": "Walking & hiking tours", "productCount": 479, "tag": "PTCMC74RQHpJ", "filter": "type::PTCMC74RQHpJ" } ], "extras": null } ] }
    ],
    "attractionCount": 20,
    "attractions": [
      {
        "id": "PRZtshIDqvnN",
        "name": "The Museum of Modern Art Admission",
        "slug": "prztshidqvnn-the-museum-of-modern-art-admission",
        "shortDescription": "A ticket to explore the art museum and see some of the most popular artworks",
        "availableFrom": "2026-10-22",
        "price": { "chargeAmount": 2848.61, "publicAmount": 2848.61, "currency": "INR", "discounts": [], "extras": null },
        "hasFreeCancellation": false,
        "hasFreeGeniusUpgrades": false,
        "duration": { "label": "Duration: 2 hours", "value": "PT2H", "minutes": 120 },
        "reviews": { "average": 9, "total": 13, "scale": "TEN_POINT", "originalScale": "FIVE_POINT", "reviewScore": "WONDERFUL", "scoreWord": "Fabulous", "categories": [ { "categoryName": "easyToAccess", "average": 4.8, "total": 5 } ], "extras": null },
        "flags": [ { "flag": "aiBadgesAdmissionIncluded", "rank": 0.1, "value": true, "label": null } ],
        "distances": { "fromSearchPointMeters": null, "toAccommodationMeters": null, "toAccommodationDescription": null },
        "primaryPhotoUrl": "https://q-xx.bstatic.com/xdata/images/xphoto/300x320/403849877.webp?k=...",
        "photos": [ { "photoId": 403849877, "isPrimary": true, "galleryUrl": "https://q-xx.bstatic.com/xdata/images/xphoto/max1200/403849877.webp?k=...", "mediumUrl": "https://r-xx.bstatic.com/xdata/images/xphoto/900x600/403849877.webp?k=...", "caption": "a view of the city from the top of a skyscraper", "extras": null } ],
        "offers": [ { "id": "OF6QAt39k8m9", "availabilityType": "date_time", "itemIds": [ "OIH87uMSWfPa" ] } ],
        "earlyBookingStats": null,
        "supportsNativeApp": true,
        "selfFundedDiscountTrackingSupported": null,
        "location": { "cityName": "New York", "ufi": 20088325, "countryCode": "us" },
        "extras": null
      }
  ...

Fields

40. Attractions Search Filters

What it does. The filter menu of an attractions search without the products: every filter with the number of attractions it would leave. Lighter than search, whose filterGroups it repeats exactly.

Where the inputs come from. The attractions journey in the journey overview.

Request

GET /api/v1/attractions/search-filters
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

Sort, paging, text and product ids are not parameters here.

What you get back

{
  "status": true,
  "message": "Filters found",
  "data": {
    "totalCount": 113,
    "unfilteredCount": 113,
    "filterGroups": [
      {
        "family": "landmark",
        "providerName": "destinationFilters",
        "options": [
          {
            "name": "Statue of Liberty",
            "productCount": 31,
            "tag": "DRzgorRcotfZ",
            "filter": "landmark::DRzgorRcotfZ",
            "children": [],
            "extras": null
          }
        ]
      }
    ],
    "extras": null
  }
}

Each option's filter is what filters takes. See filters.md.

41. Attraction Product

What it does. One attraction in full: description, highlights, what is included and not, itinerary, offers, photos, review summary, cancellation policy, addresses, operator and similar attractions.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/product
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Attraction",
  "data": {
    "product": {
      "accessibility": [
        "Accessible to pushchairs/prams"
      ],
      "additionalBookingInfo": null,
      "additionalInfo": "Suitable for all physical fitness levels\n\nPlease arrive 30 min prior to boarding time. Boarding will begin app…",
      "addresses": {
        "arrival": [
          {
            "address": "Pier 78 at Hudson River Park, 12th Ave 455",
            "city": "New York, NY",
            "country": "us",
            "googlePlaceId": "ChIJCwHl5EpYwokR-q8jdQg_ER8",
            "id": "LO3NKhflY06b",
            "instructions": null,
            "latitude": "40.759715",
            "locationType": "arrival",
            "longitude": "-74.0039699",
            "publicTransport": null,
            "zip": "10018"
          }
        ],
        "attraction": null,
        "departure": [
          {
            "address": "Pier 78 at Hudson River Park, 12th Ave 455",
            "city": "New York, NY",
            "country": "us",
            "googlePlaceId": "ChIJCwHl5EpYwokR-q8jdQg_ER8",
            "id": "LO2ip3h3WcXo",
            "instructions": "Located on the north side of Pier 78. Look for Starship Ticket Booth specifically and all the blue canopies",
            "latitude": "40.759715",
            "locationType": "departure",
            "longitude": "-74.0039699",
            "publicTransport": null,
            "zip": "10018"
  ...

Booking.com's own field names are kept and nothing is dropped; only the service type markers are removed. Ids from here: offers[].id and offers[].items[].

42. Attraction Comparison

What it does. The short "compare" view of an attraction: addresses, what is and is not included.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/comparison
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Attraction comparison",
  "data": {
    "product": {
      "addresses": {
        "arrival": [
          {
            "address": "Pier 78 at Hudson River Park, 12th Ave 455",
            "city": "New York, NY",
            "country": "us",
            "googlePlaceId": "ChIJCwHl5EpYwokR-q8jdQg_ER8",
            "id": "LO3NKhflY06b",
            "instructions": null,
            "latitude": "40.759715",
            "locationType": "arrival",
            "longitude": "-74.0039699",
            "publicTransport": null,
            "zip": "10018"
          }
        ],
        "attraction": null,
        "departure": [
          {
            "address": "Pier 78 at Hudson River Park, 12th Ave 455",
            "city": "New York, NY",
            "country": "us",
            "googlePlaceId": "ChIJCwHl5EpYwokR-q8jdQg_ER8",
            "id": "LO2ip3h3WcXo",
            "instructions": "Located on the north side of Pier 78. Look for Starship Ticket Booth specifically and all the blue canopies",
            "latitude": "40.759715",
            "locationType": "departure",
            "longitude": "-74.0039699",
            "publicTransport": null,
            "zip": "10018"
          }
        ],
        "entrance": null,
        "guestPickup": null,
        "meeting": null,
  ...

43. Attraction Review Snippets

What it does. The reviews shown on the product page, with the total number of reviews. For paging, sorting and filters use reviews.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/review-snippets
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Review snippets",
  "data": {
    "total": 1852,
    "reviews": [
      {
        "content": "We spend a wonderfully time. It was an incredible experience that we will never forget",
        "epochMs": 1743245765000,
        "id": "RS2l2kQ9JZLT",
        "language": "en-gb",
        "numericRating": 10,
        "originalScale": "FIVE_POINT",
        "providerName": null,
        "scale": "TEN_POINT",
        "travelPartnerTypes": [
          "family"
        ],
        "user": {
          "avatar": null,
          "cc1": "co",
          "name": "Sanchez Gooding"
        },
        "votes": {
          "count": 1,
          "userVoted": false
        },
        "photos": []
      },
      {
        "content": "We all enjoyed a fantastic sailing . Darius was an informative and entertaining host.",
        "epochMs": 1760858971000,
        "id": "RSdGLsYFruBI",
        "language": "en-gb",
        "numericRating": 10,
        "originalScale": "FIVE_POINT",
        "providerName": null,
        "scale": "TEN_POINT",
        "travelPartnerTypes": [
          "family"
  ...

44. Attraction Reviews

What it does. Guest reviews of an attraction with paging, sorting, three filters, and the sort and filter menus (with counts).

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/reviews
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer

{
  "status": true,
  "message": "Reviews",
  "data": {
    "total": 426,
    "page": 1,
    "pageSize": 2,
    "defaultSorter": {
      "id": "most_relevant",
      "label": "Most relevant"
    },
    "sorters": [
      {
        "id": "most_relevant",
        "label": "Most relevant"
      },
      {
        "id": "newest",
        "label": "Newest first"
      }
    ],
    "filters": [
      {
        "name": "hide_empty_reviews",
        "label": "Hide reviews without comments",
        "selectionType": "binary",
        "options": []
      },
      {
        "name": "time",
        "label": "Time of year",
        "selectionType": "single",
        "options": [
          {
            "id": "Q1",
            "label": "January to March",
            "count": null
          },
          {
            "id": "Q2",
  ...

filters[] is the menu: name (hide_empty_reviews, time, language), selectionType, and options[] {id, label, count}. sorters[] is the sort menu.

45. Attraction Availability Calendar

What it does. Which days an attraction can be booked (about 180 days from today) and its lowest price for those days.

Where the inputs come from. The attractions journey in the journey overview: autocomplete / destinations -> search -> product, reviews, availability.

Request

GET /api/v1/attractions/availability-calendar
X-RapidAPI-Key: YOUR_KEY
X-RapidAPI-Host: booking-com30.p.rapidapi.com

Parameters, rules and the answer