RocketRez is a ticketing, point-of-sale and revenue platform for attractions and tour venues, spanning reservations, retail, food and beverage, memberships, dynamic pricing, photo sales and AI-assisted guest messaging. Its customer base leans toward zoos, aquariums, theme and water parks, observation towers, boat tours, scenic railways and wildlife parks, concentrated in North America.
Connecting RocketRez to Ventrata lets you resell products from operators that use RocketRez as their booking system. Ventrata reads their live availability from RocketRez, and every booking you take is created directly in the operator's RocketRez account.
To learn more about RocketRez, visit rocketrez.com.
‼️ IMPORTANT
The RocketBooking API used for this connection is a custom API that does not follow the OCTO API standard, which may limit certain functionality and capabilities.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Bookings Sync |
Developed by | Ventrata (using RocketBooking API) |
This operator connection (also called a backend) lets you resell products from operators that use RocketRez as their primary booking system, with every booking created directly in RocketRez. Features of this connection include:
Availability Sync – live availability comes from the operator's RocketRez account.
Bookings Sync – bookings post from Ventrata to RocketRez, and RocketRez issues the tickets or vouchers.
RocketRez'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 RocketRez 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 Supplier ID, Reseller ID and 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
Your operator asks the RocketRez team ([email protected]) for them, because the operator cannot see these credentials in the RocketRez interface.
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 RocketRez and enter the Supplier ID, Reseller ID and API Key.
Enter the Supplier ID: an alphanumeric string, with or without hyphens, that identifies your operator in RocketRez (example 123e4567-e89b-12d3-a456-426614174000).
Enter the Reseller ID: an alphanumeric string without hyphens that identifies you as a reseller in the operator's RocketRez system (example AaBbCc1234567890XxYyZz0987654321).
Enter the API Key: a security token, typically 20-40 alphanumeric characters.
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 RocketRez.
Press Update Product.
📒 NOTE
RocketRez sends both retail and net prices. With Backend Pricing ticked, Ventrata records the retail price as your selling price and the net price as your cost price, whatever cost percentage is set on the operator.
Check Backend Connected to use the API connection. To pull availability from RocketRez, also check Backend Availability.
There is no Backend Pricing option for RocketRez; the API does not support pricing.
Mapping Products to RocketRez
‼️ IMPORTANT
Mapping tells Ventrata which RocketRez 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 RocketRez product, option and units from the dropdowns, which Ventrata loads from RocketRez. 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 RocketRez account.
Managing the RocketRez Connection
Update the mapping when the operator changes products, options or units in RocketRez.
Replace the key on the operator if RocketRez 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 RocketRez.
Connection Features Detailed
This section is for anyone who wants to know exactly how the RocketRez connection works. Here the direction is the opposite of a reseller connection: Ventrata calls RocketRez, using RocketBooking API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks RocketRez for availability whenever someone looks at a backend-connected product, and creates every booking in the operator's RocketRez account. RocketRez doesn't send changes back to Ventrata.
Timings are typical for RocketRez and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's RocketRez 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 RocketRez. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from RocketRez. Ventrata doesn't import product content from RocketRez. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in RocketRez. This works as follows:
What this means for you: customers book against the operator's live RocketRez availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ❌ |
Ventrata doesn't read prices from RocketRez. Ventrata doesn't read prices from RocketRez. Products use the prices you set in Ventrata, and bookings still post to RocketRez. RocketRez sends both retail and net prices. With Backend Pricing ticked, Ventrata records the retail price as your selling price and the net price as your cost price, whatever cost percentage is set on the operator. |
Promotions Sync | ❌ |
Promotions aren't sent to RocketRez. Promotions aren't sent to RocketRez. 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 RocketRez account. This works as follows:
Reserve: when a product is added to the cart, Ventrata requests a reservation of the availability. Confirm: after payment, Ventrata confirms the booking with the customer contact information. The barcodes from RocketRez are ingested as ticket (per person) barcodes in Ventrata, and the RocketRez booking reference is recorded as Supplier Reference. Update: RocketRez cannot update a booking directly via API, so a change reserves and confirms a new booking, then cancels the previous one. Cancel: Ventrata sends a cancellation request to RocketRez.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to RocketRez. If the operator changes or cancels a booking in RocketRez, 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 RocketRez. Pickup and drop-off details aren't passed to RocketRez. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to RocketRez. Answers to your booking questions aren't passed to RocketRez. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in RocketRez. Extras and add-ons aren't booked in RocketRez. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in RocketRez aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in RocketRez aren't sent back to Ventrata after a booking is confirmed. Not supported. Booking status from RocketRez (for example Redeemed) is not communicated back to Ventrata after confirmation. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with RocketRez. Pass walk-up scanning isn't available with RocketRez. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to RocketRez. Ventrata gift cards aren't passed to RocketRez. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the RocketRez connection
Good to know: limits and details of the RocketRez connection
Live availability: availability comes from RocketRez as people browse.
One-way bookings: changes the operator makes in RocketRez don't reach Ventrata.
Custom API: RocketRez's API isn't OCTO, so some features may be limited compared with OCTO backends.
Vouchers/tickets issued by RocketRez are received and issued to customers.
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 Supplier ID, Reseller ID and 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 RocketRez. 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 RocketRez. If the issue persists, contact our Technical Support.
Error when updating operator to save backend configuration.
Error when updating operator to save backend configuration.
The RocketRez API credentials are likely not valid. Double-check them with your operator or RocketRez. If the issue persists, contact support.
The product/option/unit I want to map is not on the dropdown.
The product/option/unit I want to map is not on the dropdown.
The dropdown is pulled from RocketRez based on the products, options and units made available to you. Double-check with your operator and RocketRez. If the issue persists, contact support.
Useful Resources
📚 More about Ventrata connections
Partner Information
Rocketrez Inc.
40 North Gate Drive
Steinbach, MB R5G 2T9, Canada
Ventrata Partner ID: 275b1590-a47d-456e-8e2a-8177dca254e0