Agoda hotel reviews by hotel name, URL or id, with the Booking.com reviews Agoda shows. One row per review: 0-10 rating, title, text, positives, negatives, language, stay dates, room, reviewer country, photos, hotel reply, source. Free filters before billing: max score (negative reviews), text only.
2026-10-16 — Keyword Planner and locale documentation
Validated search terminology against Google Ads Keyword Planner and Store shelves. Added localized usage guidance and bounded examples; retained existing English phrases. Clarified locale limitations where measured. No runtime, output fields, defaults, or pricing changed.
1.0 — listing and input form reworded, 2026-10-11
No behaviour, output or price changed; the same inputs return the same rows.
The input form is reordered: which properties (names now second), how many reviews and in what order, then the two filters that cut the bill (maxRating, requireText), the free hotel row, locale, pacing and proxy. Nothing was renamed or removed.
Every input now says what to pass, with an example, its default and what it costs.maxReviewsPerHotel states that the default 200 is up to $1 per property, that 0 can cost $5+ on a busy hostel and is capped at 6,000 per run, and that maxRating and requireText apply after the cap (pair maxRating with lowest_rated); locale says what Agoda translates and where the original text is; includeHotelRow says the row carries no scores; hotelIds says why an empty answer is reported as an error.
The description and pricing text name the Booking.com reviews Agoda shows (source), the translated/original text pair, everything that is never charged, that there is no start fee, and that a run stops at the maximum cost you set.
seo.json: native nouns (รีวิวโรงแรม, ホテル 口コミ, 호텔 리뷰, ulasan hotel) in the meta description.
README: a section mapping common requests to the exact input, with the output row and the status contract.
2026-08-30
Reliability: a run that cannot act on its input — a URL from the wrong site, a name nothing resolves to, an empty target list, a number outside the documented range — now ends cleanly with the reason on the run card instead of as a failed run. Nothing is charged in either case; a blocked or throttled source still fails loudly.
Store listing: moved into the categories buyers actually browse (the old Business category has no Store page).
1.0 — 2026-08-26
First release.
Every guest review of any Agoda property: rating on Agoda's 0-10 scale and the familiar 5-star scale, rating word, title, comment, separate positives and negatives, the language it was written in, stay dates and length, room type, reviewer name and country, the hotel's public reply and which source the review came from.
Three ways in: a plain property name (resolved through Agoda's own autocomplete — no id hunting), Agoda hotel URLs (the numeric id is read from the page for you), or the numeric ids directly. A name, its URL and its id all count as the same property and are harvested once.
Order by most recent, highest rated, lowest rated or most relevant.
Two cost controls that filter before billing: maxRating keeps only reviews at or below a score, and requireText drops the score-only reviews that have no words. Filtered reviews are never charged.
Billing: pay per delivered review row. Hotel rows, status rows, filtered reviews, properties with no reviews and failed properties are all free, and a property is harvested once per run whether you give its URL, its id, or both.
Reliability: a throttled call from Agoda answers 200 with no reviews at all — that is detected and retried on a fresh IP instead of reporting the property as having none.
![Agoda [Only 💰$1] Reviews Scraper API: Guest Ratings & Comments avatar](https://images.apifyusercontent.com/V5PHxm83P-i51KMNmtBqU2jY3E7dBa3p0jRcJRSxwVA/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vbmduOHZSRVNUa3NleVdFNnAtYWN0b3ItT21VcDN5em02dFdCZjVTaG4tTW15Y2hPSWtBNS1hZ29kYS1sb2dvLXBuZ19zZWVrbG9nby0zNzEwMjUucG5n.webp){kind=avatar}
