Tripadvisor place details (hotel, restaurant or attraction)

GET https://api.api.sh/tripadvisor/v1/place
1 credit / call travel & events try it in the playground →

Details for any Tripadvisor hotel, restaurant or attraction (type says which): name, URL, rating and the count per star, sub-ratings, review count, review languages, ranking, address, coordinates, phone, email, breadcrumbs, description, AI review summary, review keywords, photo count and photos, and the latest reviews. Hotels add amenities (property, room features, room types), star rating, price range and the booking-site offers for the stay when check_in / check_out are given (offers.complete false when partners were still answering). Restaurants add cuisines, price level and range, diets, meal types, features, hours, menu and awards. nearby lists the hotels, restaurants and attractions around the place (name, distance, rating, review count, rank, position, photo, link) with the counts within the range, nearby transit stops, airports and neighborhoods. raw holds the page data. Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
id string Tripadvisor location id (d-number), e.g. 93437; or pass url. Example: 93437
url string A Tripadvisor hotel, restaurant or attraction URL (instead of id).
check_in string Hotels: check-in date (YYYY-MM-DD) for offers; with check_out.
check_out string Hotels: check-out date (YYYY-MM-DD).
adults integer Hotels: adults (default 2).
rooms integer Hotels: rooms (default 1).
domain com | co.uk | de | fr | it | es | in Tripadvisor market: com (default), co.uk, de, fr, it, es or in. Names, prices, currency and review translations follow the market. Default: com

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/tripadvisor/v1/place?id=93437" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.