TripXOXO is an online marketplace for tours, activities, attractions and transfers run from India, covering more than 140 countries and 900 cities and distributing supplier product through its consumer site alongside B2B, white-label and affiliate channels. For operators, it brings Indian outbound travelers heading to Southeast Asia, the Gulf and Europe, destinations such as Pattaya, Kuala Lumpur, Singapore, Bali, Dubai and Spain, together with international independent travelers, buying theme park entry, adventure activities, safaris and city sightseeing.

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

To learn more about partnering with TripXOXO, visit tripxoxo.com.

Primary website	tripxoxo.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Indian outbound travelers to Asia, the Gulf and Europe
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Globick (using Ventrata's OCTO API)

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

Availability Sync – TripXOXO checks your live availability in Ventrata.
Pricing Sync – TripXOXO gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from TripXOXO are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the TripXOXO Connection

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

Before you begin:

You must have a commercial agreement with TripXOXO for them to sell your products. To inquire about partnering with them, contact them via tripxoxo.com.
You must have TripXOXO 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.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select TripXOXO from the list of partners.
Select TripXOXO 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.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple TripXOXO connections and would like to differentiate between them more easily in the future.
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 TripXOXO

Securely share the OCTO API key shown on the connection you've created with your TripXOXO 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 TripXOXO team to complete this.

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

📗 TIP

TripXOXO 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 TripXOXO Connection

Allow or disallow products: limit which destinations, products and options TripXOXO can access. See how to allow or disallow products.
Rename the connection to tell several TripXOXO connections apart.

Connection Features Detailed

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

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

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

Product Mapping	❌	You can't map products from Ventrata. TripXOXO maps them on its side, through your account manager or TripXOXO's portal. This works as follows: Get Products (`GET /products`) – when TripXOXO 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}`) – TripXOXO re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on TripXOXO's side – TripXOXO links each Ventrata option and unit to its own listing and ticket types. Your TripXOXO account manager does this for you, or you do it in TripXOXO's own portal if TripXOXO offers one. You only share the connection's API key. Typically with TripXOXO: TripXOXO reads your full product list about once a day. It re-reads each product about every 2 hours. What this means for you: TripXOXO can only sell what it has mapped. When you add a product, option or unit in Ventrata, TripXOXO may see it on its next refresh, but it won't sell it until it's mapped. So tell your TripXOXO account manager whenever you add one.
Content Sync	❌	TripXOXO doesn't read your product content from Ventrata. TripXOXO uses the descriptions, images and other content set up on its own side, so update your content with TripXOXO directly.
Availability Sync	✅	TripXOXO checks your live availability in Ventrata. Ventrata doesn't push availability changes to TripXOXO. This works as follows: Availability Check (`POST /availability`) – TripXOXO 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 TripXOXO needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so TripXOXO can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with TripXOXO: Availability Check: TripXOXO checks each product about every 7 hours. Availability Calendar: TripXOXO checks each product about every 10 hours. Checks are busiest between 00:00 and 06:00 UTC, which suggests most checks are live, as customers browse TripXOXO. What this means for you: when you close a date, change capacity or sell out in Ventrata, TripXOXO shows it after its next check. For dates it checks regularly, that's within about 10 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once TripXOXO asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – TripXOXO 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 TripXOXO, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when TripXOXO 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. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask TripXOXO to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in TripXOXO's portal. Otherwise it may be off, and TripXOXO won't receive your Ventrata prices. 📗 TIP – If prices on TripXOXO look wrong, check the TripXOXO reseller's pricing in Ventrata first: that's what TripXOXO reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on TripXOXO. Prices on TripXOXO don't include promotions you create in Ventrata. Set up any promotions with TripXOXO directly.
Bookings Sync	✅	Bookings and cancellations made on TripXOXO are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on TripXOXO, TripXOXO 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. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, TripXOXO confirms the hold. 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. TripXOXO gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, TripXOXO never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on TripXOXO, TripXOXO 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 TripXOXO has to contact you. Change: Booking Update (`PATCH /bookings/{uuid}`) – lets TripXOXO change a booking in place, for example a new date, time or number of people. Some resellers cancel and rebook instead. ‼️ IMPORTANT – Bookings sync one way, from TripXOXO to Ventrata. If you cancel, change or rebook a booking from TripXOXO in Ventrata, for example in the Dashboard, TripXOXO isn't notified. Contact TripXOXO so the booking is cancelled or changed on their side too, or ask the customer to cancel through TripXOXO.
Pickups/Dropoff Sync	❌	TripXOXO doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with TripXOXO how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	TripXOXO doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with TripXOXO how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through TripXOXO. Customers can only book your main products and options on TripXOXO. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to TripXOXO. Ventrata doesn't notify TripXOXO when a ticket is scanned or redeemed. TripXOXO only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	TripXOXO pass holders can't be scanned at your entrance without a booking. Customers from TripXOXO need a booking made through TripXOXO before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through TripXOXO. Gift cards bought in Ventrata can't be used on TripXOXO, and TripXOXO can't sell Ventrata gift cards.

✅ supported · ❌ not supported

Good to know: limits and details of the TripXOXO connection

Delays: availability and prices reach TripXOXO only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: TripXOXO can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What TripXOXO 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: TripXOXO issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: TripXOXO 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 TripXOXO.

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.

📚 More about Ventrata connections

Partner Information

Travelport Hopdays India Pvt. Ltd.

tripxoxo.com

Ventrata Partner ID: 3d73e52f-fbc5-47ff-8ef1-f2e29f67a92e

TripXOXO: Reseller Connection