Agoda Hotels Scraper

Export public Agoda hotel search listings with displayed prices, guest ratings, review counts, locations, amenities, and property URLs. Search using a public Agoda search URL or an Agoda city ID. Download the dataset as JSON, CSV, or Excel.

This Actor collects listing cards, not individual room offers or review text. Prices and available fields vary with dates, guest settings, locale, and what Agoda displays.

Quick start

1. Paste a public Agoda search URL or supply cityId.
2. Start with maxItems set to 10 and check the destination and currency.
3. Run the Actor and open its dataset. Inspect RUN_SUMMARY for skipped searches or partial completion.

{
  "searchUrls": [{ "url": "https://www.agoda.com/search?city=9395&adults=2&rooms=1" }],
  "maxItems": 10,
  "currency": "USD",
  "language": "en-US"
}

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 public example to see its settings before starting a run:

• Compare Paris hotel listings from Agoda in EUR
• Scrape Bangkok hotel prices from Agoda

What you get

One row per saved hotel search listing, with a property link and available price, guest score, review count and amenity fields. Keep the effective search URL and collection time for context. Optional values may be missing, and these rows do not confirm booking availability or final totals.

Who is it for?

• Travel analysts: Compare visible hotel supply and ratings across destinations.
• Revenue teams: Collect comparable price snapshots using consistent dates, guests, and currency.
• Data teams: Export public accommodation listings for dashboards and market research.

How you can use the data

• Review Bangkok hotel supply. Use city ID 9395 or your public Agoda search URL and a small maxItems. Export name, url, reviewScore and reviewCount for a manually reviewed hotel sheet.
• Prepare comparable price snapshots. Set the same future stay dates, guests, rooms and currency for each search. Keep searchUrl and scrapedAt with visible prices so the conditions of each observation remain clear.
• Compare a property's later listing. Join your own exports by propertyId when present, or retain the property URL for manual matching. Check missing prices and changes against the source rather than treating them as confirmed availability changes.

Input settings

searchUrls takes precedence over cityId and destination. When URLs are omitted or empty, the Actor builds one city search. cityId defaults to Bangkok (9395). destination is optional text for that city search, not an automatic city-ID lookup.

Explicit date, guest, currency, and locale settings can override values in supplied URLs. Review defaults in the input form when reusing a saved search.

Setting	JSON key	Guidance
Agoda search URLs	searchUrls	Up to 20 public HTTPS Agoda URLs, using { "url": "…" } entries. Use search-result pages, not individual hotel pages.
City ID	cityId	Used only when URLs are absent. Default 9395 is Bangkok.
Destination text	destination	Optional description accompanying the city ID.
Maximum hotels	maxItems	Total saved-listing limit across searches, from 1 to 500. Set explicitly for predictable bounds.
Currency	currency	Three-letter preferred currency, such as USD or EUR. The form defaults to USD.
Language / locale	language	For example en-US. Affects displayed content.
Stay dates	checkIn, checkOut	Optional YYYY-MM-DD dates. Check-out must follow check-in when both are supplied. Choose future dates for current comparisons.
Guests and rooms	adults, children, rooms	Form defaults: 2 adults, 0 children, 1 room.
Delay between searches	requestDelayMs	0–10000 milliseconds. Default 1000.
Proxy configuration	proxyConfiguration	Optional Advanced setting. Direct access is the default. See field help for supported proxy settings and limitations.

A bounded city-ID recipe:

{
  "cityId": "9395",
  "destination": "Bangkok",
  "adults": 2,
  "rooms": 1,
  "maxItems": 10,
  "currency": "USD"
}

Output data

Each dataset row represents a hotel/property listing. Optional information can be null or an empty array. A missing price or amenity is not proof that the hotel lacks it.

Fields	Meaning and limits
name, url, propertyId	Listing name, property URL and ID when discoverable.
price, currency	Displayed price and detected or requested currency. Not a guaranteed final booking total.
reviewScore, reviewCount	Guest score on Agoda's 0–10 scale and visible review count. No review text.
starRating	Visible property star rating, when available.
location, address	Displayed area/location text. address repeats that text, not a verified street address.
latitude, longitude	Currently null. Coordinates are not extracted.
amenities, imageUrl	Visible amenity labels and a listing image URL, when available.
taxesFeesNote	Displayed tax-related text, when found. Not a normalized tax breakdown.
availability	false when an unavailable/sold-out label is detected, otherwise null. Not a confirmed booking-availability flag.
searchUrl, scrapedAt	Effective search URL and collection timestamp.

Example output shape (illustrative, not a collected hotel):

{
  "name": "<displayed hotel name>",
  "url": "<public property URL>",
  "price": null,
  "currency": "USD",
  "reviewScore": null,
  "amenities": [],
  "latitude": null,
  "longitude": null
}

RUN_SUMMARY in the key-value store reports saved counts, processed searches, failed search URLs, empty-page reasons, and incomplete searches. A PARTIAL summary preserves useful listings but means not every search completed. PENDING_WORK, when present, describes unfinished searches. It does not resume them automatically.

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

The Actor uses pay-per-event pricing: start is charged when a validated run starts, and item is charged per hotel listing saved. It does not emit paid error/status rows. A start charge can apply even when no listings are saved.

Use a small maxItems and a short URL list to bound work. Budget stops are explained in RUN_SUMMARY. Optional proxy usage and other platform usage may add costs, and extracted hotel prices are separate from Actor fees.

See the live Pricing tab for current rates and plan discounts.

Tips for best results

• Check the effective search URL. Supplied URLs take precedence over the city ID, while explicit dates, guest settings, currency and locale can override URL values.
• Use future stay dates for a price comparison. Keep dates and occupancy consistent and inspect the currency reported with each price.
• Review RUN_SUMMARY before using the export. Check failed or incomplete searches alongside saved listings rather than assuming every input completed.

Limits and caveats

Processing is capped at nine minutes from the original run start. Automatic restarts do not resume extraction. Existing saved results remain accessible. Start a new run if you need another search.

• Public listings only: No login, private rates, room-level offers, booking transactions, or review-text extraction. This is not an official Agoda API.
• Partial coverage: maxItems is a ceiling, not a promise. The Actor inspects at most ten result pages per search and may stop earlier when results stop advancing or the run deadline approaches.
• Access restrictions: Agoda can block requests or display an error page. A proxy does not guarantee success. Completed public-page extraction with zero usable listings succeeds with an empty dataset and a reason in RUN_SUMMARY. This does not prove the target is private or deleted. Unresolved access challenges, execution, billing, and essential storage errors still fail when no safe partial result is available.
• Mixed searches: Saved listings can remain useful when another search fails. Inspect RUN_SUMMARY rather than assuming every input completed.
• Price comparisons: Keep stay dates, occupancy, currency, locale, and collection time comparable. Displayed prices may omit taxes or depend on availability.
• Repeated snapshots: You can run the Actor manually or integrate it with your own workflow. There is no built-in recurring monitor or automatic date refresh.

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-hotels-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchUrls": [
    {
      "url": "https://www.agoda.com/search?city=9395&adults=2&rooms=1"
    }
  ],
  "maxItems": 10,
  "currency": "USD",
  "language": "en-US"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/agoda-hotels-scraper').call({
  "searchUrls": [
    {
      "url": "https://www.agoda.com/search?city=9395&adults=2&rooms=1"
    }
  ],
  "maxItems": 10,
  "currency": "USD",
  "language": "en-US"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/agoda-hotels-scraper').call(run_input={'searchUrls': [{'url': 'https://www.agoda.com/search?city=9395&adults=2&rooms=1'}], 'maxItems': 10, 'currency': 'USD', 'language': 'en-US'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Agoda Hotels 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 Hotels 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-hotels-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 Hotels Scraper by Fetch Cat, or give it the identifier fetch_cat/agoda-hotels-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

• “Use Fetch Cat’s Agoda Hotels Scraper to collect up to 5 hotels for Bangkok city ID 9395 in USD. Show names, property links, guest scores and review counts, marking missing fields.”
• “Collect up to 5 hotels from my public Agoda search URL using the future dates and occupancy I provide. Include the effective search URL and collection time beside each visible price.”
• “Collect a small hotel sample with the Agoda search URL I provide. Make a comparison sheet with property IDs and links, and flag partial searches from the run summary without treating missing prices as confirmed unavailability.”

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.

FAQ

Can I search with a city name alone?

Use the correct Agoda cityId or copy a public search URL. destination only adds text to the city-ID search. It does not resolve arbitrary city names.

Why did I get fewer hotels or missing fields?

Availability, filters, access restrictions, and changes in Agoda's displayed cards can reduce coverage. Start with a small search you can inspect publicly, then check RUN_SUMMARY. Nullable fields are not fabricated.

Can I export reviews or room offers?

No. This Actor returns listing-level review scores/counts and displayed prices. For review text, see the related review scraper below.

Related Actors

• Agoda Reviews Scraper — Collect available public Agoda guest-review text, ratings and traveler metadata.
• Booking.com Hotels Scraper — Compare another accommodation marketplace.
• Booking Reviews Scraper — Collect available Booking.com guest reviews from the loaded public hotel or review page, without a complete-history guarantee.
• Google Hotels Scraper — Hotel search comparisons.
• TripAdvisor Reviews Scraper — Traveler review research.

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. ♥