Search restaurant locations and venues by name
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Look up dining-location suggestions from a typed name using the required string query parameter. Send a city or area name, or part of a venue name, and read the returned location records so a user can pick a place in a restaurant-focused interface. The parameter is documented as the name of the location where the restaurant is situated. This operation returns suggestion records only: it does not return restaurant details, menus, opening hours, reviews or reservations, and it accepts no filter, language or page inputs. No observed probe response was supplied for this operation, so the response description comes from a truncated source example and is unverified. For the query mumbai, the example shows a data array of location objects with documentId, locationId, isGeo, localizedName, placeType, latitude, longitude, localizedAdditionalNames.longOnlyHierarchy, locationV2 (names.longOnlyHierarchyTypeaheadV2, placeType and a vacationRentalsRoute that is either an object with a url or null), streetAddress.street1 and a thumbnail.photoSizeDynamic object holding maxHeight, maxWidth and a urlTemplate with {width} and {height} placeholders. The first example record is the city Mumbai with isGeo true and placeType CITY; the other visible records have isGeo false and placeType EATERY, such as Mumbai Kitchen in Indonesia and Mumbai Masala branches in Spain, so one response can mix place records and individual venue records. The example is cut off, so the full result count, ordering, envelope fields beyond data and error behavior are not established. Treat labels as display text, inspect a real response before relying on any field, and do not assume that locationId or documentId can be passed as restaurantsId to another operation without checking that operation's own input documentation.
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-restaurant-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-restaurant-location?key=<API_KEY>&query=<query>'
Query Result
Use Cases
- Build a restaurant search box that suggests matching cities and named venues as a traveler types mumbai, showing localizedName with its longOnlyHierarchy line underneath.
- Branch the picker on placeType and isGeo so that choosing a CITY suggestion opens an area-level dining screen while choosing an EATERY suggestion opens a single-venue screen.
- Plot suggested eateries on a preview map from latitude and longitude, after verifying in a live response that both values are present for the records you display.
- Render suggestion rows with a thumbnail from urlTemplate and the streetAddress.street1 line so users can distinguish same-named restaurants located in different countries.
- Sample several typed queries and store the raw suggestion records to study how shared or chain-style names scatter across countries before wiring a stored identifier into any restaurant-details request.
Frequently asked questions
What should I pass in the query parameter?
Pass the name of the place where the restaurant is located, for example a city such as mumbai. The parameter is a required string. The operation exposes no other inputs, so filters, language, result limits and paging are not available here.
Does this endpoint return restaurants or only cities?
The source example for mumbai contains both. The first record is the city Mumbai (placeType CITY, isGeo true) and the remaining visible records are eateries (placeType EATERY, isGeo false) with names such as Mumbai Kitchen. Because the example is truncated and no probe was supplied, the exact mix for other queries is not established, so branch on placeType and isGeo in your code.
Which response fields are documented?
The truncated source example shows a data array whose objects include documentId, locationId, isGeo, localizedName, placeType, latitude, longitude, localizedAdditionalNames.longOnlyHierarchy, locationV2, streetAddress.street1 and thumbnail.photoSizeDynamic. These fields are unverified because no observed probe response was supplied, and the example is cut off after the visible records.
Can I use a returned locationId as restaurantsId in the restaurant details operations?
Do not assume so. The restaurant details operations document restaurantsId as an input, but the supplied evidence does not show that locationId or documentId from this response is accepted there, or in what form. Check the target operation's input documentation and test with a real returned value before building a flow on it.
How do I turn the thumbnail urlTemplate into an image URL?
The example urlTemplate contains literal {width} and {height} placeholders. Replace them with pixel sizes that fit your layout, keeping within the maxWidth and maxHeight values shown beside the template. Treat the resulting address as display content and handle records where the thumbnail is missing.
Does this operation return menus, hours or reviews?
No. It is a location and venue suggestion lookup. The documented response fields describe names, hierarchy labels, coordinates, a street line and a thumbnail template only. Use the dedicated restaurant details operation for richer venue content, and check its own inputs and response documentation.