Pricing

Rating

Developer

Actor stats

Categories

Share

Ctrip / Trip.com Hotel Scraper

Scrape hotel listings from Trip.com (the English face of Ctrip): prices, ratings, reviews, location, star class, amenities, room types, and photos for any city and date range.

What you get per hotel

Input

{
"city":"Tokyo",
"cityId":228,
"checkIn":"2026-06-01",
"checkOut":"2026-06-03",
"guests":2,
"rooms":1,
"maxResults":50
}

cityId is strongly recommended for production. Trip.com's hotel list endpoint requires a numeric city ID — passing only a city name does not drive a search. The actor has a small built-in map of verified IDs (Tokyo 228, Singapore 73, Beijing 1, Shanghai 2, Madrid 357, Granada 717, New Delhi 495) and tries an in-browser autocomplete fallback for everything else, but the autocomplete resolver is not 100% reliable. To grab a cityId by hand, open https://www.trip.com/hotels/list?city=<id> for guesses and check the page title.

How it works

Trip.com renders its hotel list entirely client-side, behind a stealth-defence script (hotel-spider-defence) and a jigsaw CAPTCHA. Pure HTTP requests to the public fetchHotelList SOA endpoint are rejected without the dynamic testab token minted by the in-page JS.

The actor uses Camoufox (stealth Firefox) with Apify Residential proxy, performs a homepage warmup to settle session cookies, and then:

1. Attaches a page.on("response") listener before navigation, capturing every JSON response on /restapi/soa2/34951/fetchHotelList.
2. Loads /hotels/list?city=<id>&checkin=&checkout=&adult=&crn= and scrolls to trigger pagination / dynamic refresh XHRs.
3. Recursively walks each captured JSON for hotel records (matches dicts that look like a hotel: have hotelBasicInfo, or both hotelName and hotelId).
4. Falls back to anchor-based DOM extraction (a[href*="/hotels/detail/"] walked up to the smallest container with an image + meaningful text) if the API capture comes up short.

This is the same XHR-intercept pattern used by meesho-scraper and tatacliq-scraper in this repo.

Pricing (PPE)

Known limits

• Pagination is XHR-driven, not URL-driven. We rely on scrolling to fetch additional pages; 50-100 hotels per run is the comfortable ceiling. Larger maxResults may stall.
• CAPTCHA risk. Trip.com occasionally serves a jigsaw challenge to fresh proxy IPs. The actor retries up to 3 times with new browsers; persistent failures usually mean the proxy IP is currently flagged.
• Currency. All requests are pinned to USD via the curr URL param. Trip.com may still echo back rates that include local taxes/fees.
• City ID auto-resolve is best-effort. For ambiguous city names, supply cityId directly.