Nexus DMC is a destination management company (DMC) through which travel agents and tour operators build and sell trips in about 100 countries, covering activities, ground handling, transfers and accommodation with one point of contact and one payment. For operators, it brings trade demand only: agents and advisors packaging activities into multi-destination itineraries, long-lead and group bookings, supported by more than 900 staff across 20 countries with a presence in India, Southeast Asia, Europe, Australia, New Zealand and South America.

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

To learn more about partnering with Nexus DMC, visit nexusdmc.com.

Primary website	nexusdmc.com
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Trade-only multi-destination itineraries for agents
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Nexus DMC (using Ventrata's OCTO API)

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

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

Creating the Nexus DMC Connection

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

Before you begin:

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

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

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

📗 TIP

Nexus DMC 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 Nexus DMC Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Nexus DMC connection

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

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

ORN Vacations Private Limited

nexusdmc.com

Ventrata Partner ID: 0d6cbd98-70b0-4345-8505-bd43f4ecea11

Nexus DMC: Reseller Connection