Wannar is a Chinese-language online travel agency (OTA) selling North American and European product to Chinese-speaking travelers, covering guided tours, self-guided packages, day trips, attraction tickets, hotels and car rental. For operators, it brings mainland and Greater China outbound travelers together with Chinese-speaking residents of North America, a segment few Western marketplaces serve in Chinese, booking multi-day tours and city attractions in their own language.

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

To learn more about partnering with Wannar, visit wannar.com.

Primary website	wannar.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🇨🇳 China
Specialties	Chinese-speaking source markets
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	Wannar (using Ventrata's OCTO API)

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

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

Creating the Wannar Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Wannar connection

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

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

Wannar Travel Inc.

303 Perimeter Center N #300

Atlanta, GA 30346, United States

wannar.com

Ventrata Partner ID: c7bc8a93-6b1f-4d63-901c-58cb022e7c58

Wannar: Reseller Connection