Get hotel filter metadata for a destination and stay
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Request hotel-search filter metadata using a required geoId plus checkIn and checkOut dates in YYYY-MM-DD format. Use the geoId returned by the hotel location-search operation and keep it as the required string input here. No probe observation was supplied for this operation. The truncated documentation example shows a data object containing datePicker and a filters array; these are documentation-only fields, not verified probe results. The example datePicker contains configuration fields maxAdultsPerRoom, maxChildrenPerRoom, maxRooms and maxStayLength, as well as lastSelectableDate and timeZoneOffset. Example filter entries include name and title, nested filters, and, on some entries, minValue, maxValue, selectedRangeStart and selectedRangeEnd. Inspect the actual returned structures before exposing controls or mapping values into hotel-search parameters. Do not hard-code a universal list of facets, numeric limits, selectable dates or value encodings from the example. Refresh or invalidate cached choices when the destination or either stay date changes. This endpoint describes search controls; it does not return the hotel result list or confirm that a room can be booked.
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/get-hotels-filter API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-hotels-filter?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&geoId=<geoId>'
Query Result
Use Cases
- Design a destination filter drawer from inspected group names and nested options instead of inventing amenity, class, brand or neighborhood values.
- Evaluate the documented date-picker configuration before deciding which limits a hotel-search form can safely display.
- Invalidate stored facet selections when a traveler changes destination, check-in or check-out dates.
- Build a metadata adapter that separately handles nested options and range-style filter fields without assuming every filter group has the same shape.
Frequently asked questions
What inputs are required to retrieve hotel filter metadata?
geoId, checkIn and checkOut are all required strings. Obtain geoId through hotel location search and supply both dates in YYYY-MM-DD format. This operation does not declare adult, room or currency parameters.
Has the filter response been verified by a saved probe?
No probe observation was supplied for this operation. Its response-field descriptions come from a truncated documentation example and should be checked against an actual response before integration.
Which response fields are shown in the documentation example?
The example shows data.datePicker and data.filters. datePicker includes configuration, lastSelectableDate and timeZoneOffset. Filter entries include name, title, nested filters and, on some entries, range-related fields. This is not a verified complete response schema.
Can I reuse the same filter choices for every destination and date range?
Do not assume that. Keep the metadata associated with its geoId, checkIn and checkOut values, and invalidate selected facets when any of those values changes. Only expose options whose returned values and hotel-search mappings you have inspected.
Does this operation return hotel listings or guarantee availability?
No hotel result list is documented here. This operation is for search-control metadata; use hotel search for listings. Neither filter metadata nor an example date-picker limit guarantees bookable inventory.