Agoda API Scraper avatar

Agoda API Scraper

Pricing

from $1.00 / 1,000 dataset rows

Go to Apify Store
Agoda API Scraper

Agoda API Scraper

Scrapes Agoda accommodation search results, pricing and property details via Agoda's public GraphQL endpoints (requests-based, no browser).

Pricing

from $1.00 / 1,000 dataset rows

Rating

0.0

(0)

Developer

R.L.

R.L.

Maintained by Community

Actor stats

0

Bookmarked

7

Total users

5

Monthly active users

6 days ago

Last modified

Categories

Share

What does Agoda API Scraper do?

Agoda API Scraper extracts hotel and accommodation data — live pricing, review scores, photos, facilities and static property details — from Agoda without a browser. It talks directly to the same public GraphQL search endpoints www.agoda.com/search itself calls, so runs are fast and don't need to render pages. Give it a destination (or a list of property IDs) and your stay dates, and get back structured JSON, ready for the Apify API, scheduling and integrations.

See agoda_api_scraping.md for the underlying endpoint reverse-engineering notes.

Why use Agoda API Scraper?

  • Price monitoring — track nightly/total rates for specific properties or a whole city over time.
  • Market research — pull review scores, star ratings and facility data across a destination for competitor analysis.
  • Lead generation / travel apps — feed structured accommodation data into your own product without maintaining a browser-based scraper.

How to use Agoda API Scraper

  1. Enter a Destination (e.g. "Bangkok") — it's resolved to Agoda's internal city ID automatically. Or paste specific Property IDs to skip search entirely.
  2. Set Check-in / Check-out dates, Rooms/Adults/Children ages and a Currency.
  3. Optionally turn on Include static details for address/review-breakdown/useful-info per property.
  4. Run the Actor and download results from the Dataset tab (JSON, CSV, Excel, …).

Input

See the Input tab for the full schema. Key fields:

FieldDescription
searchFree-text destination, e.g. "Bangkok"
cityIdExact numeric Agoda city ID (skips destination resolution)
propertyIdsSpecific property IDs (bypasses search; static content only, no live pricing)
checkin / checkoutStay dates (YYYY-MM-DD)
adults / rooms / childrenAgesOccupancy
currencyDisplay currency
sortByRanking, Price or AllGuestsReviewScore
includeDetailsAdds a details object per property
maxItemsResult cap

Output

Each dataset item is one accommodation:

{
"propertyId": 14654101,
"name": "Solaria Nishitetsu Hotel Bangkok",
"url": "https://www.agoda.com/solaria-nishitetsu-hotel-bangkok/hotel/bangkok-th.html",
"propertyType": "Hotel",
"starRating": 4,
"addressCountry": "Thailand",
"addressCountryCode": "TH",
"addressCity": "Bangkok",
"addressArea": "Sukhumvit",
"latitude": 13.74, "longitude": 100.56,
"reviewScore": 9.2,
"reviewCount": 1523,
"facilityHighlights": ["Free Wi-Fi", "Swimming pool", "Airport transfer"],
"images": ["https://pix8.agoda.net/hotelImages/..."],
"priceCurrency": "USD",
"pricePerNight": 125.83,
"pricePerNightBeforeDiscount": 125.83,
"pricePerStay": 251.65,
"priceFreeCancellation": false,
"pricePayLaterEligible": false
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Main data fields

FieldMeaning
propertyIdAgoda's internal numeric property ID
name / urlDisplay name and canonical Agoda page
starRating, reviewScore, reviewCountRating summary
addressCountry, addressCity, addressArea, latitude, longitudeLocation
pricePerNight, pricePerStay, priceCurrency, priceFreeCancellation, ...The rate on Agoda's search card for those dates/occupancy, taxes and fees included
images, facilityHighlightsMedia and top amenities
checkInFrom, numberOfRooms, yearOpened, addressLine1, ... (optional)Added when "Include static details" is on

Every column holds a scalar or a list of strings — nothing nested — so a CSV or Excel export has one column per field rather than an expanded object. The column set is fixed per run: a field Agoda does not publish for a property comes back null rather than missing, and the static-detail columns appear only when that option is on, because a search alone can never fill them.

On the price. Agoda's search endpoint returns exactly one offer per property, and that is what these columns carry: the rate shown on the search card, taxes and fees included. It is not the minimum across every room type. Checked against the property pages on 2026-10-20, those list many more offers - 10 and 80 for two of the hotels sampled - and their cheapest came out both below and above the search-card rate, because the two surfaces price different things. Treat it as "what a searcher is quoted", not "the best rate available".

Where the search and the property-details endpoints disagree — they report different review counts for the same hotel, measured on 23 of 25 Bangkok properties — the row carries the search figures, which are the ones matching the dates and occupancy the run asked for.

Pricing / cost estimation

This Actor makes 1 request per page of ~25 results (plus 1 request per 20 properties if "Include static details" is on) — no browser rendering, so compute-unit usage per item is very low compared to browser-based scrapers. Check the Actor pricing tab for the current pricing model.

Languages

Agoda's API serves en-us, en-gb, pt-br, zh-cn and zh-tw. The other values in the language dropdown are kept so existing saved tasks keep loading, but Agoda returns no data for them, so a run that asks for one stops immediately and says so rather than failing. The property "useful info" labels (check-in time, room count, fees) are published in English only.

Tips

  • Leave includeDetails off for the fastest, cheapest runs when you only need pricing/ratings.
  • Use propertyIds directly if you already know which properties you want — it skips destination resolution and search pagination entirely.
  • Prices reflect Agoda's live availability at request time; re-run periodically for price-tracking use cases (see the Apify Scheduler).

Travel & booking toolkit

Part of the Travel & booking toolkit — search and pricing data across accommodation, transport, and travel-planning sites worldwide:

Did you find this useful?

Rate this actor on Apify! Your feedback helps other users find it and helps us keep improving it.

FAQ, disclaimers and support

This Actor scrapes publicly available data from Agoda for personal or business research purposes; use it in accordance with Agoda's Terms of Service and applicable law. Agoda may change its API at any time, which can affect this Actor's behavior — please report issues on the Issues tab. Need something custom? Reach out for tailored scraping solutions.