Trip.com Scraper

Pricing

Rating

Developer

Actor stats

Categories

Share

Scrape Trip.com hotels, train routes, and attractions worldwide via the realtyapi.io Trip.com API.

What it does

• 🏨 Hotel Details — auto-detects each input as hotelId (digits) or trip.com URL; returns the full record (rooms, amenities, policies, location, reviews summary, full image list, nearby POIs).
• 🔎 Hotel Search — 3 modes: by location name, by lat,lng[,radius_km] coordinates, or by Trip.com listing URL. All filters (dates / guests / price / star / sort) apply.
• 🔤 Destination Autocomplete — resolve free-text city/destination → cityId + Trip.com city URL.
• 🚄 Trains — route search (Origin → Destination [date]) returns one row per departure; per-train detail row by trainNo.
• 🎢 Attractions — things-to-do search by city keyword + per-POI detail by poiId.

Output

• One flat dataset row per result — hotel / train / POI / autocomplete row.
• Columns: Mode, Input Given, ID, Name, City, Country, Address, Price, Currency, StarRating, Rating, ReviewCount, Latitude, Longitude, Extra, Cover Photo, Listing URL.
• Full upstream JSON kept in the Raw column for power users (rooms, amenities, segments, photos, etc.).

Inputs

• Each section is independent — fill only the ones you need.
• Multiple inputs per section: one per line.
• The 🗓 Hotel Filters block (check-in/out, adults, children, rooms, sort, price, star, resultCount, page) applies to every hotel search and detail call.

Pricing

• Pay per result: $3 per 1,000 dataset items — same rate on every Apify plan tier.
• Apify start fee: $0.00005 per run.

Notes

• Trip.com SSR caps each hotel search page at ~12 hotels; this actor stitches multiple SSR + SEO sources per city to deliver up to 100 unique hotels per query.
• Date format is YYYY-MM-DD; leave check-in / check-out blank to default to ~30 days out.
• Train routes work best on European (Eurostar, France, Spain) and Chinese networks — those are the corridors with full SEO route pages on Trip.com.
• Attraction detail by arbitrary poiId works for POIs in Trip.com's SEO feeds (~350 well-known attractions across the top ~25 cities); deep-tail POIs may return a 404.

Errors

• Failures land in the dataset as rows with Mode = "ERROR" and the upstream error message in Name — nothing is silently dropped.