ROLLER is venue management software for leisure, entertainment and attractions businesses, used by more than 3,500 venues in over 30 countries across the Americas, EMEA and Asia Pacific. Its venues are trampoline parks, family entertainment centers, indoor playgrounds, karting, climbing gyms, water parks, theme parks, museums, zoos and aquariums, handling more than 5 million bookings a month.
Connecting ROLLER to Ventrata lets you resell products from operators that use ROLLER as their booking system. Ventrata reads their live availability from ROLLER, and every booking you take is created directly in the operator's ROLLER account.
To learn more about ROLLER, visit roller.software.
📒 NOTE
This connection is available only to specific client accounts. If you're interested in using it, contact our Technical Support or your Ventrata Customer Success Manager.
Primary website | |
Tags | Custom / Proprietary Operator System |
Connection features | Availability Sync · Bookings Sync |
Developed by | Ventrata (using ROLLER API) |
This operator connection (also called a backend) lets you resell products from operators that use ROLLER as their primary booking system, with every booking created directly in ROLLER. Features of this connection include:
Availability Sync – live availability comes from the operator's ROLLER account.
Bookings Sync – bookings post from Ventrata to ROLLER, and ROLLER issues the tickets or vouchers.
ROLLER'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 ROLLER 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 ROLLER 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 ROLLER.
Press Update Product.
Mapping Products to ROLLER
‼️ IMPORTANT
Mapping tells Ventrata which ROLLER 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 ROLLER product, option and units from the dropdowns, which Ventrata loads from ROLLER. 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 ROLLER account.
Managing the ROLLER Connection
Update the mapping when the operator changes products, options or units in ROLLER.
Replace the key on the operator if ROLLER 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 ROLLER.
Connection Features Detailed
This section is for anyone who wants to know exactly how the ROLLER connection works. Here the direction is the opposite of a reseller connection: Ventrata calls ROLLER, using ROLLER API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks ROLLER for availability whenever someone looks at a backend-connected product, and creates every booking in the operator's ROLLER account. ROLLER doesn't send changes back to Ventrata.
Timings are typical for ROLLER and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's ROLLER 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 ROLLER. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from ROLLER. Ventrata doesn't import product content from ROLLER. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in ROLLER. This works as follows:
What this means for you: customers book against the operator's live ROLLER availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ❌ |
Ventrata doesn't read prices from ROLLER. Ventrata doesn't read prices from ROLLER. Products use the prices you set in Ventrata, and bookings still post to ROLLER. |
Promotions Sync | ❌ |
Promotions aren't sent to ROLLER. Promotions aren't sent to ROLLER. 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 ROLLER account. This works as follows:
‼️ IMPORTANT – Bookings sync one way, from Ventrata to ROLLER. If the operator changes or cancels a booking in ROLLER, 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 ROLLER. Pickup and drop-off details aren't passed to ROLLER. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to ROLLER. Answers to your booking questions aren't passed to ROLLER. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in ROLLER. Extras and add-ons aren't booked in ROLLER. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in ROLLER aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in ROLLER aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with ROLLER. Pass walk-up scanning isn't available with ROLLER. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to ROLLER. Ventrata gift cards aren't passed to ROLLER. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the ROLLER connection
Good to know: limits and details of the ROLLER connection
Live availability: availability comes from ROLLER as people browse.
One-way bookings: changes the operator makes in ROLLER don't reach Ventrata.
Custom API: ROLLER'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 ROLLER. 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 ROLLER. If the issue persists, contact our Technical Support.
Useful Resources
📚 More about Ventrata connections
Partner Information
Roller Networks Pty Ltd
Level 4
101 Moray Street, South Melbourne, VIC 3205, Australia
Ventrata Partner ID: 16ea2b53-a9dd-4034-98f7-b9e4a9226d2c