Jonview is a Canadian business-to-business receptive tour operator owned by Japanese travel group H.I.S., packaging cross-Canada and North American product such as alpine resorts, wilderness trips and rail journeys from around 2,000 Canadian suppliers. For operators, it brings international tour operators in more than 50 countries building group and independent itineraries, moving over 300,000 visitors a year, long-lead trade demand rather than consumer traffic.

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

To learn more about partnering with Jonview, visit jonview.com.

Primary website	jonview.com
Tags	Receptive & Inbound Operator
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Canadian packages for international tour operators
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Developed by	Jonview (using Ventrata's OCTO API)

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

Availability Sync – Jonview checks your live availability in Ventrata.
Pricing Sync – Jonview gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Jonview are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – pickup and drop-off details from Jonview bookings are passed to Ventrata.

This connection is still in development and is not yet available to users.

Creating the Jonview Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Jonview connection

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

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

Jonview

jonview.com

Ventrata Partner ID: 1cea5daf-1a10-4f36-a053-bdaae7088036

Jonview: Reseller Connection