/tripadvisor/locations

POST /api/tripadvisor/locations

Price: 20 credits

Get a Tripadvisor restaurant, hotel or attraction by URL or location id: name, type, rating, review count with per-star and per-language breakdowns, sub-ratings, ranking in its city, address, coordinates, phone, website, price, cuisines or amenities, opening hours, awards and photo count

How to use it

Fetch one Tripadvisor place by its page URL or numeric location id; location_type tells restaurant, hotel or attraction apart. Pass the same id to tripadvisor/locations/reviews for its traveler reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• location string required — Tripadvisor restaurant, hotel or attraction URL or location id (examples: "https://www.tripadvisor.com/Restaurant_Review-g60763-d457808-Reviews-Daniel-New_York_City_New_York.html", "93589", "https://www.tripadvisor.com/Attraction_Review-g60763-d105127-Reviews-Central_Park-New_York_City_New_York.html"; minLength: 1)

Response

• @type string (default: "TripadvisorLocation")
• id string required
• location_type string required (one of: "restaurant", "hotel", "attraction")
• name string required
• former_name string nullable
• url string required
• geo_id string required
• geo_name string nullable
• description string nullable
• image string nullable
• rating number nullable
• review_count integer nullable
• rating_counts array (default: [])
  • @type string (default: "TripadvisorRatingCount")
  • rating integer required
  • review_count integer required
• language_counts array (default: [])
  • @type string (default: "TripadvisorLanguageCount")
  • language string required
  • review_count integer required
• subratings array (default: [])
  • @type string (default: "TripadvisorSubrating")
  • name string required
  • rating number required
• ranking string nullable
• ranking_position integer nullable
• ranking_total integer nullable
• phone string nullable
• email string nullable
• website_url string nullable
• menu_url string nullable
• address object nullable
  • @type string (default: "TripadvisorAddress")
  • street string nullable
  • city string nullable
  • region string nullable
  • postal_code string nullable
  • country string nullable
  • full_address string nullable
• neighborhoods array (default: [])
• latitude number nullable
• longitude number nullable
• price_level string nullable
• price_min number nullable
• price_max number nullable
• price_currency string nullable
• categories array (default: [])
• cuisines array (default: [])
• diets array (default: [])
• meal_types array (default: [])
• features array (default: [])
• amenities array (default: [])
• room_features array (default: [])
• room_types array (default: [])
• styles array (default: [])
• languages_spoken array (default: [])
• room_count integer nullable
• walk_score integer nullable
• special_offer object nullable
  • @type string (default: "TripadvisorSpecialOffer")
  • id string nullable
  • details string nullable
• duration string nullable
• hours array (default: [])
  • @type string (default: "TripadvisorOpeningHours")
  • day string required
  • opens string nullable
  • closes string nullable
• is_open_now boolean nullable
• is_closed boolean nullable
• has_verified_owner boolean nullable
• awards array (default: [])
  • @type string (default: "TripadvisorAward")
  • name string required
  • year integer nullable
  • description string nullable
• photo_count integer nullable
• review_keywords array (default: [])
• review_summary string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No Tripadvisor restaurant, hotel or attraction has this id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.