Trip.com Hotel Reviews Scraper
Pricing
from $0.80 / 1,000 results
Trip.com Hotel Reviews Scraper
Extract detailed hotel reviews, ratings & guest insights from Trip.com instantly. Perfect for market research, competitive intelligence & sentiment analysis. Gather structured review data, scores, comments & trends to power your hospitality analytics.
Pricing
from $0.80 / 1,000 results
Rating
5.0
(7)
Developer
Shahid Irfan
Maintained by CommunityActor stats
3
Bookmarked
39
Total users
11
Monthly active users
17 days ago
Last modified
Categories
Features
Share
What does Trip.com Hotel Reviews Scraper do?
Trip.com Hotel Reviews Scraper collects public guest reviews from a Trip.com hotel detail page and saves them as a structured dataset. Paste a hotel URL or provide a Trip.com hotel ID, choose how many reviews you need, and run the Actor. Each record combines the review text, guest rating, stay date, room type, travel type, reviewer details, and the hotel's published rating summary.
The dataset works for hotel reputation checks, guest feedback analysis, competitor comparisons, and reporting. You can export it as JSON, CSV, Excel, or XML, or send it to another tool through Apify integrations.
Why use Trip.com Hotel Reviews Scraper?
- One hotel per run, with full context - Every review carries the hotel name, address, star rating, overall score, review total, and the stay context from your URL.
- Original and translated feedback - Keep the guest's original language and the Trip.com translation when both are published.
- Useful review detail - Capture room type, travel purpose, stay date, helpful votes, reviewer country, photos, videos, and hotel replies.
- Batch delivery - Results are saved as each review page is processed, so a long run keeps its progress.
- Flexible output - Download the dataset or connect the run to Google Sheets, Airtable, webhooks, Make, Zapier, or the Apify API.
- Recovery built in - A blocked request is retried with a new session. If the block continues, the Actor uses the reviews already present on the hotel page.
What data can you extract from Trip.com hotel reviews?
| Data group | Fields |
|---|---|
| Hotel | Name, Trip.com URL, ID, city, address, latitude, longitude, star rating, main image |
| Rating summary | Overall score, score label, maximum score, published review total, recommendation text |
| Review | Review ID, text, translated text, guest rating, rating label, publication date, stay date, language |
| Stay context | Room type, travel type, check-in date, check-out date, adults, children, rooms, currency |
| Reviewer | Display name, avatar, review count, country |
| Media and feedback | Review images, videos, helpful votes, hotel responses |
| Provenance | Source code, source URL, review position in the dataset |
The Actor removes invisible characters that Trip.com inserts into some reviewer names. Missing values are omitted from the record instead of being saved as null.
How to scrape Trip.com hotel reviews
- Open Trip.com Hotel Reviews Scraper on Apify.
- Paste a public Trip.com hotel detail URL into
startUrl, or enter ahotelId. - Set
results_wantedto the number of reviews you need. - Add a proxy configuration if you need requests to go through a proxy.
- Run the Actor and open the dataset preview.
- Download the results or connect the run to your reporting workflow.
The URL can include checkIn, checkOut, adult, children, ages, crn, cityId, cityEnName, and curr. These values set the stay context and are reflected in the dataset where applicable.
If you provide hotelId together with a URL, the hotel ID wins and the stay dates and occupancy are kept. City context is read from the hotel page when the hotel changes. This lets you reuse one URL while switching hotels.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | No | Trip.com sample hotel URL | Public Trip.com hotel detail URL. Stay dates, occupancy, city, and currency are read from it when present. |
hotelId | Integer | No | - | Trip.com hotel ID. Overrides the hotel in startUrl and keeps the stay dates and occupancy. |
results_wanted | Integer | No | 20 | Maximum number of reviews to save. Range is 1 to 1000. |
proxyConfiguration | Object | No | {} | Optional Apify Proxy or custom proxy settings. |
At least one hotel reference must be usable: a URL with a hotelId, or the hotelId input. The default URL supplies a working hotel when the input is empty.
Output Data
| Field | Type | Description |
|---|---|---|
hotelId | Number | Trip.com hotel identifier. |
cityId | Number | Trip.com city identifier when present in the URL. |
cityEnName | String | English city name. |
hotelName | String | Hotel name shown on Trip.com. |
hotelUrl | String | Hotel detail URL used for the run. |
hotelImage | String | Main hotel image URL. |
hotelRating | Number | Overall hotel score. |
hotelRatingText | String | Score label such as Very good. |
hotelRatingMax | Number | Maximum hotel score. |
hotelStarRating | Number | Hotel star rating when published. |
totalReviewCount | Number | Review total shown for the hotel. |
recommendationText | String | Recommendation summary such as 77% Recommended. |
topFacilityName | String | Top rated facility or attribute. |
topFacilityScore | Number | Score for the top facility. |
positiveMentions | Array | Positive attributes highlighted for the hotel. |
hotelStreetAddress | String | Hotel street address. |
hotelLatitude | Number | Hotel latitude. |
hotelLongitude | Number | Hotel longitude. |
checkIn | String | Check-in date from the URL. |
checkOut | String | Check-out date from the URL. |
adult | Number | Adult count from the URL. |
children | Number | Child count from the URL. |
rooms | Number | Room count from the URL. |
currency | String | Currency code from the page or URL. |
reviewId | Number | Trip.com review identifier. |
reviewIndex | Number | Position of the review in the dataset. |
reviewDate | String | Review publication date and time. |
stayDate | String | Guest stay date when published. |
reviewLanguage | String | Original review language code. |
reviewOriginalText | String | Original guest review text. |
reviewTranslatedText | String | Trip.com translated text when available. |
reviewRating | Number | Score given by the guest. |
reviewRatingMax | Number | Maximum guest score. |
reviewLevel | String | Guest rating label such as Outstanding. |
roomTypeName | String | Room type attached to the review. |
travelTypeCode | Number | Trip.com travel type code. |
travelType | String | Travel purpose such as Traveling with friends. |
usefulCount | Number | Helpful votes shown for the review. |
canMarkUseful | Boolean | Whether Trip.com allows helpful votes on the review. |
reviewerName | String | Reviewer display name. |
reviewerAvatar | String | Reviewer avatar URL. |
reviewerReviewCount | Number | Reviews shown on the reviewer profile. |
reviewerCountry | String | Reviewer country when published. |
hotelResponses | Array | Hotel replies to the review when published. |
imageList | Array | Review image URLs. |
videoList | Array | Review video URLs. |
source | Number or String | Trip.com source code or label when published. |
sourceUrl | String | Hotel URL associated with the record. |
Usage Examples
Collect reviews from a hotel URL
This run collects 20 reviews and keeps the stay context from the URL.
{"startUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-11-10&checkOut=2026-11-11&adult=2&children=0&crn=1","results_wanted": 20}
Collect reviews by hotel ID
Use a hotel ID when you do not need a specific city or stay context. The Actor uses the default URL context for dates, occupancy, and currency.
{"hotelId": 78690884,"results_wanted": 50}
Collect a larger review history with a proxy
This run requests 300 reviews, reuses a URL for a different hotel ID, and sends traffic through Apify Proxy.
{"startUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=129054778&checkIn=2027-05-04&checkOut=2027-05-05&adult=2&children=0&crn=1","hotelId": 129054778,"results_wanted": 300,"proxyConfiguration": {"useApifyProxy": true}}
Sample Output
{"hotelId": 78690884,"cityId": 228,"cityEnName": "Tokyo","hotelName": "Koko Hotel Tsukiji Ginza","hotelUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-11-10&checkOut=2026-11-11&adult=2&children=0&crn=1","hotelImage": "https://ak-d.tripcdn.com/images/0200c120009cjtvnuD248_R_960_660_R5_D.jpg","hotelRating": 8.8,"hotelRatingText": "Very good","hotelRatingMax": 10,"hotelStarRating": 4,"totalReviewCount": 703,"recommendationText": "77% Recommended","topFacilityName": "Remarkably Clean","topFacilityScore": 9,"positiveMentions": ["Convenient location", "Delicious breakfast"],"hotelStreetAddress": "6 Chome-8-8 Tsukiji, Chuo Ward, Tokyo, 104-0045, Japan","hotelLatitude": 35.664786,"hotelLongitude": 139.77323,"checkIn": "2026-11-10","checkOut": "2026-11-11","adult": 2,"children": 0,"rooms": 1,"currency": "USD","reviewId": 2145839233,"reviewIndex": 1,"reviewDate": "2026-10-19 20:58:45","stayDate": "2026-10-01 00:00:00","reviewLanguage": "en","reviewOriginalText": "In this hotel we were the second time. Love it so much. The location is so comfortable, the neighborhood is so calm and cozy. Rooms are beautiful. Thank you!","reviewRating": 10,"reviewRatingMax": 10,"reviewLevel": "Outstanding","roomTypeName": "Moderate Twin Room","travelTypeCode": 40,"travelType": "Traveling with friends","usefulCount": 0,"canMarkUseful": true,"reviewerName": "Guest User","reviewerAvatar": "https://ak-d.tripcdn.com/images/1i51v12000h1rjb5x3A86_C_130_130_Q70.jpg","reviewerReviewCount": 5,"reviewerCountry": "Russia","imageList": ["https://ak-d.tripcdn.com/images/0230a424x9b0un3bpAD8E_R_150_150_R5_Q70_D.jpg","https://ak-d.tripcdn.com/images/0233g424x9b0vc36vCD45_R_150_150_R5_Q70_D.jpg"],"source": 1,"sourceUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-11-10&checkOut=2026-11-11&adult=2&children=0&crn=1"}
Tips for best results
- Use the public hotel page URL - Copy the URL from your browser so the hotel, dates, occupancy, and currency match what you see.
- Start with 20 reviews - Confirm the hotel and the fields before you request a larger history.
- Expect a review cap - Trip.com shows more reviews on the hotel page than its review pages return. The Actor saves what the public pages expose.
- Keep dates realistic - Use a valid check-in and check-out pair. Dates do not need to be in the past.
- Use a proxy when needed - A proxy configuration sends requests through the proxy you choose. Add one when your workflow requires it.
- Check the dataset preview - Confirm the hotel name and address before you send the data downstream.
Integrations and export formats
- Google Sheets - Review guest feedback and rating changes in a spreadsheet.
- Airtable - Group reviews by hotel, room type, travel type, or date.
- Webhooks - Start a downstream workflow when a run finishes.
- Make or Zapier - Send new review records to dashboards and alerts.
- Apify API - Start runs and read dataset records from your own systems.
- JSON, CSV, Excel, and XML - Download the dataset in the format your tools accept.
Frequently Asked Questions
How many reviews can one run return?
A run returns up to the results_wanted value. It stops earlier when Trip.com stops returning review pages. Trip.com can show more reviews on the hotel page than its review pages return, so totalReviewCount can be higher than the number of records you receive.
Do I need a full hotel URL?
No. A hotelId is enough. The Actor uses the default hotel URL for city, dates, occupancy, and currency. A full URL gives you control over those values.
Why do I get fewer reviews than the hotel's review total?
Trip.com limits how far its public review pages go. The Actor stops at that limit instead of repeating reviews or making up records.
Does the dataset include translated review text?
Yes, when Trip.com publishes a translation. English reviews usually have no translated copy, so reviewTranslatedText is absent for those records.
Are review photos and videos included?
Yes. imageList and videoList contain the public media URLs that Trip.com returns for each review.
Can I schedule the Actor?
Yes. Create an Apify schedule to run it hourly, daily, weekly, or at another interval. Use a proxy configuration for recurring runs.
Why are some fields missing from a record?
Trip.com does not publish every field for every review. Reviewer country, room type, stay date, translated text, media, and hotel responses depend on what the guest and the hotel provided.
Is it legal to collect Trip.com review data?
The Actor collects publicly available review data. You are responsible for complying with applicable laws, privacy rules, and Trip.com's terms. Handle reviewer names and media responsibly.
Related Actors
- Trip.com Hotels Scraper - Collect hotel listings, prices, and property details from Trip.com.
- Booking.com Reviews Scraper - Collect guest reviews from Booking.com hotel pages.
- Expedia Reviews Scraper - Collect guest reviews from Expedia hotel pages.
Support
For issues, missing fields, or feature requests, use the Issues tab on the Actor page. Include the input URL, the run ID, and a short description of the problem. Public hotel pages change, and the affected URL helps confirm the current page structure.
Legal Notice
This Actor is intended for legitimate collection of publicly available Trip.com hotel review data. Users are responsible for complying with applicable laws, privacy rules, and Trip.com's terms of service. Use reviewer information and media links responsibly.