Agoda Reviews Scraper

This Agoda reviews scraper exports guest reviews for hotels worldwide, with ratings, original review text, languages, stay details and hotel replies. Paste hotel URLs or hotel IDs, choose a provider and collect a set number of reviews per hotel.

This actor is useful for hotel groups, reputation teams and travel researchers who need consistent review records across several properties. Agoda has broad hotel coverage in Asia, and the same input format works for properties in other regions. Review IDs and hotel IDs make it possible to match repeated exports to existing records in your own database.

What this Agoda reviews scraper collects

Each dataset row represents one actual review displayed by Agoda. The actor includes a rating on a ten-point scale, the review title, the original comment when available, the publication time and the guest's display name. Additional fields include positive and negative feedback, country, traveler type, room type, length of stay, check-in and check-out dates, review photos and the hotel's response. These fields depend on what the source publishes for each review.

Agoda displays both its own guest reviews and reviews provided by Booking.com. Use providers to select agoda, booking or all. The platform field remains agoda, because that is where the exported review was displayed. The separate provider field identifies the review's origin. Booking records often lack guest country, room and stay information; missing fields remain absent or null rather than being inferred.

Input

Set hotels to a list containing HTTPS Agoda hotel URLs, Agoda review-page URLs or numeric hotel IDs written as strings. A hotel URL can include a language prefix and booking query parameters. The collection concerns hotel reviews; dates and guest counts in a booking URL do not limit the review export. A duplicate hotel is collected once, including when its URL and ID appear in the same list.

Set max_reviews to an integer from 1 to 5,000. The default is 100. This limit applies per unique hotel and combines the selected providers. For example, selecting all with a limit of 100 returns at most 100 reviews for that hotel, across Agoda and Booking together. Selecting agoda applies the same limit exclusively to Agoda reviews.

The sort options are recent, rating_high, rating_low and helpful. Recent is the default. These settings request the source's order, so they should not be treated as a guarantee of strict chronological order for Booking reviews. In particular, an imported Booking review can appear before a newer imported review.

The optional languages list filters original review languages. Supported codes are en, fr, de, it, es, ja, zh, ko, ru, nl, th, sv, id, no, da, he and pt. An empty list selects all languages. English and Chinese include the source's available regional variants. Unknown codes cause an input error.

Language selection follows Agoda's own filter. A selected review can lack a language label, or carry a different label in the source metadata. Such reviews remain included; the actor reports the available label and leaves a missing label unset.

Output

The default dataset contains only delivered reviews. The stable identifiers are place_id and review_id, both strings. Ratings retain Agoda's ten-point scale, recorded explicitly as rating_scale: 10. Publication and hotel-response timestamps use UTC, while stay dates keep the calendar date shown for the visit.

When Agoda supplies an original comment alongside a machine translation, text contains the original and text_translated contains the translation. The same rule applies to title and title_translated. For Booking reviews without a general comment, text joins the available positive and negative comments with a blank line. The separate positive_text and negative_text fields preserve those components.

A hotel response appears as reply_text, with its available timestamp and author. Those fields are omitted when there is no response. Guest verification is indicated for Agoda reviews when supported by the source; the actor does not infer verification for Booking records.

The key-value store also contains a hotels record with hotel names, URLs, ratings, displayed review totals, rating categories and available review totals by provider. Hotel profiles accompany delivered reviews and do not create additional review charges. The OUTPUT record contains delivery counts and collection status. Export the dataset to JSON, CSV, Excel or another supported Apify format for further analysis.

Example output

This is one real review from Zoku Amsterdam (hotel ID 926696), exactly as the actor delivers it:

{
  "source": "agoda-reviews",
  "platform": "agoda",
  "fetched_at": "2026-10-11T23:18:15.400Z",
  "review_id": "1124087051",
  "place_id": "926696",
  "place_name": "Zoku Amsterdam",
  "place_url": "https://www.agoda.com/zoku-amsterdam/reviews/amsterdam-nl.html",
  "provider": "agoda",
  "rating": 9.2,
  "rating_scale": 10,
  "rating_text": "Exceptional",
  "title": "Neat hotel with working space and greenhouse",
  "text": "Haven't stayed in a place like this before. Would recommend! ",
  "positive_text": null,
  "negative_text": null,
  "title_translated": null,
  "text_translated": null,
  "language": "en",
  "language_raw": "en",
  "author_name": "Oliver",
  "author_country": "United States",
  "author_country_code": "US",
  "traveler_type": "Solo traveler",
  "room_type": "Loft",
  "nights": 4,
  "stay_check_in": "2026-05-22",
  "stay_check_out": "2026-05-26",
  "stay_month": "May 2026",
  "published_at": "2026-05-26T00:26:00.000Z",
  "likes": 0,
  "is_verified": true,
  "photos": [],
  "reviewer_review_count": 0
}

Use cases

• Reputation monitoring for hotel chains: pull the newest reviews of every property each week and compare scores by guest country or traveler type.
• APAC market research: collect Japanese, Chinese, Korean and Thai reviews in their original language to see what guests in each market praise or complain about.
• Review analytics tools: feed consistent review_id, place_id and rating fields into dashboards and sentiment models.
• Service recovery: filter low-rated reviews with rating_low sorting and check whether the hotel has replied.

How this compares with other Agoda review scrapers

Many Agoda scrapers return hotel listings and prices and add reviews as a side feature. This actor focuses on reviews only: one row per review, original and translated text kept apart, guest country, traveler type, room type and stay dates as separate fields, the hotel's reply included, and a cursor-based continuation for large hotels. You choose between Agoda's own guests, Booking.com reviews shown on Agoda, or both, and you pay only for reviews actually delivered.

Limits and continuation

The available collection is one source dataset per hotel, using the selected sorting and languages. Agoda's displayed review count can exceed the number accessible within that dataset. The actor collects up to 5,000 unique reviews per provider in a selected collection and removes repeated IDs. This is a collection limit, not a promise that every hotel will supply that many records.

Large runs continue automatically until the per-hotel limit is reached, the source is exhausted or the run's available time ends. The lower-level response can include an opaque cursor and partial status. To resume manually, reuse that cursor with the same hotel list, review limit, providers, sorting and languages. A missing hotel or a collection failure produces a warning and does not create a diagnostic review row. Other hotels can still produce useful results.

Pricing

Billing is per delivered review, using the review event shown in the actor's current pricing panel. Empty results create no review charges. Hotel summaries and warnings do not count as reviews. The requested limit is a maximum; billing follows the records actually delivered after duplicate removal and applicable delivery limits.

Runs by users without a paid Apify plan deliver at most ten reviews in total. This is a delivery cap, and delivered records still follow the actor's current event price. Paid users can request the full supported limit. Consult the pricing panel before starting a large export, and set a run spending limit when appropriate for your workflow.

FAQ

Can I collect only Agoda reviews?

Yes. Set providers to agoda. Select booking for Booking reviews displayed by Agoda, or leave the default all to combine both. The per-hotel review limit applies to the selected records together.

Why are some guest details missing?

The source does not publish every field for every review. Booking reviews generally have less guest and stay metadata. The actor returns what is available, without guessing a guest's country, room or visit dates.

Are ratings converted to five stars?

No. Ratings retain Agoda's ten-point scale. Use rating_scale when comparing these records with exports from platforms that use a five-point scale.

Can the export include every displayed hotel review?

The actor can return fewer records than the displayed total because the accessible source dataset, selected languages and provider limits determine availability. Check available totals and warnings when evaluating coverage. Different sorts and language filters represent separate collection choices, not a guarantee of complete historical coverage.

Can I use the review ID as a permanent review link?

The review ID supports record matching. Agoda does not expose a public URL for each exported review, so place_url links to the hotel's review page instead.