Get restaurant details by restaurantsId (V2)

View all Tripadvisor Hotel, Rental & Travel Data endpoints →

Retrieve the detail record for one known Tripadvisor restaurant using the V2 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. Use it to enrich a restaurant you have already identified with address, cuisine, opening-status and photo data. It does not search for restaurants, return menus, provide review text or make 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 openStatus, openStatusText, currentHoursText, hoursTodayText, allOpenHours (days and times) and an addHoursLink. The location object includes name, description, address, address_obj (street1, street2, city, state, postalcode, country), ancestors, category, cuisine, dietary_restrictions, display_hours, a nested hours object with timezone and week_ranges (open_time and close_time), latitude, longitude, location_id, location_string, neighborhood_info, num_reviews, awards, parent_display_name and a photo object with large, medium, original, small and thumbnail renditions. Latitude, longitude, location_id and num_reviews appear as strings, and several fields are null in the example. The example is cut off, so remaining fields, error responses and any effect of currencyCode are not established. Inspect the actual response before choosing which fields to display or store.

API Features

Current details path for new clients V2 is the non-deprecated restaurant-details operation, taking one required restaurantsId and an optional currencyCode, which makes it the starting point for new integrations.
Open-status text fields The source example includes openStatus, openStatusText, currentHoursText and hoursTodayText, plus allOpenHours day and time strings that fit open-now badges and hours panels.
String coordinates and place IDs Example latitude, longitude and location_id values arrive as strings, together with name, location_string and parent_display_name, so your code should convert types after checking the live payload.
Photo rendition URLs The example photo object lists caption, id and an images map with large, medium, original, small and thumbnail entries, each giving url, width and height values for responsive cards.
Neighborhood and review-count context Example neighborhood_info entries name nearby areas and num_reviews gives an aggregate count, adding local context to a known restaurant without being a review-text feed.

Live API Demo

GET /api/project/tripadvisor-data/get-restaurant-details-v2

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

Use Cases

Frequently asked questions

What does this V2 operation return for a restaurant?

The truncated source example shows a data object with hours and location. Visible fields cover opening status and hours, address data, cuisine and dietary tags, coordinates, identifiers, neighborhood context, a review count and photo renditions. These fields are unverified because no probe response was supplied, and the example ends before the full record.

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.

Is currencyCode required, and what does it do?

No, currencyCode is optional. It is documented as a value from the currency reference lookup, with USD as the example. The visible part of the source example shows no price field, so its effect on the response is unverified. Compare requests with and without it before depending on it.

Can this endpoint give me menus, review text or reservations?

Nothing in the supplied evidence shows menus, review text or booking features. The example exposes a review count (num_reviews) and an addHoursLink, but not individual reviews. Treat this operation as a profile lookup for a known restaurant and verify any other field in the real response.

Should I migrate from the deprecated restaurant-details path?

Yes for new work. The older operation is labeled deprecated and shares the same inputs, but the visible source examples are truncated and no probe response exists for either path. Compare real responses and error behavior for your restaurantsId values before switching, and do not assume the schemas are equal.

How should I handle string numbers and null fields?

In the source example latitude, longitude, location_id and num_reviews are strings, and fields such as bearing, distance and street2 are null. Parse values defensively, keep identifiers as strings, and make every optional field render safely when missing.

Related operations

Guides

View Subscription Plans →