Trip.com Hotel Reviews Scraper

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 structured dataset records. Give it a Trip.com hotel URL, or provide a hotel ID for the default hotel context, then choose how many reviews you want.

Records include hotel and stay context, ratings, original and translated review text, room type, travel type, reviewer details, helpful counts, and published media links. Use the dataset for reputation monitoring, hospitality research, guest experience analysis, competitor benchmarking, and reporting.

Why use Trip.com Hotel Reviews Scraper?

• Collect review data at scale - Gather up to the requested number of reviews for one hotel and stay context.
• Keep hotel context with every review - Match guest feedback with the hotel name, Trip.com URL, overall rating, review count, location, and selected stay details.
• Analyze original and translated feedback - Preserve the original review language and Trip.com translated text when it is published.
• Compare guest segments - Group feedback by room type, travel type, stay date, review score, and reviewer information.
• Export for your workflow - Download the dataset as JSON, CSV, Excel, XML, or another Apify-supported format, or connect the run to webhooks and external automation.

What data can you extract from Trip.com hotel pages?

Field	Description
hotelId	Trip.com hotel identifier.
cityId	Trip.com city identifier.
cityEnName	English city name used for the hotel context.
hotelName	Property name shown on Trip.com.
hotelUrl	Hotel detail URL associated with the record.
hotelImage	Property image URL when available.
hotelRating	Overall hotel score.
hotelRatingText	Text label for the overall hotel score.
hotelRatingMax	Maximum value of the overall hotel score.
totalReviewCount	Total published review count shown for the hotel.
recommendationText	Property recommendation summary when available.
topFacilityName	Top facility or attribute highlighted for the hotel.
topFacilityScore	Score associated with the highlighted facility.
positiveMentions	Positive attributes highlighted for the property.
hotelStreetAddress	Street address when available.
hotelLocality	Locality or city from the hotel address.
hotelRegion	State, province, or region from the hotel address.
hotelCountry	Country from the hotel address.
hotelLatitude	Hotel latitude when available.
hotelLongitude	Hotel longitude when available.
checkIn	Check-in date used for the selected stay context.
checkOut	Check-out date used for the selected stay context.
adult	Number of adults in the selected stay context.
children	Number of children in the selected stay context.
rooms	Number of rooms in the selected stay context.
currency	Currency used for the selected context.
reviewId	Trip.com review identifier.
reviewIndex	Position of the review in the returned dataset.
reviewDate	Review publication date and time.
stayDate	Guest stay date when published.
reviewLanguage	Original language of the review.
reviewOriginalText	Original guest review text.
reviewTranslatedText	Translated review text when available.
reviewRating	Score given by the guest.
reviewRatingMax	Maximum value of the guest review score.
reviewLevel	Review label such as Great.
roomTypeName	Room type associated with the review.
travelTypeCode	Trip.com travel type code when available.
travelType	Travel purpose label such as business traveler or couple.
usefulCount	Number of helpful votes shown for the review.
canMarkUseful	Whether the review can be marked useful.
reviewerName	Reviewer display name.
reviewerAvatar	Reviewer profile image URL when available.
reviewerReviewCount	Review count shown on the reviewer profile.
imageList	Review image URLs when available.
videoList	Review video URLs when available.
source	Review source label when published by Trip.com.
sourceUrl	Trip.com URL used for the run.

Unavailable fields are omitted from each dataset item.

How to scrape Trip.com hotel reviews

1. Open Trip.com Hotel Reviews Scraper on Apify.
2. Paste a public Trip.com hotel detail URL into startUrl, including the desired stay dates and occupancy when relevant.
3. Set results_wanted to the maximum number of reviews to collect.
4. Run the Actor and review the dataset preview.
5. Download the results or connect the run to your reporting or automation workflow.

You may provide hotelId without a full URL, but a complete Trip.com hotel detail URL gives the most accurate hotel, location, date, and occupancy context.

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	No	Trip.com sample hotel URL	Trip.com hotel detail URL. The URL can include hotelId, cityId, checkIn, checkOut, adult, children, and crn values.
hotelId	Integer	No	78690884	Trip.com hotel identifier. Used to build a hotel URL when startUrl is not provided.
results_wanted	Integer	No	20	Maximum number of reviews to save.
locale	String	No	en-US	Locale used for the hotel review request context.
region	String	No	US	Region used for the hotel review request context.
proxyConfiguration	Object	No	{"useApifyProxy": false}	Optional Apify Proxy configuration for the run.

The Actor reads stay and occupancy values from the Trip.com URL. Common URL parameters include checkIn, checkOut, adult, children, ages, crn, cityId, cityEnName, and curr.

Usage Examples

Basic extraction from a hotel URL

Use a complete Trip.com hotel detail URL when you want the returned records to match a particular stay context.

{
    "startUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-04-06&checkOut=2026-04-07&adult=2&children=0&crn=1",
    "results_wanted": 10
}

Run with a hotel ID

Use a hotel ID for a quick run when the default hotel context is acceptable.

{
    "hotelId": 78690884,
    "results_wanted": 20
}

Use a proxy for repeated collection

Set an Apify Proxy group when you are running repeated hotel checks or larger review collections.

{
    "startUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-04-06&checkOut=2026-04-07&adult=2&children=0&crn=1",
    "results_wanted": 50,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": ["RESIDENTIAL"]
    }
}

Sample Output

Example dataset item; optional fields may be absent.

{
    "hotelId": 78690884,
    "cityId": 228,
    "cityEnName": "Tokyo",
    "hotelName": "Koko Hotel Tsukiji Ginza",
    "hotelUrl": "https://www.trip.com/hotels/tokyo-hotel-detail-78690884/koko-hotel-tsukiji-ginza/",
    "hotelRating": 8.7,
    "hotelRatingText": "Very good",
    "hotelRatingMax": 10,
    "totalReviewCount": 641,
    "recommendationText": "76% Recommended",
    "positiveMentions": ["Convenient location", "Close to metro"],
    "hotelLocality": "Tokyo",
    "hotelCountry": "Japan",
    "checkIn": "2026-04-06",
    "checkOut": "2026-04-07",
    "adult": 2,
    "children": 0,
    "rooms": 1,
    "currency": "PKR",
    "reviewId": 1881103079,
    "reviewIndex": 1,
    "reviewDate": "2026-03-19 18:56:29",
    "stayDate": "2026-03-01 00:00:00",
    "reviewLanguage": "zh",
    "reviewOriginalText": "房間很小很小的那種，還好設施齊全，周圍交通方便快捷。早餐很豐富，選擇很多，甜品和南瓜泥很好吃，值得信賴。",
    "reviewTranslatedText": "The room was tiny, but thankfully it had all the necessary facilities. The surrounding area offers convenient and fast transportation. Breakfast was excellent with a wide variety of choices; the desserts and pumpkin puree were especially delicious.",
    "reviewRating": 9,
    "reviewRatingMax": 10,
    "reviewLevel": "Great",
    "roomTypeName": "Standard Double Room",
    "travelType": "Business traveler",
    "usefulCount": 2,
    "reviewerName": "Ivan",
    "reviewerReviewCount": 84,
    "imageList": ["https://ak-d.tripcdn.com/images/0235c224x98ob9xzfA68F_R_150_150_R5_Q70_D.jpg"],
    "sourceUrl": "https://us.trip.com/hotels/detail/?cityEnName=Tokyo&cityId=228&hotelId=78690884&checkIn=2026-04-06&checkOut=2026-04-07&adult=2&children=0&crn=1"
}

Tips for best results

• Use a complete hotel URL - Copy the hotel detail URL from Trip.com so the hotel, city, dates, occupancy, and currency context are clear.
• Start with a small limit - Test with 10 or 20 reviews before increasing results_wanted for a scheduled collection.
• Choose realistic dates - Keep checkIn, checkOut, and occupancy values valid for the hotel page you are using.
• Expect optional fields - Images, videos, translated text, room types, and reviewer details depend on what Trip.com publishes for each record.
• Schedule monitoring runs - Repeated runs can help you compare new review dates, ratings, recurring complaints, and positive mentions over time.
• Check the dataset preview - Confirm the hotel identity and stay context before using the records in reports or downstream systems.

Integrations and export formats

• Google Sheets - Review guest feedback and rating changes in a spreadsheet.
• Airtable - Organize reviews by property, room type, travel type, or review date.
• Webhooks - Trigger a workflow after an Actor run finishes.
• Make or Zapier - Send new datasets to alerts, dashboards, or internal tools.
• Apify API - Start runs and retrieve dataset records programmatically.
• JSON, CSV, Excel, and XML - Export data for analysis, reporting, or system integration.

Frequently Asked Questions

What kind of Trip.com pages does this Actor support?

It supports public Trip.com hotel detail pages and collects reviews for one selected property per run.

How many reviews can one run return?

The Actor returns up to the results_wanted value, subject to the number of reviews Trip.com makes available for the selected hotel and stay context.

Does it collect translated Trip.com reviews?

Yes. The dataset includes reviewOriginalText and reviewTranslatedText when both versions are published.

Can I run the Actor without a full hotel URL?

Yes. Provide hotelId for a quick run. A complete startUrl is recommended when you need a specific city, stay date, occupancy, or currency context.

Why are some fields missing from a review?

Trip.com does not publish every field for every hotel or guest review. Media, translated text, room type, reviewer counts, and helpful votes may be unavailable for some records.

Can I schedule Trip.com review collection?

Yes. Create an Apify schedule to run the Actor hourly, daily, weekly, or at another interval supported by your workflow.

Is it legal to collect Trip.com review data?

Public data collection may be subject to applicable laws, privacy requirements, and Trip.com’s terms. You are responsible for confirming that your use of the dataset is permitted and for handling reviewer information responsibly.

Related Actors

• Trip.com Hotels Scraper - Collect hotel listings, prices, availability, and related property data from Trip.com.
• Booking 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 and include the input URL, run ID, and a short description of the problem. Public hotel pages can change, so reporting the affected page helps keep the Actor aligned with current Trip.com output.

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.