/tripadvisor/locations/reviews

POST /api/tripadvisor/locations/reviews

Price: 20 credits

Get traveler reviews of a Tripadvisor restaurant, hotel or attraction in every language: title, text, star rating, sub-ratings, visit month and traveler type, dates, helpful votes, photos, reviewer profile and the owner's response, filterable by rating, traveler type, visit month and keyword

How to use it

Fetch the reviews of one Tripadvisor place by its page URL or the location id that tripadvisor/locations and tripadvisor/locations/search return. Reviews come in their original language; filters combine.

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"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1; max: 5000)
• sort string — Review order (default: "newest"; one of: "newest", "detailed")
• ratings array nullable — Only reviews with one of these star ratings (examples: [1,2])
• traveler_types array nullable — Only reviews from these kinds of travelers (one of: "family", "couples", "solo", "business", "friends")
• months array nullable — Only reviews of visits in these calendar months (examples: [12,1,2])
• languages array nullable — Only reviews originally written in one of these languages (one of: "ar", "cs", "da", "de", "el", "en", "es", "fi", "fr", "hu", "in", "it", "iw", "ja", "ko", "nl", "no", "pl", "pt", "ru", "sk", "sr", "sv", "th", "tr", "vi", "zhCN", "zhTW"; examples: ["fr","de"])
• keyword string nullable — Only reviews mentioning this word or phrase (examples: "breakfast"; minLength: 1)

Response

• @type string (default: "TripadvisorReview")
• id string required
• location_id string required
• url string nullable
• text string nullable
• rating integer nullable
• language string nullable
• original_language string nullable
• published_date string nullable
• created_date string nullable
• stay_month string nullable
• traveler_type string nullable (one of: "family", "couples", "solo", "business", "friends")
• helpful_count integer nullable
• is_owner_favorite boolean nullable
• subratings array (default: [])
  • @type string (default: "TripadvisorSubrating")
  • name string required
  • rating number required
• tips array (default: [])
• photos array (default: [])
  • @type string (default: "TripadvisorReviewPhoto")
  • id string required
  • image string required
  • caption string nullable
• author object nullable
  • @type string (default: "TripadvisorReviewAuthor")
  • id string nullable
  • name string nullable
  • alias string nullable
  • url string nullable
  • image string nullable
  • hometown string nullable
  • is_verified boolean nullable
  • contribution_count integer nullable
  • helpful_vote_count integer nullable
• owner_response object nullable
  • @type string (default: "TripadvisorOwnerResponse")
  • id string nullable
  • text string required
  • language string nullable
  • published_date string nullable
  • author_name string nullable
  • author_role 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.