WAUG is a Seoul-based online travel marketplace for activities and attraction tickets, with offices in Seoul and Singapore, listing attraction tickets, tours, transport passes, airport transfers, eSIMs, sports tickets and fine-dining reservations across around 300 destinations. For operators, it brings Korean outbound travelers, its core audience, whose trips reach well beyond its Asian base into Europe, Australia and North America, booking tickets and tours ahead of the trip.

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

To learn more about partnering with WAUG, visit waug.com.

Primary website	waug.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🇰🇷 South Korea
Specialties	Korean source market
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	WAUG (using Ventrata's OCTO API)

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

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

Creating the WAUG Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the WAUG connection

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

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

WAUG Inc.

4F, 36 Gyeonghuigung-gil, Jongno-gu, Seoul

Republic of Korea (서울특별시 종로구 경희궁길 36 4층)

waug.com

Ventrata Partner ID: 22ecebb7-b70f-42f1-a9b4-9c42a9106b21

WAUG: Reseller Connection