Agoda Reviews Scraper & API: Past the 10K Limit, from $0.75/1K avatar

Agoda Reviews Scraper & API: Past the 10K Limit, from $0.75/1K

Pricing

from $0.75 / 1,000 reviews

Go to Apify Store
Agoda Reviews Scraper & API: Past the 10K Limit, from $0.75/1K

Agoda Reviews Scraper & API: Past the 10K Limit, from $0.75/1K

Scrape Agoda guest reviews of any property, from every provider Agoda lists: score, title, comment, pros and cons, room, nights, traveller type, country, photos and hotel response. Retries Agoda's empty answers, reads past its 10,000-review limit. New-reviews-only monitoring and webhook.

Pricing

from $0.75 / 1,000 reviews

Rating

0.0

(0)

Developer

Alexis Morain

Alexis Morain

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Agoda Reviews Scraper

This Actor exports the guest reviews of any property on Agoda. Give it property URLs or hotel ids and it returns one row per review: the score out of 10, the title, the comment, the pros and cons when the guest filled them, the room, the nights, the stay dates, the traveller type, the guest's country, the photos and the hotel's response. It reads the reviews from every provider Agoda returns for the property, not only Agoda's own guests. A summary row per property comes with it.

It works as an Agoda reviews API: plain HTTP requests to the endpoint that Agoda's own review page calls, no browser, no residential proxy. Agoda's review list has two habits that silently cut the results of a naive scraper, and this Actor is built around them. Pricing is pay per event: $1.50 per 1,000 reviews on the Apify Free plan, down to $0.75 per 1,000 on Gold, plus $0.005 when a run starts.

What makes it different: it keeps asking when Agoda answers with an empty page, it reads past Agoda's 10,000-review list limit, and it covers all providers on the page. It also has a New reviews only mode with a webhook for scheduled monitoring.


What does Agoda Reviews Scraper do?

For each property you give it, the Actor:

  1. Finds the hotel id. A numeric id in the input is used as is. For a URL, the id is read from the property's Agoda page.
  2. Asks Agoda for the first page of reviews. The answer announces how many reviews each provider holds, which fixes the number of pages to read.
  3. Reads the pages newest first, 100 reviews per page and per provider, eight pages at a time, and retries every page that comes back empty.
  4. If the property has more than 10,000 reviews, reads it again traveller type by traveller type (see below) and removes duplicates.
  5. Pushes the reviews in batches of 100, and adds a summary row for the property unless you turn it off.

Agoda's two traps, and what the Actor does about them

Trap 1: about one answer in two comes back empty. Agoda's review endpoint returns 200 OK with no reviews roughly every other time, at random, whatever the pace and the session. In our recon of 21 October 2026, 11 of 20, then 7 of 20, then 9 of 20 pages came back full. Agoda's own website retries in the background. A scraper that treats the first empty page as the end of the list stops anywhere. This Actor takes the number of pages from the total the first answer announces, and retries each empty page (up to 14 attempts, on a new IP every fourth attempt) until the reviews arrive. It never takes an empty page for the end of the list.

Trap 2: the list stops at page 100. With 100 reviews per page, Agoda serves 10,000 reviews at most per request, whatever the sort order. For a property above that, the Actor first reads the 10,000 newest, then reads the property again for each of Agoda's six traveller groups. Each slice stays under the limit, and the slices add up to the total within one review (Baiyoke Sky Hotel, 21 October 2026). Reviews already seen are removed and never charged twice.

Also: several providers. Agoda mixes the reviews of its own guests with reviews from partner brands. On The Peninsula Hong Kong the first answer announces two providers: 353 reviews from Agoda and 336 from a second provider, 689 in total. Reading only the default provider loses nearly half of them. The Actor reads every provider the answer lists, and the summary row has a providers object with the count per provider.

Why scrape Agoda reviews?

  • Reputation monitoring for hotels listed on Agoda. Schedule a daily run in New reviews only mode and send a webhook to Slack, Make, Zapier or n8n.
  • Competitor research. Read what guests praise and criticise at the properties around yours, with pros and cons in separate fields when guests filled them.
  • Guest origin studies. Country, traveller type, room and length of stay are separate columns.
  • Sentiment analysis and LLM pipelines. Text, score and dates, one row per review.
  • Complete datasets. Properties above 10,000 reviews, which most scrapers cut at the limit.

Apify adds scheduling, an API for every run, integrations with Google Sheets, Slack, Zapier, Make and n8n, and exports to JSON, CSV and Excel.

How to scrape Agoda reviews

From the Apify console

  1. Click Try for free and open the Actor.
  2. Open the property on Agoda and copy its URL, for example https://www.agoda.com/the-peninsula-hong-kong/hotel/hong-kong-hk.html. Locale prefixes such as /fr-fr/ and query strings are fine.
  3. Paste it in Page URLs, one per line. A numeric hotel id such as 9729 works too.
  4. Set Max reviews per page URL. The default is 100, and 0 means every review.
  5. Optionally set a date window.
  6. Click Start, then export the dataset as JSON, CSV or Excel.

How to find the Agoda hotel id

Run the Actor with the URL. The placeId of the summary row is the hotel id. You can use it as input in later runs.

Which fields should I fill?

I want to...FillNotes
Try it oncePage URLsThe prefilled URL with 20 reviews costs about four cents on the Free plan.
Get every review of a propertyMax reviews per page URL = 0One charged result per review, so this is also your cost cap per URL.
Get recent reviewsOnly reviews from the last N days1 to 3650. Reads newest first and stops when a whole page is older than the date.
Get reviews since a fixed dateOnly reviews published afterYYYY-MM-DD. If both are set, the later date wins.
Monitor a propertyReview mode = New reviews onlyAdd a Monitoring key for several independent watches on one property.
Be told when a run endsWebhook URLReceives a JSON summary.
Get a reviews-only CSVAdd one summary row per URL = offOtherwise the dataset also holds one place row per property.

There is no language, score or traveller type filter for Agoda in this version, because Agoda does not offer one that we could validate. If you pass such a field through the API anyway, the run stops with a message saying so, instead of pretending to filter. Filter the dataset after the run.

Input examples

One property, the 100 newest reviews:

{
"startUrls": ["https://www.agoda.com/the-peninsula-hong-kong/hotel/hong-kong-hk.html"],
"maxReviewsPerPlace": 100
}

Every review of a property above 10,000 reviews:

{
"startUrls": ["https://www.agoda.com/baiyoke-sky-hotel/hotel/bangkok-th.html"],
"maxReviewsPerPlace": 0
}

Two properties, last 60 days, by URL and by id:

{
"startUrls": [
"https://www.agoda.com/baiyoke-sky-hotel/hotel/bangkok-th.html",
"9729"
],
"maxReviewsPerPlace": 0,
"lastDays": 60
}

Daily monitoring, with a webhook:

{
"startUrls": ["https://www.agoda.com/the-peninsula-hong-kong/hotel/hong-kong-hk.html"],
"maxReviewsPerPlace": 0,
"reviewMode": "new-only",
"webhookUrl": "https://hooks.example.com/agoda"
}

Details that need a word

  • Pros and cons are optional. positiveText and negativeText are filled only when the guest filled them. Otherwise they are null and the comment is in text.
  • language is Agoda's code, not a detection. The Actor passes on the language code Agoda attaches to the review. In our sample page of The Peninsula, a review written in Chinese carried en. Do not rely on language to detect the language of the text.
  • publishedAt is in UTC. Agoda gives the date with the property's local offset (+07:00 for Bangkok). The Actor converts it.
  • The first 10,000 are read twice on a very large property. The second read is how the Actor goes past the limit. Duplicates are dropped before anything is charged.
  • A failing URL does not stop the others. The run is marked failed only if every URL failed.
  • A slice that cannot be read is reported. If one of the traveller slices of a large property stays unreadable, the log says some older reviews may be missing, and the run is not recorded as a complete read in monitoring mode.
  • Proxy. Agoda cuts an IP that makes thousands of calls (we saw HTTP 502 on the whole domain from a home connection after about 2,000 calls). The Actor takes a new IP from the Apify datacenter proxy after each block. Keep the Proxy field at its default.

What data can it extract? Every output field

Each review is one dataset row with "type": "review".

FieldTypeDescription
typestringreview for a review, place for the summary row
sourcestringAlways agoda
reviewIdstringAgoda review id, stable across runs
ratingnumberGuest score, out of 10
ratingScaleintegerAlways 10
titlestringReview title
textstringThe comment
positiveTextstringPros, when the guest filled them
negativeTextstringCons, when the guest filled them
languagestringLanguage code Agoda gives the review (see the note above)
publishedAtstringReview date and time, ISO 8601 UTC
stayDatestringMonth of the stay, YYYY-MM
checkinDatestringCheck-in date, YYYY-MM-DD
checkoutDatestringCheck-out date, YYYY-MM-DD
nightsintegerLength of stay in nights
travelerTypestringAgoda's label, for example Couple, Solo traveler, Group, Family with young children, Family with teens
roomTypestringRoom the guest booked
helpfulVotesintegerHelpful votes on the review
photosarrayURLs of the guest's photos
reviewerNamestringDisplay name
reviewerLocationstringGuest country
reviewerCountryCodestringGuest country code, upper case
reviewerContributionsintegerNumber of reviews the guest wrote, null when Agoda gives none
ownerResponsestringThe hotel's response
ownerResponseDatestringDate of the response, as Agoda formats it
ownerResponderRolestringName or role of who responded
providerstringProvider shown by Agoda for the review, for example Agoda
placeIdstringAgoda hotel id
placeNamestringProperty name
placeTypestringAlways hotel on Agoda rows
placeUrlstringProperty page on Agoda
scrapedAtstringWhen the row was collected, ISO 8601 UTC

reviewUrl, originalLanguage, subRatings and reviewerProfileUrl are null on Agoda rows, and isMachineTranslated is false. They exist to keep the column names of the Tripadvisor and Booking.com Actors.

The summary row

One row per property, with "type": "place":

FieldDescription
placeId, placeName, placeType, placeUrlThe property
rating, ratingScaleAgoda's overall score out of 10
reviewsCountThe review count Agoda shows for the property
reviewsWithTextReviews with a comment, summed over providers: the reviews the list holds
providersReviews per provider id
reviewsDeliveredReviews this run delivered
inputThe URL or id you gave
scrapedAtCollection time

city, address and countryCode are null on Agoda summary rows.

Example output

A review row (read from a page of The Peninsula Hong Kong reviews):

{
"type": "review",
"source": "agoda",
"placeId": "9729",
"placeName": "The Peninsula Hong Kong",
"reviewId": "1026798197",
"rating": 10.0,
"ratingScale": 10,
"title": "Exceptional",
"text": "Everything about the stay was the best you can imagine. I'll definalety come back!",
"positiveText": null,
"negativeText": null,
"language": "en",
"publishedAt": "2025-09-19T23:27:00Z",
"stayDate": "2025-04",
"checkinDate": "2025-04-18",
"checkoutDate": "2025-04-20",
"travelerType": "Couple",
"roomType": "Deluxe Room",
"nights": 2,
"helpfulVotes": 0,
"photos": [],
"reviewerName": "Thomas",
"reviewerLocation": "Thailand",
"reviewerCountryCode": "TH",
"ownerResponse": null,
"provider": "Agoda"
}

A summary row (rating and review count left out):

{
"type": "place",
"source": "agoda",
"placeId": "9729",
"placeName": "The Peninsula Hong Kong",
"placeType": "hotel",
"reviewsWithText": 689,
"providers": {"332": 353, "3038": 336},
"input": "https://www.agoda.com/the-peninsula-hong-kong/hotel/hong-kong-hk.html"
}

The provider counts are the ones Agoda announced for the property in our recon of 21 October 2026.

How many Agoda reviews can it get? Measurements

Measured on the Apify platform on 21 October 2026:

PropertyReviews with a comment on AgodaDeliveredTime
Baiyoke Sky Hotel, Bangkok11,20611,166150 s

Without the traveller split, 10,000 is the most Agoda's list serves for this hotel. The 40 reviews missing from the 11,206 are the gap between the count Agoda announces and what its endpoint returned; we have not found where they go. We did not measure other properties above 10,000.

For The Peninsula Hong Kong, Agoda announces 353 + 336 = 689 reviews over two providers (recon). We did not record a delivered count for it on the platform.

Monitor new Agoda reviews: New reviews only mode

Set Review mode to New reviews only and schedule the Actor.

  • The Actor keeps a registry per property in a named key-value store of your account, agoda-reviews-registry, with the ids of the reviews already delivered.
  • Set Max reviews per page URL to 0 on the first run. A run stopped by the review limit, a spend limit, a timeout or unreadable pages is not recorded as complete, and the next run reads the full history again. Reviews already delivered are never returned or charged twice.
  • After a complete read, later runs read only reviews newer than that read minus 30 days, which covers reviews that appear after newer ones.
  • Skipped reviews are not charged. The status message says how many were skipped.
  • With a date window set (last N days or published after), the run is not recorded as a complete read.
  • A Monitoring key names the watch yourself. Without it, the watch is tied to the property.

Webhook at the end of the run

Fill Webhook URL and the Actor sends one JSON POST when it has finished reading (example values):

{
"actor": "agoda-reviews-scraper",
"runId": "abc123",
"datasetId": "def456",
"mode": "new-only",
"status": "succeeded",
"places": 1,
"reviews": 4,
"skippedAlreadySeen": 11166,
"targets": 1,
"failedTargets": 0,
"chargeLimitReached": false
}

status is succeeded, partial (some URLs failed) or failed (every URL failed). The URL is stored as a secret and is never written to the log. The call has a 15 second timeout, a 307 or 308 redirect is followed once, and a failure never changes the run's result. The webhook is not sent when the input is invalid.

Export Agoda reviews to CSV, Excel or JSON

Open the run, go to Storage or the Output tab, and choose JSON, CSV, Excel, HTML or XML. From the API:

https://api.apify.com/v2/datasets/<DATASET_ID>/items?format=csv&token=<YOUR_API_TOKEN>

For a reviews-only file, turn off Add one summary row per URL, or filter on the type column after the export. photos is a list and stays intact in JSON.

Using the Agoda reviews API from your code

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("alexmorain/agoda-reviews-scraper").call(run_input={
"startUrls": ["https://www.agoda.com/the-peninsula-hong-kong/hotel/hong-kong-hk.html"],
"maxReviewsPerPlace": 0,
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
if row["type"] == "review":
print(row["publishedAt"], row["rating"], row["travelerType"], row["title"])

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('alexmorain/agoda-reviews-scraper').call({
startUrls: ['9729'],
maxReviewsPerPlace: 0,
lastDays: 60,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
const reviews = items.filter((row) => row.type === 'review');
console.log(reviews.length, 'reviews in the last 60 days');

cURL

curl -X POST "https://api.apify.com/v2/acts/alexmorain~agoda-reviews-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"startUrls": ["9729"], "maxReviewsPerPlace": 50}'

This call waits for the run and returns the items. For big properties, start the run with POST /v2/acts/alexmorain~agoda-reviews-scraper/runs and read the dataset when it ends.

What people use it for

Hotel reputation monitoring

List your properties, schedule a daily New reviews only run, and send the webhook to a chat channel. A run with a few new reviews costs about one cent on the Free plan.

Comparing providers

The provider column and the providers counts in the summary row show how many reviews come from Agoda's own guests and how many from partner brands.

Guest origin and room analysis

reviewerCountryCode, travelerType, roomType and nights are separate columns, so a pivot table gives the average score by country or room.

Large property datasets

For a property above 10,000 reviews, the traveller split gives you the whole list, with duplicates removed.

Agoda Reviews Scraper pricing

You pay per event. There is no monthly rental.

EventFree planBronzeSilverGold and above
Review (per 1,000)$1.50$1.30$1.10$0.75
Summary row (per 1,000)$2.00$1.80$1.60$1.00
Actor start (per run, per GB of memory, minimum one)$0.005$0.005$0.005$0.005

The Actor runs with 512 MB, so the start fee is $0.005 per run. The tier that applies is the one of your Apify plan.

JobFree planGold plan
100 reviews, one property$0.157$0.081
1,000 reviews, one property$1.507$0.756
All 11,166 reviews of Baiyoke Sky Hotel$16.76$8.38
Daily monitoring run with 3 new reviews$0.0115$0.0083

Each worked example is the reviews plus one summary row ($0.002 Free, $0.001 Gold) plus the start fee. The $5 of monthly credit in the Apify Free plan covers about 3,300 reviews.

Cost control. Max reviews per page URL caps each URL. You can also set a maximum cost for the run in the Apify run options. The Actor pushes reviews through the platform's charging check, so it stops at the limit instead of passing it; we checked this on the platform before publishing. Reviews already delivered in New reviews only mode are not charged again.

Limits and what this Actor does not do

  • No filter on language, score or traveller type. Filter the dataset after the run.
  • The language column is Agoda's code, which can differ from the language of the text.
  • Small gap on very large properties. Baiyoke Sky Hotel: 11,166 of 11,206.
  • Agoda empty answers make runs slower than the page count suggests. About half of the requests are retried.
  • The summary row has no city, address or country.
  • No sub-scores per review (cleanliness, location and so on).
  • Property URLs only. The URL must look like agoda.com/<name>/hotel/<city>.html, or a review page of the same property. City and search pages are not read.
  • Provider coverage is what Agoda lists. The Actor requests a fixed list of nine provider ids and reads those Agoda announces in its answer.

FAQ

Is there an Agoda reviews API?

This Actor does not use an official Agoda API. It reads the review data that the public property pages load and returns it as JSON through the Apify API. You call it with an Apify token.

How do I scrape Agoda reviews?

Paste the property URL or hotel id in the Actor, set the maximum number of reviews, press Start, and download the dataset as CSV, Excel or JSON.

How do I export Agoda reviews to CSV?

Run the Actor, open the dataset and choose CSV. Turn off the summary row if you want only reviews in the file.

Why does my Agoda scraper stop after a few pages?

Agoda answers about every other request with an empty list. A scraper that takes the first empty answer as the end of the list stops anywhere. This Actor retries empty pages until the reviews arrive.

Can I scrape more than 10,000 Agoda reviews from one property?

Yes. Agoda's list stops at page 100, which is 10,000 reviews at 100 per page. The Actor reads the rest traveller type by traveller type and removes duplicates. We got 11,166 of 11,206 reviews on one Bangkok hotel.

Why is the review count lower than the number on the Agoda page?

The Actor returns reviews that have a comment, which is what the list holds. The summary row shows both numbers, reviewsCount and reviewsWithText. Agoda announces slightly more reviews than it returns (40 of 11,206 on Baiyoke Sky Hotel).

Does it get the reviews from Agoda's partner providers?

Yes. It reads every provider that Agoda lists for the property, and provider says which one each review comes from. On The Peninsula Hong Kong, Agoda lists two providers.

Can I filter by language or score?

Not in this version. Filter the dataset on rating or language after the run. Keep in mind the language caveat above. Use Max reviews per page URL or a date window to keep the cost down.

Does it need an Agoda account or a browser?

No. Plain HTTP requests through the Apify datacenter proxy.

How do I find the Agoda hotel id?

Run the Actor once with the URL and read placeId in the summary row. You can use that number as input.

How do I monitor new Agoda reviews?

Use New reviews only with a daily or weekly schedule and add a webhook. See the monitoring section.

The Actor reads pages that anyone can open without logging in. The output contains data that guests made public: a display name, a country, the review text. Personal data is protected by the GDPR in the European Union and by similar laws elsewhere. Use the data for a legitimate purpose, check Agoda's terms and take legal advice for your own use. This is not legal advice.

Integrations, exports and support

Connect the dataset to Google Sheets, Slack, Zapier, Make or n8n with Apify's integrations, or use the Apify API and client libraries. Runs can be scheduled from the console.

Something not working, or a field you need? Open an issue in the Issues tab. The same developer publishes Tripadvisor Reviews Scraper, Booking.com Reviews Scraper and Airbnb Reviews Scraper, with the same column names.

Guide and use cases

Use cases for outbound and automation, the output fields, pricing and common questions are on the Agoda Reviews Scraper page of my site. The Reviews family page puts it side by side with the other scrapers of the same family.