Skip to main content

Trip.com: Reseller Connection

Connect Trip.com to Ventrata to sync availability and prices and receive bookings instantly. Reaches Chinese and Asia Pacific travelers.

Trip.com logo

 

Trip.com is the international brand of Trip.com Group, one of the world's largest online travel agencies (OTAs) and the leading one in China, selling tickets, tours and activities in more than 140 countries alongside flights and hotels. For operators, it brings mainland Chinese and wider Asia Pacific outbound travelers through the Trip.com and Ctrip websites and apps and B2B partners, with 19 languages and 24/7 support for the traveler.

 

Connecting Trip.com to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

 

To learn more about partnering with Trip.com, visit trip.com.

 

Primary website

Tags

OTA · OTA with Tours & Activities Division

Destination markets

🌎 Global

Source markets

🇨🇳 China · 🇭🇰 Hong Kong · 🇮🇩 Indonesia · 🇯🇵 Japan · 🇲🇾 Malaysia · 🇵🇭 Philippines · 🇸🇬 Singapore · 🇰🇷 South Korea · 🇹🇼 Taiwan · 🇹🇭 Thailand · 🇻🇳 Vietnam

Specialties

Chinese and international source markets

Connection features

Availability Sync · Pricing Sync · Bookings Sync

Ventrata Booked GMV (last 12 months)

US$1M+

Ventrata Booked Suppliers (last 12 months)

25+

Developed by

Trip.com (using Ventrata's OCTO API)

 

This reseller connection lets you sell your products through Trip.com without managing availability, pricing and bookings by hand. Features of this connection include:

  • Availability Sync – Trip.com checks your live availability in Ventrata.

  • Pricing Sync – Trip.com gets your prices from your reseller pricing in Ventrata.

  • Bookings Sync – bookings, updates and cancellations from Trip.com are created in Ventrata instantly, and customers get Ventrata tickets.

 

You're using a best-in-class Trip.com connection

Trip.com Group has given Ventrata a partner award three years in a row at its global partner conference, so you can rely on a connection Trip.com trusts to bring your tours and tickets to its travelers across Asia-Pacific and beyond.

Trip.com Attractions & Tours Strategic Partner Award 2026

Ventrata received the Strategic Partner Award at the ENVISION Attractions & Tours Sub-Forum in Shanghai, for delivering robust connectivity for tour and attraction operators worldwide. Learn more

Trip.com Attractions & Tours Excellent Partner Award 2025

Ventrata received the Excellent Partner Award at the ENVISION 2025 Attractions & Tours Global Partners Forum, for connection quality and close collaboration with the Trip.com Attractions & Tours team. Learn more

Trip.com Attractions & Tours Strategic Partner Award 2024

Ventrata received the Strategic Partner Award at the Global Partner Summit in Abu Dhabi, as one of a select group of partners outside China, for its performance, leadership in OCTO open API standardization, and collaboration with the Attractions & Tours team. Learn more

 

Creating the Trip.com Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

  • You must have a commercial agreement with Trip.com for them to sell your products. To inquire about partnering with them, contact them via trip.com.

  • You must have Trip.com created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

 

  1. In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Trip.com from the list of partners.

  2. Select Trip.com Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.

  3. (Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Trip.com connections and would like to differentiate between them more easily in the future.

  4. Press the Create Octo Connection button.

 

 

 

 

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

 

Mapping Products to Trip.com

Securely share the OCTO API key shown on the connection you've created to your Trip.com contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Trip.com team to complete this.

 

Your Ventrata configuration is complete. You do not need to take any further steps.

 

 

📗 TIP

Trip.com can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

 

Managing the Trip.com Connection

  • Allow or disallow products: limit which destinations, products and options Trip.com can access. See how to allow or disallow products.

  • Rename the connection to tell several Trip.com connections apart.

 

Connection Features Detailed

This section is for anyone who wants to know exactly how the Trip.com connection works: which Ventrata OCTO API calls Trip.com makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

 

In short: Trip.com pulls everything it needs from Ventrata. It reads your products, checks your availability and prices, and sends bookings and cancellations. Ventrata doesn't push changes to Trip.com, so anything you change in Ventrata reaches Trip.com the next time it checks.

 

Timings are typical for Trip.com and rounded, and they can change if Trip.com changes how it syncs.

 

Product Mapping

❌

You can't map products from Ventrata. Trip.com maps them on its side, through your account manager or Trip.com's portal.

This works as follows:

  • Get Products (GET /products) – when Trip.com sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child).

  • Get Product (GET /products/{productId}) – Trip.com re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

  • Mapping on Trip.com's side – Trip.com links each Ventrata option and unit to its own listing and ticket types. Your Trip.com account manager does this for you, or you do it in Trip.com's own portal if Trip.com offers one. You only share the connection's API key.

 

Typically with Trip.com:

  • Trip.com reads your full product list every few days.

  • It re-reads each product about every 10 minutes.

 

What this means for you: Trip.com can only sell what it has mapped. When you add a product, option or unit in Ventrata, Trip.com may see it on its next refresh, but it won't sell it until it's mapped. So tell your Trip.com account manager whenever you add one.

Content Sync

❌

Trip.com doesn't read your product content from Ventrata.

Trip.com uses the descriptions, images and other content set up on its own side, so update your content with Trip.com directly.

Availability Sync

✅

Trip.com checks your live availability in Ventrata. Ventrata doesn't push availability changes to Trip.com.

This works as follows:

  • Availability Check (POST /availability) – Trip.com sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (AVAILABLE, LIMITED, SOLD_OUT, CLOSED or FREESALE), the remaining vacancies, the booking cutoff and an availabilityId, which Trip.com needs to book that slot.

  • Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Trip.com can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

 

Typically with Trip.com:

  • Availability Check: Trip.com checks your products around the clock, usually starting today and covering about 3 months per request, looks up to about 3 months ahead and re-checks the same product and dates about every 40 minutes.

  • Checks are spread evenly around the clock, which points to a scheduled background sync rather than live customer searches.

 

What this means for you: when you close a date, change capacity or sell out in Ventrata, Trip.com shows it after its next check. For dates it checks regularly, that's within about 40 minutes. Dates further ahead are usually checked less often.

Pricing Sync

✅

Your prices come back with every availability check, once Trip.com asks for them with the octo/pricing capability.

This works as follows:

  • octo/pricing capability – Trip.com asks for prices by adding octo/pricing to the Octo-Capabilities header of its requests. Without it, Ventrata sends availability with no prices at all.

  • Availability Check (POST /availability) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Trip.com, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

  • Group prices – when Trip.com also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing.

  • Booking Reservation (POST /bookings) and Booking Confirmation (POST /bookings/{uuid}/confirm) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at.

 

Typically with Trip.com:

  • Trip.com requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

  • Trip.com sends the number of people per unit type, so group prices are calculated for the actual booking.

 

‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Trip.com to map your products, ask them to enable pricing (octo/pricing) as well, or switch it on yourself if you map in Trip.com's portal. Otherwise it may be off, and Trip.com won't receive your Ventrata prices.

📗 TIP – If prices on Trip.com look wrong, check the Trip.com reseller's pricing in Ventrata first: that's what Trip.com reads.

Promotions Sync

❌

Your Ventrata promotions don't apply on Trip.com.

Prices on Trip.com don't include promotions you create in Ventrata. Set up any promotions with Trip.com directly.

Bookings Sync

✅

Bookings and cancellations made on Trip.com are created in Ventrata instantly, and customers get Ventrata tickets.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when a customer starts checkout on Trip.com, Trip.com sends the product, option, chosen slot (availabilityId) and one unit item per person. Ventrata checks capacity again and creates an ON_HOLD booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – once payment goes through, Trip.com confirms the hold, with its own booking reference and the customer's contact details. The booking becomes CONFIRMED in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Trip.com gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, Trip.com never confirms, and the hold expires on its own and frees the places.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – when a customer cancels on Trip.com, Trip.com cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Trip.com has to contact you.

  5. Change: Trip.com doesn't use Booking Update (PATCH /bookings/{uuid}), so a change most likely reaches Ventrata as a cancellation plus a new booking.

 

Typically with Trip.com:

  • Trip.com doesn't set a hold time, so the default hold time applies.

  • A typical Trip.com booking is for about 2 people.

  • It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire.

  • Trip.com also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) about every 5 hours, for example to reconcile its records.

 

‼️ IMPORTANT – Bookings sync one way, from Trip.com to Ventrata. If you cancel, change or rebook a booking from Trip.com in Ventrata, for example in the Dashboard, Trip.com isn't notified. Contact Trip.com so the booking is cancelled or changed on their side too, or ask the customer to cancel through Trip.com.

Pickups/Dropoff Sync

❌

Trip.com doesn't send pickup or drop-off details with its bookings.

If your products include pickups, check with Trip.com how it collects pickup details, or arrange them with the customer.

Custom Questions Sync

❌

Trip.com doesn't send answers to your booking questions.

If you rely on booking questions, for example names or dietary needs, check with Trip.com how it collects that information.

Extras Sync

❌

Extras and add-ons can't be booked through Trip.com.

Customers can only book your main products and options on Trip.com. Sell extras separately, for example on arrival.

Redemption Sync

❌

Redemptions aren't reported to Trip.com.

Ventrata doesn't notify Trip.com when a ticket is scanned or redeemed. Trip.com only sees a redemption if it reads the booking back from Ventrata.

Pass Walkup Scanning Sync

❌

Trip.com pass holders can't be scanned at your entrance without a booking.

Customers from Trip.com need a booking made through Trip.com before they visit.

Gift Card Sync

❌

Ventrata gift cards can't be sold or redeemed through Trip.com.

Gift cards bought in Ventrata can't be used on Trip.com, and Trip.com can't sell Ventrata gift cards.

✅ supported · ❌ not supported

 

Good to know: limits and details of the Trip.com connection

  • Delays: availability and prices reach Trip.com only when it checks, so there's always a short delay after you change something in Ventrata.

  • Cancellation cutoff: Trip.com can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.

  • What Trip.com can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.

  • Tickets: Trip.com issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.

  • Test bookings: Trip.com can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

 

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Trip.com.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

 

 

Partner Information

Trip.com Travel Singapore Pte. Ltd.

30 Raffles Place, #29-01

Singapore City, 048622, Singapore

 

Ventrata Partner ID: d143eb10-863b-461f-8d88-57c36d6b55a3

Did this answer your question?