/expedia/hotels/reviews

POST /api/expedia/hotels/reviews

Price: 1 credit

Get Expedia guest reviews for a hotel by hotel id (numeric, h-prefixed, or a hotel page URL): each review has the guest rating and label, title, text, author, submission date, language, verified flag, length of stay, liked/disliked themes, helpful votes, guest photos and the property's management response.

How to use it

Fetch guest reviews for a single Expedia hotel by id (numeric like 66525849, h-prefixed like h66525849, or a hotel URL containing .h{id}.), most recent first. Each item has id, rating (out of 10), rating_label, title, text, author, created_at, locale, is_verified, stay_detail, themes, helpful_count, photos and management_response. Set count to the number of reviews you want.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Expedia hotel id (numeric or h-prefixed) or a hotel page URL containing it (examples: "66525849", "h66525849", "https://www.expedia.com/x.h66525849.Hotel-Information"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "ExpediaHotelReview")
• id string required
• rating number nullable
• rating_label string nullable
• text string nullable
• author string nullable
• created_at string nullable
• locale string nullable
• is_verified boolean (default: false)
• stay_detail string nullable
• themes array (default: [])
• helpful_count integer nullable
• photos array (default: [])
• management_response 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 — Hotel not found (well-formed but nonexistent hotel 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.