Find hotel destinations and their geoId values

View all Tripadvisor Hotel, Rental & Travel Data endpoints →

Resolve a typed hotel destination into Tripadvisor location suggestions using the required string query parameter. Use the returned location information to let a traveler choose a destination, then retain its geoId separately from any individual hotel id. This operation looks up locations; it does not search hotel inventory or return an individual property detail record. An observed successful probe with query=New York returned HTTP 200 and a JSON object with status=true, message as a string, timestamp as an integer and data as an array of location objects. Declared location fields are documentId, secondaryText, title and trackingItems, all strings when present. The observed response additionally included integer geoId values. Read suggestions directly from data, not data.data. The unverified source example shows the declared fields and HTML-style bold markup in title, but does not establish geoId; geoId is supported by the observed probe instead. Treat result labels as display content, handle ambiguous destinations through explicit selection and tolerate missing optional fields. Timestamp units and a maximum result count are not documented.

API Features

Single-query destination resolution Submit the required query string to look up location suggestions for a hotel destination rather than supplying coordinates or stay dates.
Observed integer destination identifiers The successful probe included integer geoId values that can be retained for a separate destination-based hotel-search request.
Location labels for disambiguation Use the declared title and secondaryText strings, when present, to present distinct choices for similar destination names.
Direct suggestion-array handling The observed response places location objects directly in the top-level data array, alongside status, message and timestamp.
Identifier separation for hotel workflows Keep geoId as a destination identifier and documentId as a separate returned string; neither should be assumed to identify an individual hotel.

Live API Demo

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

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

Use Cases

Frequently asked questions

What should I pass in query?

Pass the destination name as a string. The recorded successful probe used New York. The parameter is required; this lookup does not accept stay dates or coordinates.

Where are the location suggestions in the response?

The observed response places them directly in the top-level data array. Do not look for data.data. The same response includes status, message and an integer timestamp.

Was geoId actually observed or only shown in an example?

An integer geoId was observed in the successful probe. The unverified source example documents documentId, secondaryText, title and trackingItems as strings but does not itself establish geoId.

Is a returned geoId the same as a hotel id or documentId?

No such equivalence is established. Use geoId as a destination identifier for destination-based hotel search, keep documentId separately and obtain an individual hotel id from a property result before requesting hotel details.

How should I handle ambiguous names and formatted titles?

Show the available title and secondaryText labels and require an explicit selection when multiple destinations could match. The source example includes bold markup in title, so render it safely rather than inserting it as untrusted HTML.

Does this endpoint return hotel availability or confirm a booking?

No. It resolves destination queries into location suggestions. Hotel search, property details and any booking or inventory confirmation are separate concerns.

Related operations

Guides

View Subscription Plans →