Ingresso is a UK ticket distribution and channel management platform, part of accesso Technology Group, connecting attractions, theaters, live entertainment and sports venues to more than 100 distribution partners through a single API, with GetYourGuide, Expedia, Groupon, Tiqets and Headout among them. It reports over 34 million tickets sold and more than 300 connected attractions and venues, giving sellers one route into inventory that spans multiple regions and a large global consumer base.
Connecting Ingresso to Ventrata lets you resell products from operators that use Ingresso as their booking system. Ventrata reads their live availability and prices from Ingresso, and every booking you take is created directly in the operator's Ingresso account.
To learn more about Ingresso, visit ingresso.co.uk.
Primary website | |
Tags | Booking / Ticketing System · Third-Party Booking System Channel Manager |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using Ingresso API) |
This operator connection (also called a backend) lets you resell products from operators that use Ingresso as their primary booking system, with every booking created directly in Ingresso. Features of this connection include:
Availability Sync – live availability comes from the operator's Ingresso account.
Pricing Sync – prices come from Ingresso, or you set prices in Ventrata.
Bookings Sync – bookings post from Ventrata to Ingresso, and Ingresso issues the tickets or vouchers.
Ingresso's external API used for this connection is a custom API that does not follow the OCTO API standard, which may limit certain functionality and capabilities.
Creating the Ingresso 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 API key for the operator. See the steps below.
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: Configure the Operator in Ventrata
Ask the operator for the API key for your account.
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 Ingresso and enter the API key.
Press Update Operator.
Step 2: Connect Each Product
Open the operator's 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 Ingresso, and Backend Pricing to use prices from Ingresso.
Press Update Product.
Mapping Products to Ingresso
‼️ IMPORTANT
Mapping tells Ventrata which Ingresso 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 Ingresso product, option and units from the dropdowns, which Ventrata loads from Ingresso. 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 their Ingresso account.
Managing the Ingresso Connection
Update the mapping when the operator changes products, options or units in Ingresso.
Replace the key on the operator if Ingresso or the operator issues a new one.
Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to Ingresso.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Ingresso connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Ingresso, using Ingresso API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks Ingresso for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's Ingresso account. Ingresso doesn't send changes back to Ventrata.
Timings are typical for Ingresso and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's Ingresso product in the Ventrata Dashboard. This works as follows:
What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in Ingresso. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from Ingresso. Ventrata doesn't import product content from Ingresso. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in Ingresso. This works as follows:
What this means for you: customers book against the operator's live Ingresso availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from Ingresso. This works as follows:
|
Promotions Sync | ❌ |
Promotions aren't sent to Ingresso. Promotions aren't sent to Ingresso. Your Ventrata promotions still apply to the price your customer pays in Ventrata. |
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's Ingresso account. This works as follows:
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Ingresso. If the operator changes or cancels a booking in Ingresso, Ventrata isn't notified. Ask the operator to tell you about any changes they make. |
Pickups/Dropoff Sync | ❌ |
Pickup and drop-off details aren't passed to Ingresso. Pickup and drop-off details aren't passed to Ingresso. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Ingresso. Answers to your booking questions aren't passed to Ingresso. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Ingresso. Extras and add-ons aren't booked in Ingresso. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Ingresso aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in Ingresso aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Ingresso. Pass walk-up scanning isn't available with Ingresso. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Ingresso. Ventrata gift cards aren't passed to Ingresso. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Ingresso connection
Good to know: limits and details of the Ingresso connection
Live availability: availability comes from Ingresso as people browse.
One-way bookings: changes the operator makes in Ingresso don't reach Ventrata.
Custom API: Ingresso's API isn't OCTO, so some features may be limited compared with OCTO backends.
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 API key or endpoint is most likely incorrect. Check them with your 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 the operator has made available to you in Ingresso. Ask the operator. 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 Ingresso. If the issue persists, contact our Technical Support.
📚 More about Ventrata connections
Partner Information
Ingresso Group Limited
Unit 5
The Pavilions, Ruscombe Business Park, Ruscombe, Reading, RG10 9NN, United Kingdom
Ventrata Partner ID: 4253ef7a-3a2d-4943-9de3-5d2b12509bfc