Search hotels by destination, dates and optional filters
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Search for hotels with a required destination geoId and checkIn and checkOut dates in YYYY-MM-DD format. Obtain geoId through hotel location search and supply it as a string. Optional adults, rooms and childrenAges describe the party; currencyCode selects a currency from the currency lookup; pageNumber selects a result page and has a documented default of 1. The contract also accepts sort, priceMin, priceMax, rating, distFrom, distFromMaxDistance and the array filters amenity, brand, class, deals, healthSafety, neighborhood, style and type. The supplied documentation does not define accepted filter tokens, sort values, rating scale or distance units. Inspect applicable filter metadata before mapping controls, and leave unverified optional values unset. A saved successful HTTP 200 probe returned status=true, a message string, an integer timestamp and a data object containing a data array: the observed hotel-list path is data.data, not the outer data object. A separate truncated documentation example shows rows with id, title, bubbleRating, cardPhotos, isSponsored, primaryInfo, secondaryInfo, priceDetails, priceForDisplay, priceSummary and strikethroughPrice; those row fields were not confirmed by the supplied probe metadata and should not be assumed present. Verify a selected row’s hotel identifier before forwarding it to the hotel-details id input. No total-count, page-size, stable ordering, booking, exhaustive inventory or live-price guarantee is established by the supplied evidence.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/tripadvisor-data/search-hotels API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-hotels?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&geoId=<geoId>&pageNumber=1'
Query Result
Use Cases
- Create a date-specific hotel shortlist after a traveler selects a destination geoId from hotel location search.
- Implement a result-page adapter that reads data.data and records the requested pageNumber without inventing total-page or page-size metadata.
- Save hotel search criteria with selected rows so a later comparison can recover the original party, stay dates, currency and verified filter selections.
- Build a controlled shortlist-to-detail workflow that checks the selected hotel identifier before requesting extra property content.
- Prototype price, rating and facet controls only after inspecting accepted values, leaving unsupported or unverified options hidden.
Frequently asked questions
Should geoId identify a destination or a hotel?
It identifies the destination selected through hotel location search, not an individual hotel. geoId is a required string here, alongside required checkIn and checkOut dates in YYYY-MM-DD format.
Where is the hotel list in the observed response?
The saved successful probe returned a JSON object with status=true, message, timestamp and an outer data object. The list was the nested data.data array. The supplied probe metadata does not establish the fields inside each row.
What pagination behavior is documented?
pageNumber is optional and its documented default is 1. No page size, total-page field, maximum page number or stable ordering guarantee is established by the supplied evidence.
Which optional filters can I send?
The contract accepts amenity, brand, class, deals, healthSafety, neighborhood, style and type as arrays, plus priceMin, priceMax, rating, distFrom, distFromMaxDistance and sort. Allowed tokens, sort codes, rating scale and distance units are not documented. Inspect applicable metadata and verify mappings before sending values.
Are the row-level prices, ratings and photos verified?
A truncated documentation example shows priceForDisplay, priceDetails, priceSummary, strikethroughPrice, bubbleRating and cardPhotos, but the supplied probe metadata confirms only the nested list shape. Treat these row fields as unverified and optional; neither the example nor the search confirms a bookable offer.
How do I move from a search result to hotel details?
Select the hotel deliberately and verify the identifier accepted by the detail endpoint’s id input before forwarding it. Keep the same stay and party context. Search uses currencyCode, whereas the detail lookup names its currency input currency.