/agoda/hotels/reviews

POST /api/agoda/hotels/reviews

Price: 10 credits

Get paginated guest reviews for an Agoda hotel by property id (or hotel URL). Each review includes the rating and rating label, title, full review text (or separate pros and cons for partner reviews), the review source, reviewer name, country, traveler type, room type, length of stay, helpful/unhelpful vote counts, review and stay dates, and any guest-uploaded photos.

How to use it

Fetch guest reviews for one Agoda hotel by numeric property id or a hotel URL containing hotelId. Returns a list of reviews, each with id, rating, rating_text, title, text, pros, cons, provider (Agoda / Booking.com / Priceline), author, country, country_code, traveler_type, room_type, length_of_stay, helpful_count, unhelpful_count, created_at, check_in_date, check_out_date and images. Set count for how many reviews to return and sort to order them (recent, rating_high, rating_low, helpful).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Agoda property id or a hotel URL containing it (examples: "10696", "https://www.agoda.com/shangri-la-hotel-bangkok/hotel/bangkok-th.html?hotelId=10696"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Order in which reviews are returned (default: "recent"; one of: "recent", "rating_high", "rating_low", "helpful")

Response

• @type string (default: "AgodaReview")
• id string required
• rating number nullable
• rating_text string nullable
• text string nullable
• pros string nullable
• cons string nullable
• provider string nullable
• author string nullable
• country string nullable
• country_code string nullable
• traveler_type string nullable
• room_type string nullable
• length_of_stay integer nullable
• helpful_count integer nullable
• unhelpful_count integer nullable
• created_at string nullable
• check_in_date string nullable
• check_out_date string nullable
• images 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 (well-formed but nonexistent property 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.