A Ventrata-to-Ventrata connection lets another Ventrata client, such as a sightseeing or tour operator that also uses Ventrata, resell your products. Your availability, pricing and bookings sync between the two Ventrata accounts in real time.
This article is for the supplier, the account that owns the products. If you're the account reselling another Ventrata client's products, see Ventrata: Operator Backend.
Connection type | Ventrata-to-Ventrata (both accounts run on Ventrata) |
Tags | Operator Reselling Others · Booking / Ticketing System |
Connection features | Product Mapping · Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync · Custom Questions Sync |
Developed by |
Both accounts take part in the setup:
Supplier account (owns the products) | Creates the reseller in Ventrata and a Ventrata Reseller Connection for them, then securely shares the connection's API key. See Ventrata: Reseller Connection. |
Reseller account (sells the products) | Creates the supplier as an Operator with the Backend Partner Ventrata (Operator Backend), pastes the API key, then connects and maps each product. See Ventrata: Operator Backend. |
📗 TIP
You can use a Ventrata-to-Ventrata connection to work with another Ventrata client, or to resell products within your own account across your destinations.
Ventrata Clients You Can Connect With
Ventrata is not a reseller.
Ventrata is the platform both accounts run on. Your commercial relationship is always with the individual Ventrata client reselling your products, never with Ventrata itself, and each of those clients needs its own reseller record in your account and its own connection.
Don't create a connection to Ventrata itself. Create a Ventrata Reseller Connection for the client you have an agreement with.
The following Ventrata clients are listed in our Partner Gallery as resellers. Follow the article for the client you have an agreement with to set up your connection:
You can also connect with any other Ventrata client that isn't listed above, or across your own destinations. No certification is needed, because both accounts already run on Ventrata. Follow the steps below.
Creating the Ventrata Reseller Connection
🔐 Required Role Permissions: See Connections, Modify Connections
Before you begin:
The reseller has its own Ventrata account.
You have a commercial agreement with the reseller for them to sell your products.
The reseller is created as a Reseller in your Ventrata account, with retail and wholesale/commission pricing set up.
In the Ventrata dashboard, go to Connections > Connections.
Connections - Connections
Press the + New Connection button.
New Connection
Search for the 'Ventrata Reseller Connection'.
Press the + NEW CONNECTION button.
Ventrata Reseller Connection
Enter a name for the connection.
Create New Connection
📒 NOTE
You can limit the reseller's access to specific destinations or products by allowing or disallowing them in their respective fields.
In the 'Reseller' field, start typing the reseller's name and select it from the list.
Reseller Connection
Check the 'Override Wholesale' box to use the wholesale price sent from the reseller via API instead of what is configured locally.
Override Wholesale
Press the Create Connection button.
Create Connection
Press the
eye icon to reveal the API key (shown after creating the connection), then copy it.
Reseller Connection API Key
Securely share the API key with the reseller. They paste it as the OCTO API Key when they set you up as an operator. See Ventrata: Operator Backend.
What the Reseller Does Next
Once they have the API key, the reseller completes the setup in its own account:
Creates you as an Operator, with the Backend Partner Ventrata (Operator Backend), and pastes the API key as the OCTO API Key.
Recreates your products in its account and assigns you as the operator, with Backend Connected ticked.
Maps each product, option and unit to yours on the product's Mappings tab.
The steps are in Ventrata: Operator Backend.
Testing the Connection
Ask the reseller to make a test booking. Then check that the booking appears in your bookings table.
Scanning the Reseller's Tickets
Once the reseller has used the connection, its Ventrata API key appears on your Ventrata Reseller Connection. Your staff can then look up tickets the reseller issued, by reference, email or mobile number, and redeem them at your venue. The ticket is redeemed in the reseller's account and the booking is created in yours.
📒 NOTE
For redemption to work, map each of the reseller's products, options and units to yours on the connection. Unmapped units fail with Product not mapped.
Connection Features Detailed
This section is for anyone who wants the detail. Click a row to see how each feature works.
Product Mapping | ✅ |
The reseller maps its products to yours in its own Ventrata account. On each backend-connected product, the reseller opens the Mappings tab and picks the matching product, option and units from the supplier's account. Products that aren't mapped correctly are highlighted in red, and bookings for them fail. |
Content Sync | ❌ |
Product content isn't copied between accounts. The reseller recreates each product in its own account: ticket types, options and opening hours, plus fares, tour times and tour groups unless it uses Backend Pricing and Backend Availability. |
Availability Sync | ✅ |
The reseller reads live availability from the supplier's account. With Backend Availability ticked on the reseller's product, availability comes live from the supplier's account through OCTO availability checks. Without it, the product uses the availability set in the reseller's account but still sends bookings to the supplier. |
Pricing Sync | ✅ |
Optional: the reseller can inherit the supplier's pricing. With Backend Pricing ticked, the reseller's product uses the supplier's prices. Without it, the reseller sets its own prices in its account. On the supplier side, ticking Override Wholesale on the Ventrata Reseller Connection uses the wholesale price sent by the reseller over the API instead of the one configured on the reseller in the supplier's account. |
Promotions Sync | ❌ |
Promotions aren't shared between accounts. Promotions set up in the supplier's account don't carry over to the reseller's products. Each account sets up its own. |
Bookings Sync | ✅ | |
Pickups/Dropoff Sync | ✅ |
Pickup details are passed to the supplier with the booking. Pickup requests and the selected pickup point are sent with the booking. |
Custom Questions Sync | ✅ |
Answers to booking questions are sent with the booking. Questions set up on the supplier's product are answered on the reseller's side and passed through with the booking. |
Extras Sync | ❌ |
Not listed as a supported feature of this connection. If you need extras on a Ventrata-to-Ventrata connection, contact our Technical Support. |
Redemption Sync | ✅ / ❌ |
Limited: the supplier can scan the reseller's tickets once the connection is in use. After the reseller has used the connection, the supplier's staff can look up and redeem tickets issued by the reseller's account. See Scanning the Reseller's Tickets in Ventrata: Reseller Connection. |
Pass Walkup Scanning Sync | ❌ |
Not part of this connection. Walk-up pass scanning is used by pass programs such as Go City and CityPASS, not by Ventrata-to-Ventrata connections. |
Gift Card Sync | ❌ |
Not part of this connection. Gift cards from one Ventrata account can't be used in the other. |
✅ supported · ✅ / ❌ limited · ❌ not supported
Troubleshooting
The reseller can't see some of my products.
The reseller can't see some of my products.
Check which destinations, products and options are allowed on the reseller and on the connection. Then check that the products and options are enabled for sale on the Direct API source.
Redemption fails with "Product not mapped".
Redemption fails with "Product not mapped".
The reseller's product, option or unit isn't mapped to yours on the connection. Map it, then scan the ticket again.
Redemption fails with "Redemption succeeded but the booking was not received, please try again".
Redemption fails with "Redemption succeeded but the booking was not received, please try again".
The ticket was redeemed in the reseller's account, but the booking didn't reach yours in time. Scan the ticket again. A ticket that's already redeemed returns the existing redemption, so it isn't redeemed twice.
Redemption fails with "Multiple bookings returned, scan individual tickets instead".
Redemption fails with "Multiple bookings returned, scan individual tickets instead".
The lookup found more than one booking. Scan each ticket on its own instead of looking up by email or mobile number.
Bookings from the reseller don't arrive.
Bookings from the reseller don't arrive.
Check that the reseller used the API key from this connection, and that their products are backend-connected and mapped. If the issue persists, contact our Technical Support.
FAQs
Can I use this within my own Ventrata account?
Can I use this within my own Ventrata account?
Yes. You can use a Ventrata-to-Ventrata connection to resell products across your own destinations, as well as with another Ventrata client.
What does Override Wholesale do?
What does Override Wholesale do?
When ticked, the connection uses the wholesale price sent by the reseller over the API instead of the wholesale price configured on the reseller in your account.
Can I limit what the reseller can sell?
Can I limit what the reseller can sell?
Yes. Allow or disallow destinations and products on the connection, on top of the settings on the reseller.
Is this the right connection for any partner that uses Ventrata?
Is this the right connection for any partner that uses Ventrata?
Only use this connection type when connecting to another Ventrata client. For other resellers, use the connection described in their own article.
📚 More about Ventrata connections
Partner Information
Ventrata Ltd
55 Baker Street, London
United Kingdom, W1U 7EU
Ventrata Partner ID: a6a2a406-088a-4466-b87c-7fcc17770b71