Trip.com Hotels, Rooms & Reviews Scraper
Pricing
from $1.00 / 1,000 hotel results
Pull structured hotel listings from trip.com with prices, room types, amenities, policies, nearby places, and full guest reviews with ratings breakdown and an AI review summary. Search by destination or paste trip.com URLs directly.
Search: type a destination name, pick dates and filters below. URL: paste trip.com hotel links copied from your browser - every link shape works (search links, hotel detail links, and the /hotels/-hotels-list-/ links copied from a search engine).
One destination per line - just the city name, e.g. "Tokyo" or "New York". Trip.com city ids also work: a bare id ("228") or "228|Tokyo". Names are matched against a built-in index of trip.com's own destinations; for smaller towns not in the index, switch to URL mode and paste a trip.com hotel link for that place.
Check-in date, format YYYY-MM-DD. Leave empty to default to 14 days from today.
Check-out date, format YYYY-MM-DD. Leave empty to default to one night after check-in.
Number of adult guests per room.
Number of child guests per room.
Currency prices are shown and pushed in.
Keep only hotels rated at or above this many stars. 0 = no filter. Applied client-side after fetching each page.
Keep only hotels scoring at or above this out of 10 from guest reviews. 0 = no filter. Applied client-side after fetching each page.
One or more trip.com hotel URLs, any shape: a hotel list search URL (/hotels/list?city=...), a hotel detail URL (/hotels/detail/?hotelId=...), or the SEO links trip.com and search engines use (/hotels/tokyo-hotels-list-228/, /hotels/tokyo-hotel-detail-123456/hotel-name/, landmark and brand pages). Multi-URL supported, pagination walks forward, missing dates/guests are filled from the fields above. Non-hotel links (homepage, city directories) are skipped with a warning. Dates, guests and currency in a link win over the run-level fields above. Trip.com ignores page, sort and star in a plain list link (each fetch returns a fresh slice of the destination), so use Minimum star rating and Minimum guest review score, which are also applied to hotels from pasted links. A hotelUrl key is accepted as a single-link alias. Left untouched, this field scrapes the example links below, one per link shape; clear it and paste your own to scrape only those.
[ "https://www.trip.com/hotels/list?city=228&cityName=Tokyo&checkIn=2026-11-15&checkOut=2026-11-16&adult=2&children=0&crn=1&curr=USD", "https://us.trip.com/hotels/list?city=359", "https://www.trip.com/hotels/tokyo-hotels-list-228/", "https://au.trip.com/hotels/singapore-hotels-list-73/", "https://www.trip.com/hotels/tokyo-asakusa/hotels-c228m15019878/", "https://www.trip.com/hotels/shanghai-ibis/hotels-c2b1137/", "https://www.trip.com/hotels/tokyo-jr-tokyo-station/hotels-c228r8254862/", "https://www.trip.com/hotels/detail/?hotelId=1677831", "https://www.trip.com/hotels/detail/?hotelId=686797&checkIn=2026-11-15&checkOut=2026-11-16&adult=2&crn=1&curr=USD", "https://www.trip.com/hotels/tokyo-hotel-detail-993510/imperial-hotel-tokyo/", "https://www.trip.com/hotels/tokyo-hotel-detail-1489108/", "https://www.trip.com/hotels/dali-hotel-detail-21785314/liu-minyue-garden-designer-vacation-accommodation/review.html", "https://www.trip.com/hotels/ho-chi-minh-city-hotel-detail-2073112/park-hyatt-saigon/photo.html"]When ON, also fetch each hotel's detail page for amenities, policies, nearby places, full description, and guest reviews with an AI summary. When OFF, only the listing-page fields are returned (name, price, rating, image, address). Default ON since most of the field set lives on the detail page.
Cap the guest reviews attached to each hotel (the most recent ones trip.com returns on the page). Default 20, 0 to skip reviews. Reviews bill on the existing detail-enrichment event in blocks: one extra unit per 10 delivered reviews (see the Pricing tab).
Order of the reviews attached to each hotel, applied to the reviews the page returns, before the cap. mostRelevant keeps the site order.
Keep only reviews written after this date (YYYY-MM-DD). Empty keeps all.
How many list pages to walk per destination (or per pasted list URL). Does not cap the total, only how many pages are fetched, defers to Max listings. Leave empty to walk every result page.
Stop after this many hotels across all destinations. This is the run's cap, defaulting to 20. Set to 0 to remove the cap entirely (an empty Max pages will then walk every result page).
Apify proxy used to fetch pages. The default below works out of the box.
ID of an interrupted run whose hotels should not be re-scraped: this run continues the previous one's dedup set. Leave empty to start fresh. For recurring diff runs (new/updated only on a schedule) you don't need this - turn on Incremental mode below instead.
ON: the actor remembers the hotels it delivered for this exact search scope (keyed automatically, or use State key below) and on each scheduled run classifies every hotel as NEW, UPDATED, UNCHANGED or EXPIRED - pushing only new and changed rows plus EXPIRED tombstones, and stamping each row with changeType, changedFields, firstSeenAt and lastSeenAt. UPDATED is decided by comparing the whole record: price, original price, taxes total, discount, rating and review counts, amenities, policies, rooms (room prices and remaining-room counts) and the reviews you requested. It does NOT compare scrapedAt, the image URLs, or any field you list under Ignore fields; list order is ignored. Use Change scope to compare only prices and room availability. OFF (default): every run returns the full result set like before.
Name for the incremental baseline when Incremental mode is ON. Leave empty to key the baseline on a hash of the search scope automatically (recommended). Use the same key across runs to compare like with like; a different key starts a new baseline.
With Incremental mode ON, also push hotels that did not change (stamped changeType=UNCHANGED). Default OFF - unchanged hotels are only remembered, not pushed.
With Incremental mode ON, push a tombstone row (changeType=EXPIRED, last known field values) for hotels from the previous run that this run's search no longer returns - only when the search ran to completion. Default ON.
With Incremental mode ON. 'all' (default): any change in the compared fields makes a row UPDATED. 'priceAndStock': only price changes (current, original, total with taxes, discount, currency) and per-room price, room name and remaining-room count make a row UPDATED; descriptions, amenities, badges, reviews and images never do.
With Incremental mode ON, UPDATED rows carry only ids, name, link, current prices, priceChanges {field: {old, new}} and roomChanges [{roomId, change: ADDED|REMOVED|CHANGED, changes}] instead of the full record (no detail or review payload, so no detail or review charge rides on a compact row). NEW rows stay full. Default OFF.
With Incremental mode and Push EXPIRED tombstones ON: a hotel is tombstoned only after it was missing from this many CONSECUTIVE complete scans (default 1 = the first complete scan that misses it). EXPIRED means the search no longer returned the hotel; it does not prove the hotel is unavailable, since a result-pool resample and a delisting look the same without a detail probe.
With Incremental mode ON, dataset fields listed here never count as a change (they are excluded from changeType/changedFields while staying in the output). Top-level names (e.g. badges) or dotted paths into a list (e.g. rooms.roomPromotions drops that key from every room, the rest of the room is still compared). Built-in defaults already cover the scrape timestamp and the image URLs (images, image), and lists whose order the site reshuffles are compared order-independently.
Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify -> Settings -> Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export, ignored by other connectors.