Agoda and Trip.com Reviews Scraper: Hotel Reviews, Replies
Pricing
from $2.70 / 1,000 agoda reviews
Agoda and Trip.com Reviews Scraper: Hotel Reviews, Replies
Agoda and Trip.com hotel reviews for hotel links or IDs: score, original text, English translation, traveler type, hotel reply; $5.40 per 1,000 Agoda reviews. Trip.com reviews $3.60 per 1,000. Both sites in one run, only-new mode, free hotel summary and error rows.
Pricing
from $2.70 / 1,000 agoda reviews
Rating
0.0
(0)
Developer
Arcadium Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 hours ago
Last modified
Categories
Share
Give it Agoda or Trip.com hotel links (or hotel IDs) and it returns one JSON row per guest review: score, the text in the language it was written in plus an English translation, traveler type, stay details and the hotel's reply. $5.40 per 1,000 Agoda reviews and $3.60 per 1,000 Trip.com reviews on the free plan, less on paid plans; you pay only for rows you get.
Why this actor
- Drop-in input. Input written for
knagymate/fast-agoda-reviews-scraperorknagymate/trip-com-reviews-scraper(hotelUrl,maxReviews,sortBy,cutoffDate,language),lergassy/agoda-reviews-scraper(startUrls,reviewsSort,reviewLanguages) orfactden/ctrip-trip-reviews-scraper(fromDate) works as it is. - Two Asian review sites in one run and one row shape, filtered on the
platformfield. - Original text and an English translation side by side for multilingual feedback.
- Only new reviews under a
stateKey; edited reviews come back once, markededited. - Know what you got. Free
coveragerows (stated vs delivered), an optional free hotel summary and a freeerrorrow with acodeper failed input.
Built by Arcadium Data: public data, dated and agent-ready, never personal data.
Use with AI agents
Returns Agoda and Trip.com hotel reviews (score, original text, English translation, hotel reply, traveler type, reviewer country) for hotel links or IDs. Agents can call it through the Apify MCP server (https://mcp.apify.com, open source as apify/actors-mcp-server) as arcadium/agoda-tripcom-reviews: the input schema is read from the actor, the result is a dataset of JSON rows.
Input example (minimal):
{"startUrls": [{ "url": "https://www.agoda.com/ibis-bangkok-riverside/hotel/bangkok-th.html" },{ "url": "https://www.trip.com/hotels/detail/?hotelId=425587" }],"maxReviewsPerHotel": 20}
What comes back: one review row per review (charged; platform is agoda or tripcom), free coverage rows (stated total vs delivered), an optional free hotel-summary row per hotel (includeHotelSummary) and a free error row for an input that could not be read. Filter on the rowType field. An input that fails is reported, not hidden (includeErrorRows, on by default): the error row carries rowType: "error", a code (invalid_input, not_found, blocked, unavailable), a message and the input it is about. Retry on blocked and unavailable later; do not retry the other codes with the same input.
Cost of the call above: 20 Agoda reviews at $5.40 per 1,000 plus 20 Trip.com reviews at $3.60 per 1,000 plus the $0.001 start fee is about $0.19 on the free plan; paid plans pay less. Free rows are never charged.
What you get
| Field | What it holds |
|---|---|
platform | agoda or tripcom. |
reviewId | The site's own review ID, prefixed Agoda___ or Tripcom___. Stable between runs, so weekly exports can be deduplicated. |
date | Review date, ISO format. |
title | Review headline (Agoda; Trip.com reviews have none). |
text | The review in the language it was written in. |
pros, cons | Liked and disliked text where the site asks separately (some Agoda reviews). |
ratingOverall | Score on a 0 to 5 scale (the site's 1 to 10 score divided by 2). The original is in extras.score10. |
language | Two-letter language of the original text (the regional variant, such as zh-tw, is in extras.languageVariant). |
vendorResponse | The hotel's reply, with the greeting name removed. |
helpfulVotes | Helpful votes. |
country | Reviewer country as a two-letter code. On by default; switch off with includeReviewerCountry: false. |
extras | textTranslated (English translation when the site provides one), travelerType, roomType, stay dates or stay month, nights, photoCount, ownerResponseDate; Trip.com adds subScores10 (location, facilities, service, cleanliness), recommends, followUpText (the guest's later addition) and reviewSource (Trip.com or Ctrip). |
entityId, productName, productUrl, product | Which hotel the review belongs to. |
Output example:
{"platform": "agoda","reviewId": "Agoda___1190000001","date": "2026-10-08","title": "また泊まりたいホテル","text": "スタッフの対応がとても良く、部屋も清潔でした。川沿いの景色も最高です。","ratingOverall": 5,"language": "ja","country": "TH","vendorResponse": "Dear Guest, thank you for staying with us...","extras": {"score10": 10,"textTranslated": "The staff were very helpful and the room was clean. The river view is great too.","travelerType": "Couple","roomType": "Superior Room","nights": 3,"checkIn": "2026-10-05"},"entityId": "230691","productName": "Ibis Bangkok Riverside"}
Input
{"startUrls": [{ "url": "https://www.agoda.com/ibis-bangkok-riverside/hotel/bangkok-th.html" },{ "url": "https://www.trip.com/hotels/shanghai-hotel-detail-425587/hilton-shanghai-hongqiao/" }],"agodaHotelIds": [10713],"maxReviewsPerHotel": 500,"sort": "NEWEST","languages": ["en", "ja"],"dateFrom": "3 months"}
| Field | What it does |
|---|---|
startUrls | Agoda hotel or review pages and Trip.com hotel pages, mixed. Any Agoda locale and any Trip.com country site work. |
agodaHotelIds, tripcomHotelIds | Numeric hotel IDs instead of links. |
maxReviewsPerHotel | Cap per hotel. |
sort | Newest first (default), most relevant (Agoda: most helpful), highest or lowest rating. |
languages | Only reviews written in these languages. zh matches every Chinese variant. |
dateFrom | Only reviews from this date on. With newest first, reading stops once a whole page is older (Trip.com keeps a 120-day margin because it orders by stay month). |
onlyNewReviews, stateKey | Only reviews not delivered by an earlier run with the same key. |
includeHotelSummary | One free row per hotel: Agoda's own score, rating count and category scores against the city average, the combined score of every provider Agoda shows; Trip.com's score, category scores, positive and negative counts, address and the advertised "from" price. |
includeReviewerCountry | Adds the reviewer's country as an ISO code. On by default. |
Coverage and edited reviews
A free coverage row per hotel says how many reviews the site reports against how many you received, and why reading stopped (your cap, the end, or the date). With onlyNewReviews, a review that was edited after it was delivered comes back once more with extras.changeType set to edited; that row is charged like a new review.
Use it from an AI assistant
Paste this into your assistant to run the actor for you:
Use the Apify actor "arcadium/agoda-tripcom-reviews" to collect hotel reviews.Input: {"startUrls":[{"url":"<Agoda or Trip.com hotel link>"}],"maxReviewsPerHotel":200,"sort":"NEWEST"}Each review row has date, ratingOverall, text, extras.textTranslated (English) and vendorResponse.Run it, then summarize the main praise and complaints per site and say how many reviews got a hotel reply.
Use it from code
Python:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("arcadium/agoda-tripcom-reviews").call(run_input={"startUrls": [{"url": "https://www.agoda.com/ibis-bangkok-riverside/hotel/bangkok-th.html"}],"maxReviewsPerHotel": 200,})for item in client.dataset(run["defaultDatasetId"]).iterate_items():if item.get("rowType") == "review":print(item["date"], item["ratingOverall"], (item["extras"].get("textTranslated") or item["text"] or "")[:80])
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('arcadium/agoda-tripcom-reviews').call({startUrls: [{ url: 'https://www.trip.com/hotels/detail/?hotelId=425587' }],maxReviewsPerHotel: 200,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.filter((i) => i.rowType === 'review').length, 'reviews');
Pricing
You pay per review delivered, at the price of your Apify plan. Agoda and Trip.com reviews are priced separately. Hotel summary rows, coverage rows, error rows and repeats in only-new mode are free.
| Apify plan | Per 1,000 Agoda reviews | Per 1,000 Trip.com reviews |
|---|---|---|
| Free | $5.40 | $3.60 |
| Starter (Bronze) | $4.50 | $3.30 |
| Scale (Silver) | $3.60 | $3.00 |
| Business (Gold) | $2.70 | $2.70 |
| Platinum | $2.70 | $2.70 |
| Diamond | $2.70 | $2.70 |
Plus a one-off $0.001 per GB of memory when a run starts.
Set a maximum cost per run in the Apify run options and the actor stops before it goes over.
Related actors and data
- Hotel Reviews Scraper: Tripadvisor, Booking.com, Google
- Booking.com Reviews Scraper: Pros, Cons, Reviewer Country
- Tripadvisor Reviews Scraper: Ratings, Replies, Translations
- Review Monitor: Negative Review Alerts and Rating Drift
- Hotel demand peaks report: the next 90 nights of hotel rates by city, with spike nights flagged.
- Arcadium Data MCP Server: AI agents can ask the same questions as tools (
search_reviews,hotel_prices,city_rate_curve,review_snapshot).
Use cases
- Reputation monitoring in Asia: pull the newest Agoda and Trip.com reviews every week with
onlyNewReviewsnext to Booking.com, Tripadvisor and Google. - Reply tracking:
vendorResponseandextras.ownerResponseDateshow which reviews the hotel answered and how fast. - Competitor benchmarking: Agoda's category scores against the city average and Trip.com's sub-scores, from the summary row.
- Multilingual analysis: the original text for native-language models, the English translation for everything else.
Limitations
- Public reviews only. Nothing behind a login.
- Agoda: only Agoda's own reviews are returned. Agoda also shows Booking.com reviews of the same hotel; use our Booking.com reviews actor for those.
- Agoda's "most recent" order is newest first except for a few imported reviews, and its pages overlap by a few reviews between requests, so a full read usually returns about 98% of the stated total (duplicates are dropped, never charged).
- Trip.com orders "most recent" by stay month, so a late review of an old stay can appear further down; the date filter keeps a 120-day margin for that.
- Trip.com folds repeat and very short reviews; the coverage row states the number that can be paged, not the larger headline count.
- English translations are what the sites provide: Agoda translates most non-English reviews, Trip.com only some.
- Searching by hotel name is not supported. Paste the hotel link or the hotel ID.
Privacy
Reviewer names, nicknames, user IDs, profile photos, member levels, guest photos, emails and phone numbers are never collected. Names in greetings and sign-offs of hotel replies (for example 'Dear John' or 'Regards, Anna') are replaced with [name]; other names in the text are not detected. The reviewer's country is on by default and is a two-letter country code, nothing else about the person; switch it off with includeReviewerCountry: false.
FAQ
How fresh is the data? It is read when you run the actor, so it matches what the site shows at that moment.
Can I get only new reviews since my last run?
Yes. Turn on onlyNewReviews and keep the same stateKey. The state is stored per hotel. Use another stateKey to start a separate series.
Where do I find a hotel ID?
Agoda: the number after hotel_id= or selectedproperty= in a search link. Trip.com: the hotelId in a hotel link, or the number after hotel-detail-.
A hotel returned no reviews. Why? Check that the link opens a hotel page in your browser. Unknown hotels return an error row, which is not charged.
Something looks wrong in the output. Who do I tell? Open an issue on the actor page with the run link. We read them all.