[Home](/)[Blog](/blog)Trip.com API Documentation: What Exists and How to Get Access # Trip.com API Documentation: What Exists and How to Get Access ![Denis Gramm, StayAPI](/blog_post_author.png) By Denis Gramm, StayAPI· Aug 07, 2026 ·8 min read I hope you enjoy reading this blog post. If you want our team to help you with hotel data integration, [click here](/book-demo). Quick summary This guide maps what each official Trip.com program actually covers, who qualifies for access, and the working routes to hotel data if you don't. ## Table of contents - [Key Takeaways](#key-takeaways) - [What Official Trip.com API Documentation Exists](#what-official-trip-com-api-documentation-exists) - [What Developers Actually Need vs What's on Offer](#what-developers-actually-need-vs-what-s-on-offer) - [Getting Trip.com Hotel Data Without a Partnership](#getting-trip-com-hotel-data-without-a-partnership) - [The Trip.com Reviews Endpoint in Practice](#the-trip-com-reviews-endpoint-in-practice) - [Trip.com URL Parameters, Decoded](#trip-com-url-parameters-decoded) - [Getting Started](#getting-started) - [FAQ](#faq) There is no public Trip.com API documentation. If you've been searching for it, expecting a developer portal with a signup button, that portal doesn't exist. Trip.com's official APIs are real, but every one of them sits behind a partner agreement. The docs are the reward for approval, and you can't read them before applying. That gap is worth mapping properly, because the programs differ a lot in what they cover and who they accept. This guide goes through each official route, what its documentation actually contains, and how developers get Trip.com hotel data when partnership is off the table. ## Key Takeaways - **Trip.com has no public API docs.** Every official program (affiliate, distribution, supplier) gates its documentation behind an application and approval. - **The affiliate program is the only open door,** and it provides links, widgets, and commission tracking. There are no data endpoints in it. - **Distribution and supplier APIs require a commercial agreement.** They're built for travel agencies reselling inventory and hotels managing their own listings, with volume expectations to match. - **Review data has a working route without partnership.** Third-party data APIs return Trip.com guest reviews as structured JSON, the same pattern that works for the [Booking.com API](https://stayapi.com/blog/booking-com-api). - **The hotelId in any Trip.com URL is the key.** Grab it from the address bar and you can query data for that property directly. ## What Official Trip.com API Documentation Exists ![What Official Trip.com API Documentation Exists | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6MjI4LCJwdXIiOiJibG9iX2lkIn19--6086bb462ac2dc772ac12685cf8711631657498a/what_official_trip_com_api_documentation_exists_b.png?disposition=inline) Trip.com Group runs several partner programs, and each one has its own gated documentation. | Program | Who It's For | What the Docs Cover | Data Endpoints? | | --- | --- | --- | --- | | **Affiliate program** | Publishers, content sites | Link building, widgets, commission reporting | No | | **Distribution API** | Travel agencies, resellers | Booking flows, inventory access | Yes, under contract | | **Supplier/hotel APIs** | Hotels and chains listing on Trip.com | Rates, availability, content for your own property | Own property only | The affiliate program has open signup, and it's where most searches for Trip.com developer access end up. What it offers is monetization: deep links, search widgets, and commission tracking on bookings you refer. Useful for a travel content site. Empty for anyone who needs hotel data in their own system. The distribution API is the real thing: programmatic inventory, pricing, and booking. It's also a commercial partnership with an application process, integration review, and volume expectations. Typically the companies that get through are established agencies and resellers, and timelines run months. Supplier APIs point the other direction: hotels pushing their own rates and availability onto the platform. This is what people usually mean by Ctrip XML: a two-way XML connection, typically [run through a channel manager](https://www.siteminder.com/ctrip/), that sends availability, rates, and inventory to Trip.com Group and delivers bookings back to the hotel's system. They provide no visibility into other properties. If your goal is reading data about arbitrary hotels (reviews, details, market presence), none of these programs is designed for you. ## What Developers Actually Need vs What's on Offer Most people hunting for Trip.com API documentation want one of four things. | You Need | Official Route | Practical Route | | --- | --- | --- | | **Guest reviews** | None | Third-party data API | | **Hotel details and content** | Distribution partners only | Third-party data API | | **Rates and availability** | Distribution partners only | Cross-OTA rate endpoints for the same properties | | **Booking capability** | Distribution API (contract) | Affiliate deep links | The pattern: booking and monetization have official answers, data access mostly doesn't. That's common across OTAs, and it's the same wall we documented for Booking.com and Agoda. Trip.com's review pool is worth the chase for many teams. The platform's guest base skews heavily toward Asia-Pacific travelers, so its reviews often cover a market segment that's thin on Western OTAs. For hotels courting that market, those reviews are feedback you can't get anywhere else. ## Getting Trip.com Hotel Data Without a Partnership ![Getting Trip.com Hotel Data Without a Partnership | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6MjMwLCJwdXIiOiJibG9iX2lkIn19--36a77d319688f6369047139d9c26dea2f56112ef/getting_trip_com_hotel_data_without_a_partnership_b.png?disposition=inline) Three routes, in ascending order of reliability. **Waiting on partnership approval** works if you're genuinely a reseller or agency with volume to promise. For a data use case, applying for a distribution contract is the wrong tool and usually a dead end. **Scraping** works technically: Trip.com pages load data through internal endpoints you can intercept. We covered the general technique and its costs in our [hotel data scraper guide](https://stayapi.com/blog/hotel-data-scraper). The maintenance reality applies in full here: bot detection, shifting page structures, and pipelines that break silently. **A third-party data API** is the maintained version of the same access. Data providers keep the extraction layer working and publish actual documentation, the thing this search started with. The [Trip.com API from StayAPI](https://stayapi.com/apis/tripcom) delivers guest reviews for any hotel on the platform as structured JSON. Alongside it, a parallel set of [Ctrip endpoints](https://stayapi.com/apis/ctrip) covers Trip.com Group's Chinese-market platform with search, hotel details, rooms, and reviews. Scope honesty: the Trip.com surface is reviews today, so if you need nightly rates for those same properties, you'd pull them through Booking.com or Google Hotels endpoints under the same API key. | | **Partnership** | **DIY Scraping** | **Data API (StayAPI)** | | --- | --- | --- | --- | | **Documentation you can read now** | No | n/a | Yes, public | | **Approval required** | Yes, commercial | No | No | | **Reviews access** | Not offered | Fragile | Yes, structured JSON | | **Maintenance burden** | None | Ongoing | None | | **Time to first data** | Months | Weeks | Minutes | ## The Trip.com Reviews Endpoint in Practice ![The Trip.com Reviews Endpoint in Practice | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6MjMyLCJwdXIiOiJibG9iX2lkIn19--fedf25e090e0f82728306b40812bc3823d772e81/the_trip_com_reviews_endpoint_in_practice_b.png?disposition=inline) Here's what documented access looks like once you have an API key. Hotel 702258 is a real property with 919 reviews on the platform. ``` curl -X GET "https://api.stayapi.com/v1/tripcom/hotel/reviews/702258?page=1&page_size=10" \ -H "x-api-key: YOUR_API_KEY" ``` The response (truncated): ``` { "success": true, "hotel_id": 702258, "data": { "total_reviews": 919, "reviews": [...], ... } } ``` | Field | Description | | --- | --- | | `rating` | Guest score out of 10 | | `title` | Review headline | | `text` | Full review content | | `reviewer_name` | Guest display name | | `stay_date` | When the guest stayed | Pagination is built in (`page` and `page_size`), and the data is real-time: you make a request, you get the current state of that hotel's reviews. The full parameter list is in the [Trip.com reviews endpoint documentation](https://stayapi.com/docs/endpoints/tripcom/hotel-reviews). ## Trip.com URL Parameters, Decoded ![Trip.com URL Parameters, Decoded | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6MjM0LCJwdXIiOiJibG9iX2lkIn19--6cf600ee2138b2bc6cdbf12b7f8adb890d42affe/trip_com_url_parameters_decoded_b.png?disposition=inline) A surprising number of developers land on this question, so here's the practical answer. Trip.com hotel pages encode the stay in the URL query string. A detail-page URL typically carries a `hotelId`, `checkIn` and `checkOut` dates in YYYY-MM-DD format, and guest count parameters. Change the dates in the URL and the page reloads priced for the new stay. For data work, one parameter matters: **the hotelId is the stable identifier for the property** , and it's the same ID the reviews endpoint above expects. Copy it straight from the address bar of any hotel page. No lookup step, no scraping required to find it. Exact parameter names vary a little across locales and page versions, so treat the URL as a convenient ID source rather than a stable API of its own. ## Getting Started 1. Sign up at [stayapi.com](https://stayapi.com/users/sign_up). Free tier, no credit card, no partner application. 2. Open any Trip.com hotel page and copy the hotelId from the URL. 3. Make your first call with the curl example above, swapping in your hotel ID and API key. 4. For a no-code pipeline, the [Trip.com reviews to Google Sheets integration](https://stayapi.com/integrations/trip-com-reviews-to-google-sheets) walks through landing the data in a spreadsheet, and the same pattern feeds Looker Studio, Power BI, N8N, or Make.com. For portfolio-scale review monitoring, [book a demo call](https://stayapi.com/book-demo). ## FAQ ### Does Trip.com have a public API? No. All official Trip.com APIs (affiliate, distribution, supplier) require an application and agreement before you can even read the documentation. Third-party data APIs are the route that needs no approval. ### How do I get official Trip.com API access? Apply through Trip.com Group's partner channels for the program that matches your business: affiliate for monetization, distribution for resell inventory, supplier if you operate a listed property. Data-only use cases generally don't fit any of the three. ### What are the checkin and checkout parameters in Trip.com hotel URLs? Trip.com hotel URLs typically carry `checkIn` and `checkOut` dates in YYYY-MM-DD format plus guest counts, and the page reprices when you change them. The most useful parameter is `hotelId`, which identifies the property and works as the ID in data API calls. ### Is there a free Trip.com API? No official free API exists. Data providers with free tiers are the closest option (StayAPI's free tier covers testing the Trip.com reviews endpoint). ### What is Ctrip XML? It's Trip.com Group's two-way XML connectivity for hotels. A channel manager or PMS pushes availability, rates, and inventory to Ctrip and Trip.com and receives bookings back, and the hotel requests the connection through its Trip.com market manager. It covers the hotel's own listing only; agencies reselling Trip.com inventory go through the separate distribution program. ### What's the difference between Trip.com and Ctrip? Same group, different platforms: Trip.com serves the international market while Ctrip is the Chinese-market brand, with separate hotel IDs and review pools. Data coverage differs too: Ctrip endpoints include search, details, and rooms alongside reviews. Ship in 3 days ## Ready to simplify your hotel data? Join other developers using StayAPI to build the next generation of travel applications. Get started for free today. [Start Building Free](/users/sign_up)[Book a Demo](/book-demo) [← Back to Blog](/blog)[Previous: Agoda API Key: How to Get One (and What It Includes) →](/blog/agoda-api-key) Hotel data ### Want accurate hotel data? Stop building data pipelines and start building product. Reliable access to hotel reviews, prices, and details with StayAPI. [Book a Demo](/book-demo) ## Table of contents - [Key Takeaways](#key-takeaways) - [What Official Trip.com API Documentation Exists](#what-official-trip-com-api-documentation-exists) - [What Developers Actually Need vs What's on Offer](#what-developers-actually-need-vs-what-s-on-offer) - [Getting Trip.com Hotel Data Without a Partnership](#getting-trip-com-hotel-data-without-a-partnership) - [The Trip.com Reviews Endpoint in Practice](#the-trip-com-reviews-endpoint-in-practice) - [Trip.com URL Parameters, Decoded](#trip-com-url-parameters-decoded) - [Getting Started](#getting-started) - [FAQ](#faq) About StayAPI StayAPI: Hotel Data API For travel-tech developers We collect, clean, and standardize hotel data so you can build amazing travel products without maintaining your own data collection. 50+ Endpoints 5 Major Platforms Supported sources Booking.comTripAdvisorAirbnbAgodaGoogle Hotelsand more