/google/hotels/reviews

POST /api/google/hotels/reviews

Price: 20 credits

Get Google Hotels reviews for a hotel by feature ID, aggregated across Google and travel sites.

How to use it

Get guest reviews for a hotel by its feature_id (hex '0x..:0x..'). Returns review text, rating, author, relative date, the source site (Google, Tripadvisor, Priceline, Trip.com, etc.), hotel highlights the guest noted, and any owner reply. Reviews are aggregated across Google and partner travel sites.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• feature_id string required — Hotel feature ID in hex form '0x..:0x..' (examples: "0x89c28aad4f6a9ce5:0xa4793816b9bcb218"; minLength: 1)
• count integer required — Max number of reviews (min: 1)

Response

• @type string (default: "GoogleHotelReview")
• id string required
• source string nullable
• rating number nullable
• rating_max number nullable
• text string nullable
• relative_date string nullable
• author object nullable
  • @type string (default: "GoogleHotelReviewAuthor")
  • name string required
  • profile_url string nullable
  • image string nullable
• source_url string nullable
• owner_reply string nullable
• owner_reply_date string nullable
• highlights array (default: [])

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 — Hotel not found for the given feature_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.