Zaui is a Vancouver-built reservation platform for tour, activity and transportation businesses, in the market for more than twenty years, with an online booking engine, channel manager, mobile check-in and reseller and agent portals. For operators, it brings trade demand, with resellers and travel agents on Zaui booking partner products through their own portal logins across its network of tour, shuttle and attraction operators.

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

To learn more about partnering with Zaui, visit zaui.com.

📒 NOTE

Looking to resell products from operators that use Zaui instead? See Zaui: Operator Backend.

Primary website	zaui.com
Tags	Reseller System
Destination markets	🌎 Global
Source markets	🌎 Global
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Zaui (using Ventrata's OCTO API)

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

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

Creating the Zaui Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Zaui connection

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

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

Zaui Software Ltd.

Suite 423-119 Pender Street West, Vancouver, BC V6B 1S5

Canada

zaui.com

Ventrata Partner ID: e67349dd-5231-4c91-9996-1abfea2a2b93

Zaui: Reseller Connection