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

Dated destination hotel discovery Combine a hotel location-search geoId with checkIn and checkOut to build a destination shortlist for a specified stay rather than searching by a hotel identifier.
Observed nested result-list parsing Extract hotel rows from the data.data array observed in the successful saved probe. Do not treat the enclosing data object as the result list or infer item fields from the envelope.
Explicit page and party context Use the documented pageNumber default of 1 and retain dates, adults, rooms, childrenAges and currencyCode alongside each requested result page. Page size and total-page metadata are not established.
Verified-value search refinement The contract exposes array facets plus price, rating, distance and sort controls. Map only inspected values; token sets, sort codes, rating scale and distance units are not defined in the supplied parameter descriptions.
Selective detail handoff Choose rows intentionally, verify the hotel identifier accepted by the detail lookup, and enrich only those records. The documentation example’s row id does not by itself prove an item-level mapping.

Live API Demo

GET /api/project/tripadvisor-data/search-hotels

Request cost is temporarily unavailable. No price is assumed.

View pricing

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'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →