Get restaurant details by restaurantsId (legacy path)
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Retrieve the detail record for one known Tripadvisor restaurant through the deprecated restaurant-details path. The required restaurantsId string is documented as coming from a restaurant search result, and the optional currencyCode string is documented as coming from the currency reference lookup, with USD as the example. Existing clients can keep this request shape while they plan a move to the V2 details operation; new integrations should start with V2. This lookup returns details for a single restaurant only and does not search for restaurants, list menus or take reservations. No observed probe response was supplied, so the response description comes from a truncated source example and is unverified. The visible part shows a data object with hours and location. The hours object includes allOpenHours (days and times), currentHoursText, hoursTodayText, openStatus, openStatusText and an addHoursLink. The location object includes address, address_obj (street1, street2, city, state, postalcode, country), ancestors, category, cuisine, dietary_restrictions, description, display_hours, a nested hours object with timezone and week_ranges (open_time and close_time), latitude, longitude, location_id, location_string, name, neighborhood_info, num_reviews, awards, open_now_text and a photo object with image renditions. Latitude, longitude, location_id and num_reviews appear as strings. The example is cut off, so remaining fields, error responses and any effect of currencyCode are not established. The visible portion matches the V2 example; differences in schema or status behavior, if any, are not documented, so compare real responses before swapping paths.
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-restaurant-details-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-restaurant-details-deprecated?key=<API_KEY>'
Query Result
Use Cases
- Audit existing clients that still call the deprecated restaurant-details path and list which response fields each one actually reads before planning the move to V2.
- Run side-by-side response comparisons between this legacy path and V2 for a sample of known restaurantsId values, recording any field, status or error differences you observe.
- Keep a legacy dining-guide page working during a migration window by caching the cuisine, address and opening-hours fields it already displays.
- Check whether stored restaurantsId values still resolve before retiring an old integration, handling failures explicitly instead of assuming both paths behave the same.
- Write regression fixtures from the legacy path so a replacement client can be tested against the same hours, address and cuisine fields it must preserve.
Frequently asked questions
Should I use this deprecated path for a new integration?
No. The operation is labeled deprecated, so new work should start with the V2 restaurant-details operation, which takes the same restaurantsId and currencyCode inputs. Use this legacy path only to keep an existing client running or to compare responses while you migrate.
Where do I get restaurantsId?
The parameter documentation says to take restaurantsId from a restaurant search result. This operation does not discover restaurants and no sample value is supplied, so pass an identifier you already obtained, unchanged and as a string.
What does currencyCode change?
currencyCode is optional and is documented as a value from the currency reference lookup, with USD as the example. The visible part of the source example does not show a price field, so the effect on the response is unverified. Test with and without it and read the actual payload.
Which response fields are documented?
The truncated source example shows data.hours and data.location. Visible fields include opening-status text, weekly hours, address data, cuisine and dietary tags, coordinates, location_id, name, neighborhood_info, num_reviews and a photo object with several image sizes. These are unverified source-example fields, and the example is cut off before the end of the record.
Is the response identical to the V2 operation?
The visible portion of the source example is the same for both paths, but it is truncated and no probe response was supplied. Differences in schema, limits or error behavior are therefore not established. Compare real responses for your restaurantsId values before replacing one path with the other.
Are latitude, longitude and review counts numbers?
In the source example, latitude, longitude, location_id and num_reviews appear as strings. Parse them in your own code after checking the live response, and tolerate null values, as fields such as bearing, distance and street2 appear as null in the example.