TBO is a business-to-business travel distribution platform listed in India, trading with agents as TBO Holidays and connecting more than 159,000 travel agencies, independent advisors and enterprise buyers in over 100 countries with hotels, flights, transfers, sightseeing, activities, rail and cruises. For operators, it brings trade demand only: agents booking on behalf of clients, strongest across India, the Middle East and Southeast Asia, weighted toward family and group travel and packaged alongside hotels and flights, with no consumer storefront.

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

To learn more about partnering with TBO, visit tboholidays.com.

Primary website	tboholidays.com
Tags	B2B Marketplace · Travel Agent
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Travel agent sales packaged with hotels and flights
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	TBO (using Ventrata's OCTO API)

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

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

Creating the TBO Connection

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

Before you begin:

You must have a commercial agreement with TBO for them to sell your products. To inquire about partnering with them, contact them via tboholidays.com. To start one, visit tboholidays.com/wholesaler.aspx.
You must have TBO 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 TBO from the list of partners.
Select TBO 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 TBO 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 TBO

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

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

📗 TIP

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

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

Connection Features Detailed

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

In short: TBO 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 TBO, so anything you change in Ventrata reaches TBO the next time it checks.

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

Product Mapping	❌	You can't map products from Ventrata. TBO maps them on its side, through your account manager or TBO's portal. This works as follows: Get Products (`GET /products`) – when TBO 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}`) – TBO re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on TBO's side – TBO links each Ventrata option and unit to its own listing and ticket types. Your TBO account manager does this for you, or you do it in TBO's own portal if TBO offers one. You only share the connection's API key. Typically with TBO: TBO reads your full product list about every 4 hours. It re-reads each product about every 10 hours. What this means for you: TBO can only sell what it has mapped. When you add a product, option or unit in Ventrata, TBO may see it on its next refresh, but it won't sell it until it's mapped. So tell your TBO account manager whenever you add one.
Content Sync	✅ / ❌	TBO can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when TBO adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach TBO on its next product refresh. Typically with TBO: TBO requests `octo/content`.
Availability Sync	✅	TBO checks your live availability in Ventrata. Ventrata doesn't push availability changes to TBO. This works as follows: Availability Check (`POST /availability`) – TBO 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 TBO needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so TBO can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with TBO: Availability Check: TBO checks each product about every 10 hours. What this means for you: when you close a date, change capacity or sell out in Ventrata, TBO 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 TBO asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – TBO 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 TBO, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when TBO 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 TBO to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in TBO's portal. Otherwise it may be off, and TBO won't receive your Ventrata prices. 📗 TIP – If prices on TBO look wrong, check the TBO reseller's pricing in Ventrata first: that's what TBO reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on TBO. Prices on TBO don't include promotions you create in Ventrata. Set up any promotions with TBO directly.
Bookings Sync	✅	Bookings and cancellations made on TBO 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 TBO, TBO 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, TBO 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. TBO gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, TBO 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 TBO, TBO 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 TBO has to contact you. Change: TBO doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with TBO: TBO doesn't set a hold time, so the default hold time applies. A typical TBO booking is for about 2 people. ‼️ IMPORTANT – Bookings sync one way, from TBO to Ventrata. If you cancel, change or rebook a booking from TBO in Ventrata, for example in the Dashboard, TBO isn't notified. Contact TBO so the booking is cancelled or changed on their side too, or ask the customer to cancel through TBO.
Pickups/Dropoff Sync	❌	TBO doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with TBO how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	TBO doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with TBO how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through TBO. Customers can only book your main products and options on TBO. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to TBO. Ventrata doesn't notify TBO when a ticket is scanned or redeemed. TBO only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	TBO pass holders can't be scanned at your entrance without a booking. Customers from TBO need a booking made through TBO before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through TBO. Gift cards bought in Ventrata can't be used on TBO, and TBO can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the TBO connection

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

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

Tek Travels FZCO

2408 Oaks Liwa Heights, Jumeirah Lake Towers (JLT), P.O. Box 34544, Dubai

United Arab Emirates

tboholidays.com

Ventrata Partner ID: 21246fee-1945-4e0b-90a7-f3ab809a5574

TBO: Reseller Connection