Agoda Reviews Scraper

Export public Agoda hotel reviews, ratings, traveler details and property context into a dataset you can download or read through the API.

Quick start

1. Open Input and paste a public Agoda hotel URL. Replace the illustrative URL below with your chosen property. Choose Automatic for the existing managed-proxy setup or Direct to use no proxy.
2. Set a small per-hotel limit and choose a supported sort order.
3. Click Start, then open the dataset to review the saved rows.

{
  "hotelUrls": [
    {
      "url": "https://www.agoda.com/example-hotel/hotel/example-city.html"
    }
  ],
  "propertyIds": [],
  "maxReviewsPerHotel": 10,
  "sort": "mostRecent",
  "language": "en-us",
  "currency": "USD",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a small preconfigured example, then adjust the hotel and review limit for your own work.

• Marina Bay Sands review sample — collect up to 30 reviews with most-helpful sorting.
• Agoda Seasonal Review Monitor — collect up to 10 most-recent reviews for comparison in your own workflow.
• Monitor Recent Negative Agoda Reviews — collect up to 10 reviews with lowest-rating-first sorting. The Actor does not filter by date, perform sentiment analysis or send alerts.

What you get

• Export Agoda hotel reviews: Save public review titles, text, ratings, dates, stay dates, and traveler context.
• Collect property context: Include hotel name, city, country, overall rating, rating text, and total review count when available.
• Analyze review segments: Use traveler type, room type, reviewer country, length of stay, and helpful votes.
• Run multiple hotels: Process several hotel URLs or property IDs in one run.

Who is it for?

Hotel reputation teams, hospitality researchers and travel editors who need source-linked guest feedback and property context.

Common workflows

Compare nearby properties. Export a bounded review sample for each hotel with the same language and sort order. Group ratings and guest comments by property in your spreadsheet. The Actor collects reviews. Your own analysis decides which themes or comparisons are meaningful.

Review guest segments. Use the saved traveler type, room type, stay date and reviewer country when Agoda supplies them. For example, compare comments about breakfast across family and business stays. Missing fields remain missing, so a segment is only as complete as the source.

Prepare a recurring review sheet. Save a task for your selected properties and schedule it. Deduplicate exports by review identity and compare them in your own workflow before treating a row as new. The Actor does not send built-in sentiment alerts.

Input settings

Setting	JSON key	What to enter
Hotel URLs	hotelUrls	Public Agoda hotel page URLs or /accom/property?propertyId=123456 links, including locale prefixes such as /tr-tr/. Property links use the numeric ID directly without an extra hotel-page request.
Property IDs	propertyIds	Agoda property IDs when you already know them.
Maximum reviews per hotel	maxReviewsPerHotel	Maximum saved rows per hotel. The input form defaults to 10. Omitting this key in API input uses 25.
Sort	sort	mostHelpful, mostRecent, highestRating or lowestRating.
Language	language	Locale such as en-us.
Currency	currency	Currency code such as USD, EUR, or GBP.
Resume checkpoint	resumeFromCheckpoint	Opt in to remaining sources from a matching accessible RUN_CHECKPOINT. Missing checkpoint data is an error. This does not discover a previous run’s store automatically.
Connection	connectionMode	automatic (default) or direct. Direct never enables paid fallback.
Advanced proxy settings	proxyConfiguration	Optional managed settings or your own proxy pool. See input help for precedence and costs.

Property links keep the submitted URL in hotelUrl. City and country remain null when the URL does not contain a location slug; property name, ratings and reviews still come from Agoda's matched review response. Locale prefixes do not override the selected language.

Output data

Field group	Fields
Property	hotelUrl, propertyId, hotelName, city, country
Property ratings	overallRating, overallRatingText, totalReviews
Review identity	reviewId, reviewTitle, reviewDate, stayDate
Review content	reviewText, rating, ratingText
Traveler context	travelerType, roomType, reviewerName, reviewerCountry, lengthOfStay
Management reply, when available	ownerResponse, ownerResponseAuthor, ownerResponseDate
Extra metadata	helpfulVotes, provider, scrapedAt

The following synthetic example illustrates the record shape. It is not a captured guest review. propertyId is numeric and lengthOfStay is a number or null.

{
  "hotelUrl": "https://www.agoda.com/example-hotel/hotel/example-city.html",
  "propertyId": 123456,
  "hotelName": "Example Hotel",
  "city": "Bangkok",
  "country": "TH",
  "overallRating": 8.7,
  "overallRatingText": "Excellent",
  "totalReviews": 2450,
  "reviewId": "987654321",
  "reviewTitle": "Great location",
  "reviewText": "Clean room and friendly staff.",
  "rating": 9.2,
  "ratingText": "Exceptional",
  "reviewDate": "2026-06-20",
  "stayDate": "2026-06",
  "travelerType": "Couple",
  "roomType": "Deluxe Room",
  "reviewerName": "Example Guest",
  "reviewerCountry": "Portugal",
  "lengthOfStay": 2,
  "helpfulVotes": 3,
  "provider": "Agoda",
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A start event is charged after input and checkpoint validation, followed by a review event for each saved review row. A run with no review rows can still incur the start event.

The Actor stops further collection when the remaining review-event budget cannot cover another row. Check RUN_SUMMARY for a budget-limited result. Property aggregates are not charged as invented review rows.

Check the live Pricing tab for current rates. Compute, storage, proxy traffic and other platform usage may add costs.

Tips for best results

• Test one hotel first. Use a small limit to check the locale and available fields.
• Keep comparisons consistent. Use the same language, currency and sort order across properties.
• Use full public URLs or known IDs. Check that each input points to the hotel you intend.
• Inspect partial outcomes. Read RUN_SUMMARY alongside saved reviews when one property fails. Useful records from other hotels remain available. A partial result does not mean every requested hotel was fully collected.

Limits and caveats

• The actor exports public Agoda review data. It does not access private booking or account data.
• Some hotels may hide or delay review fields depending on region, language, or availability.
• Processing is capped at ten minutes, even if a longer platform timeout is requested. Large inputs may be incomplete.
• Agoda can change review sorting, pagination, and page structure.
• Reviewer names and countries can be missing or partially anonymized.

Long or blocked lookups can stop before all requested reviews are collected. A matching accessible RUN_CHECKPOINT can supply remaining sources when resumeFromCheckpoint is enabled. This is not automatic cross-run incremental monitoring.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~agoda-reviews-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"hotelUrls":[{"url":"https://www.agoda.com/example-hotel/hotel/example-city.html"}],"propertyIds":[],"maxReviewsPerHotel":10,"sort":"mostRecent","language":"en-us","currency":"USD","proxyConfiguration":{"useApifyProxy":false}}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  "hotelUrls": [
    {
      "url": "https://www.agoda.com/example-hotel/hotel/example-city.html"
    }
  ],
  "propertyIds": [],
  "maxReviewsPerHotel": 10,
  "sort": "mostRecent",
  "language": "en-us",
  "currency": "USD",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
};
const run = await client.actor('fetch_cat/agoda-reviews-scraper').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import json
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run_input = json.loads('''{
  "hotelUrls": [
    {
      "url": "https://www.agoda.com/example-hotel/hotel/example-city.html"
    }
  ],
  "propertyIds": [],
  "maxReviewsPerHotel": 10,
  "sort": "mostRecent",
  "language": "en-us",
  "currency": "USD",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}''')
run = client.actor('fetch_cat/agoda-reviews-scraper').call(run_input=run_input)
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Agoda Reviews Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Agoda Reviews Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/agoda-reviews-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Agoda Reviews Scraper by Fetch Cat, or give it the identifier fetch_cat/agoda-reviews-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Collect up to 10 recent public Agoda reviews for each of these hotel URLs.”
• “Collect up to 10 reviews per hotel for these three supplied Agoda URLs in en-us and USD, then compare the returned ratings.”
• “Retrieve up to 10 reviews for this supplied Agoda property ID with mostRecent sorting, then summarize room-related comments from the saved rows.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

Privacy and data handling

The Actor retrieves public hotel review data, not private booking or account records. Results are stored in your Apify run storage. Error diagnostics can include secret-redacted input and request context to help investigate extraction failures. Avoid including unnecessary personal or sensitive data in your input.

FAQ

Does it require an Agoda account?
No. It extracts public review data.

Can I export to CSV or Excel?
Yes. Download the Apify dataset as CSV, Excel, JSON, XML, RSS, or through the Dataset API.

Can I scrape several hotels in one run?
Yes. Add multiple hotel URLs or property IDs.

Why are some fields empty?
Agoda does not expose every review field for every hotel, locale, or review.

Can a successful run contain no reviews? Yes. A matching first-page response that explicitly confirms no written comments succeeds with an empty dataset: RATINGS_ONLY_NO_WRITTEN_REVIEWS when aggregate ratings exist, otherwise NO_REVIEWS_AVAILABLE, in the source's RUN_SUMMARY reason. Aggregate rating totals are not written-review counts. Existing review rows, including rating-only rows returned by Agoda, keep their rating fields. The Actor never invents a review row from a property aggregate. An empty response alone does not prove there are no reviews: positive written-comment counts, mismatched targets, malformed responses and exhausted request failures remain actionable failures. Mixed batches retain successfully saved reviews and report failed sources separately.

Related Actors

• Trip.com Hotels Scraper — collect public hotel listing cards with available names, ratings, links and visible prices.
• Airbnb Reviews Scraper — export guest review text and ratings for Airbnb listings.
• ProductReview.com.au Scraper — retrieve consumer review records from ProductReview.com.au.
• Google News Scraper — retrieve news headlines, publisher details, links and available feed descriptions for a hotel or travel topic.
• Website Content Crawler Lite — extract readable content from public hotel or destination web pages.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥