TrvlNxt is the business-to-business (B2B) travel platform of Riya Travel, part of the Mumbai-headquartered Riya Group, supplying travel agencies with flights, hotels, activities, European rail passes, cruises, car rental, insurance, visas and forex across India, the United States, Canada, the UAE and Thailand. For operators, it brings trade demand only: Indian outbound and diaspora travel agents who package activities alongside flights, hotels and rail into long-lead itineraries.

Connecting TrvlNxt to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with TrvlNxt, visit trvlnxt.parikshan.net.

Primary website	trvlnxt.parikshan.net
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Indian outbound and diaspora travel agents packaging long-lead itineraries
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	TrvlNxt (using Ventrata's OCTO API)

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

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

Creating the TrvlNxt Connection

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

Before you begin:

You must have a commercial agreement with TrvlNxt for them to sell your products. To inquire about partnering with them, contact them via trvlnxt.parikshan.net.
You must have TrvlNxt 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 TrvlNxt from the list of partners.
Select TrvlNxt 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 TrvlNxt 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 TrvlNxt

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the TrvlNxt connection

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

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

Riya Holidays Pvt. Ltd.

Gulab Building, P. D'Mello Road, Fort, Mumbai 400001

India

trvlnxt.parikshan.net

Ventrata Partner ID: 3ba943dd-9493-410b-b8c4-c7bafaa2742e

TrvlNxt: Reseller Connection