Outbox is a Montréal-based cloud ticketing platform for live events and venues, sold white-label with digital tickets and wallet, general admission and reserved seating, 3D seat maps, inventory and distribution control and a full API, in multiple languages and currencies. The company reports more than 500 million tickets sold for clients including Bell Centre, Cirque du Soleil, Osheaga, The O2 and venues across Canada, the US, the UK and Mexico.
Connecting Outbox to Ventrata lets you resell products from operators that use Outbox as their booking system. Ventrata reads their live availability and prices from Outbox, and every booking you take is created directly in the operator's Outbox account.
To learn more about Outbox, visit outbox.com.
‼️ IMPORTANT
Outbox's external API used for this connection is a custom XML-RPC API that does not follow the OCTO API standard, which may limit certain functionality and capabilities.
‼️ IMPORTANT
Because Outbox sells timed-entry seats, always use Backend Availability. Without it, bookings can be made for time slots that do not exist or are sold out in Outbox and will fail.
📗 TIP
Make a test booking after mapping and ask the operator to confirm it arrived in Outbox with the correct time slot and ticket types.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using Outbox Partner Sell API) |
This operator connection (also called a backend) lets you resell products from operators that use Outbox as their primary booking system, with every booking created directly in Outbox. Features of this connection include:
Availability Sync – live availability comes from the operator's Outbox account.
Pricing Sync – prices come from Outbox, or you set prices in Ventrata.
Bookings Sync – bookings post from Ventrata to Outbox, and Outbox issues the tickets or vouchers.
Outbox'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 Outbox 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 and API URL for the operator. See the steps below.
Make sure you receive production credentials: staging and production use different URLs and keys, and production inventory is set up separately from staging.
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 requests a new API channel for you from their Outbox account manager, who also sets up the onsales and inventory you may sell. Outbox issues the credentials.
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 Outbox and enter the API Key and API URL.
Enter the API Key: it identifies you as a sales channel (reseller) in the operator's Outbox system and controls which onsales (products) and which currency are available to you. Each reseller needs its own key; keys cannot be shared between companies.
Enter the API URL: the address of the operator's Outbox API, usually on the operator's ticketing domain and ending in /extapi/ (for example https://tickets.onetimessquare.com/extapi/). It must start with https://.
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 Outbox, and Backend Pricing to use prices from Outbox.
Press Update Product.
📒 NOTE
Outbox sends retail prices only. With Backend Pricing ticked, Ventrata records the retail price and calculates your net (cost) price using the cost percentage set on the operator in the Ventrata Dashboard.
Check Backend Connected, then Backend Availability to pull time slots and availability and Backend Pricing to pull pricing.
Mapping Products to Outbox
‼️ IMPORTANT
Mapping tells Ventrata which Outbox 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 Outbox product, option and units from the dropdowns, which Ventrata loads from Outbox. 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 Outbox account.
Managing the Outbox Connection
Update the mapping when the operator changes products, options or units in Outbox.
Replace the key on the operator if Outbox 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 Outbox.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Outbox connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Outbox, using Outbox Partner Sell API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks Outbox for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's Outbox account. Outbox doesn't send changes back to Ventrata.
Timings are typical for Outbox and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's Outbox 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 Outbox. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from Outbox. Ventrata doesn't import product content from Outbox. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in Outbox. This works as follows:
What this means for you: customers book against the operator's live Outbox availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from Outbox. This works as follows:
Outbox sends retail prices only. With Backend Pricing ticked, Ventrata records the retail price and calculates your net (cost) price using the cost percentage set on the operator in the Ventrata Dashboard. |
Promotions Sync | ❌ |
Promotions aren't sent to Outbox. Promotions aren't sent to Outbox. 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 Outbox account. This works as follows:
Reserve: seats are locked in Outbox for the hold period Outbox returns when a product is added to the cart; each Outbox order covers a single time slot. Confirm: after payment, with customer contact details; first name, last name, email and country are required, phone and postal code are passed when available, and customer language is set to French or English from their locale. The Outbox order number is recorded as Supplier Reference. Tickets: a barcode per seat is issued as a QR code on each Ventrata ticket, plus a PDF with all tickets for the order; QR values match the Outbox PDF. Update: Outbox cannot change an existing order via API, so updating a confirmed booking only reissues its tickets; to change the date, time slot or ticket count, cancel and rebook. Cancel: cancelling a confirmed booking cancels the Outbox order; cancelling an unconfirmed (on hold) booking releases the locked seats.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Outbox. If the operator changes or cancels a booking in Outbox, 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 Outbox. Pickup and drop-off details aren't passed to Outbox. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Outbox. Answers to your booking questions aren't passed to Outbox. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Outbox. Extras and add-ons aren't booked in Outbox. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Outbox aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in Outbox aren't sent back to Ventrata after a booking is confirmed. Not supported. Booking status from Outbox (for example a ticket scanned) is not communicated back to Ventrata. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Outbox. Pass walk-up scanning isn't available with Outbox. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Outbox. Ventrata gift cards aren't passed to Outbox. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Outbox connection
Good to know: limits and details of the Outbox connection
Live availability: availability comes from Outbox as people browse.
One-way bookings: changes the operator makes in Outbox don't reach Ventrata.
Custom API: Outbox's API isn't OCTO, so some features may be limited compared with OCTO backends.
Tickets: QR codes and PDF tickets from Outbox are issued to your 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 API Key and API URL 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 Outbox. 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 Outbox. If the issue persists, contact our Technical Support.
Error when updating the operator to save the backend configuration.
Error when updating the operator to save the backend configuration.
The API Key or API URL is likely incorrect, or test credentials were used with a production URL (or the other way round). Double-check with your operator. If the issue persists, contact support.
The product/option/unit I want to map is not in the dropdown, or the dropdown is empty.
The product/option/unit I want to map is not in the dropdown, or the dropdown is empty.
The dropdown is pulled from Outbox based on the onsales assigned to your API Key. Ask your operator to confirm with Outbox that inventory is set up for your API channel in the environment you are using (staging and production are configured separately). If the issue persists, contact support.
Products, options or units appear as "Undefined" in the mapping dropdowns.
Products, options or units appear as "Undefined" in the mapping dropdowns.
The names come from the operator's onsale setup in Outbox. Ask your operator to add titles and price type descriptions in Outbox.
Booking confirmation fails with "Country code is required".
Booking confirmation fails with "Country code is required".
Outbox requires a country on every order. Make sure the checkout, booking form or reseller connection selling this product collects the customer's country, then retry.
Prices differ from what the operator expects.
Prices differ from what the operator expects.
Outbox returns tax-inclusive prices that include service charges for your channel. Check the price tables and service charges for your API channel with your operator.
No time slots are shown for a date.
No time slots are shown for a date.
The operator has no event or no seats released for that date in Outbox. Check with your operator.
Useful Resources
📚 More about Ventrata connections
Partner Information
Outbox Technology Inc.
3575 Boulevard Saint-Laurent, Suite 705
Montreal, QC H2X 2T7, Canada
Ventrata Partner ID: 01a06240-f33b-7362-b04f-35ed782cee0e