Vintia is a Belgian ticketing, booking and admissions provider, part of the SALTO WECOSYSTEM and formerly Gantner Ticketing, with Enviso among its products. More than 1,000 European zoos, museums, theme parks, spas and leisure centers use it for admissions, online ticketing, point of sale, group bookings and access control, making it a backend for mid-size and large leisure venues across Europe.
Connecting Vintia to Ventrata lets you resell products from operators that use Vintia (Enviso) as their ticketing system. Ventrata reads their live availability and prices from Vintia, and every booking you take is created directly in the operator's Vintia account, with tickets inside your Ventrata account.
To learn more about Vintia, visit vintia.com.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using Vintia's Enviso API) |
This operator connection (also called a backend) lets you resell products from operators that use Vintia as their booking system, with every booking created directly in Vintia. Features of this connection include:
Availability Sync – live availability comes from the operator's Vintia account.
Pricing Sync – prices come from Vintia, or you set prices in Ventrata.
Bookings Sync – bookings made in Ventrata are created in the operator's Vintia account.
Creating the Vintia Connection
🔐 Required Role Permissions: See Operators, Modify Operators, See Products, Modify Products
Before you begin:
You must have a commercial agreement with the operator for their rates and terms.
You must have the operator's Vintia credentials: Tenant Key, Api Key and Secret. See Step 1.
You must recreate the operator's products in Ventrata. See how to create products. The connection syncs availability, pricing and bookings, but doesn't create products in Ventrata.
Step 1: Get the Vintia Credentials
Ask the operator for the Tenant Key, Api Key and Secret of their Vintia (Enviso) account, and make sure they share them securely. If they're not sure where to find them, they can ask Vintia.
Step 2: Configure the Operator in Ventrata
In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.
In the Backend Partner section, select Vintia and enter the Tenant Key, Api Key and Secret.
Press Update Operator.
📒 NOTE – Each set of credentials connects you to one Vintia account. Set up each operator separately.
Step 3: Connect Each Product
Open the product in Products → Products and edit it. Check that Operator is set to this operator.
Tick Backend Connected. Tick Backend Availability to use availability from Vintia, and Backend Pricing to use prices from Vintia.
Press Update Product.
📒 NOTE
With Backend Pricing ticked, Ventrata records the prices Vintia sends. If Vintia sends both retail and net prices, the net price is recorded as your cost. If it sends only one of them, Ventrata calculates the other using the cost percentage set on the operator in the Ventrata Dashboard.
Mapping Products to Vintia
‼️ IMPORTANT
Mapping tells Ventrata which Vintia product, option and units to check availability for and book. If a backend-connected product isn't mapped correctly, its bookings fail. A red highlight across the product row shows an incorrectly mapped product.
In the Ventrata Dashboard, go to Products → Products and open the product.
Open the Mappings tab. It appears once the product is set to Backend Connected.
For each Ventrata option and unit, select the matching Vintia product, option and units from the dropdowns, which Ventrata loads from Vintia. Don't leave any field empty.
Press Save Changes.
📗 TIP
Make a test booking after mapping, and ask the operator to confirm it arrived in Vintia.
Managing the Vintia Connection
Update the mapping when the operator changes products, options or units in Vintia.
Replace the credentials on the operator if Vintia issues new ones.
Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to Vintia.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Vintia connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Vintia. For each feature, it explains what Ventrata does, when, and what that means for you.
In short: Ventrata asks Vintia for availability and prices whenever someone looks at a backend-connected product, and creates every booking in Vintia. Vintia doesn't send changes back to Ventrata.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the matching Vintia product in the Ventrata Dashboard. This works as follows:
What this means for you: if a product, option or unit is missing from the dropdown, it isn't available to you in Vintia yet. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks live availability in Vintia. This works as follows:
What this means for you: customers book against live Vintia availability, so you can't oversell a slot that's already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from Vintia. This works as follows:
|
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's Vintia account. This works as follows:
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Vintia. If a booking is changed or cancelled in Vintia, Ventrata isn't notified. |
Content Sync | ❌ |
Ventrata doesn't import product content from Vintia. Ventrata doesn't import product content from Vintia. You create and describe the products in Ventrata yourself. |
Promotions Sync | ❌ |
Promotions aren't sent to Vintia. Promotions aren't sent to Vintia. Your Ventrata promotions still apply to the price your customer pays in Ventrata. |
Pickups/Dropoff Sync | ❌ |
Pickup and drop-off details aren't passed to Vintia. Pickup and drop-off details aren't passed to Vintia. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Vintia. Answers to your booking questions aren't passed to Vintia. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Vintia. Extras and add-ons aren't booked in Vintia. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Vintia aren't sent back to Ventrata. Redemptions and other status changes in Vintia aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Vintia. Pass walk-up scanning isn't available with Vintia. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Vintia. Ventrata gift cards aren't passed to Vintia. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Vintia connection
Good to know: limits and details of the Vintia connection
Credentials per operator: the Vintia credentials are saved on the operator in Ventrata.
Live availability: availability comes from Vintia as people browse, so there's no availability to keep in sync by hand.
One-way bookings: changes made in Vintia don't reach Ventrata.
FAQs
I get an error when I save the operator's backend configuration.
I get an error when I save the operator's backend configuration.
The Vintia credentials are most likely incorrect. Check them with the operator. If the issue persists, contact our Technical Support.
There's no Backend Connected box in the product settings.
There's no Backend Connected box in the product settings.
The operator set on the product most likely doesn't have a backend configured. Check the operator's Backend Partner settings and try again. If the issue persists, contact our Technical Support.
The product, option or unit I want to map isn't in the dropdown.
The product, option or unit I want to map isn't in the dropdown.
The dropdowns list what's available to you in Vintia. Ask the operator to make it available. If the issue persists, contact our Technical Support.
Bookings fail for a backend-connected product.
Bookings fail for a backend-connected product.
Check the product's mapping first: every option and unit must be mapped. Then check that the slot is still available in Vintia. If the issue persists, contact our Technical Support.
📚 More about Ventrata connections
Partner Information
Vintia
Ventrata Partner ID: cb9f6c14-9cf8-4e5b-a055-df6f96b3cbfe