Skip to main content

Onebox: Operator Backend

Connect Onebox to Ventrata to resell Onebox operators' products with live availability, prices and bookings.

Onebox logo

 

Onebox is a Barcelona-based ticket distribution system for live events and leisure, used by promoters, venues, festivals, theaters, museums, stadiums and theme parks to run sales, dynamic pricing, seat maps, capacity and access control. Customers include Atlético de Madrid and Teatro Apolo, the company reports more than 65 million tickets sold, and its distribution network reaches ticketing operators, travel agencies, hotels and shopping centers across Spain.

 

Connecting Onebox to Ventrata lets you resell products from operators that use Onebox as their booking system. Ventrata reads their live availability and prices from Onebox, and every booking you take is created directly in the operator's Onebox account.

 

To learn more about Onebox, visit oneboxtds.com.

 

📒 NOTE

This connection is coming soon. It's in development. If you'd like to use it, contact our Technical Support or your Ventrata Customer Success Manager.

‼️ IMPORTANT

Mapping tells Ventrata which product to request availability from Onebox. If a backend connected product is not mapped correctly, its bookings will fail. A red highlight across the product row means the product is not mapped correctly.

📒 NOTE

Recreate the products from Onebox in Ventrata, matching the Onebox configuration exactly.

📗 TIP

Only fields marked with an asterisk (*) are required when creating the operator.

 

Primary website

Tags

Booking / Ticketing System

Connection features

Availability Sync · Pricing Sync · Bookings Sync

Developed by

Ventrata (using Onebox Distribution API)

 

This operator connection (also called a backend) lets you resell products from operators that use Onebox as their primary booking system, with every booking created directly in Onebox. Features of this connection include:

  • Availability Sync – live availability comes from the operator's Onebox account.

  • Pricing Sync – prices come from Onebox, or you set prices in Ventrata.

  • Bookings Sync – bookings post from Ventrata to Onebox, and Onebox issues the tickets or vouchers.

 

Onebox'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 Onebox 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 Channel ID and Client Secret for the operator. See the steps below.

  • Recreate the products from Onebox in Ventrata, matching the Onebox configuration exactly.

  • 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: Sign a commercial agreement and request credentials

Sign a commercial agreement with the operator whose products you intend to resell through Onebox.

 

Contact Onebox and request the credentials below.

 

  • Channel ID

  • Client Secret

 

Step 2: Configure the Operator in Ventrata

Contact Onebox and request the Channel ID and the Client Secret.

 

  1. In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.

  2. In the Backend Partner section, select Onebox and enter the Channel ID and Client Secret.

  3. Press Update Operator.

 

 

 

Step 3: Connect Each Product

  1. Open the operator's product in Products → Products and edit it. Check that Operator is set to this operator.

  2. Tick Backend Connected. Tick Backend Availability to use availability from Onebox, and Backend Pricing to use prices from Onebox.

  3. Press Update Product.

📒 NOTE

Onebox sends net prices only. With Backend Pricing ticked, Ventrata records the net price as your cost price and calculates the retail price using the cost percentage set on the operator in the Ventrata Dashboard.

 

Check Backend Connected and keep Backend Availability checked.

 

Check Backend Pricing if you want to inherit pricing from the backend partner.

 

 

Mapping Products to Onebox

‼️ IMPORTANT

Mapping tells Ventrata which Onebox 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.

 

  1. In the Ventrata Dashboard, go to Products → Products and open the product.

  2. Open the Mappings tab. It appears once the product is set to Backend Connected.

  3. For each Ventrata option and unit, select the matching Onebox product, option and units from the dropdowns, which Ventrata loads from Onebox. Don't leave any field empty.

  4. Press Save Changes.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

📗 TIP

Make a test booking after mapping, and ask the operator to confirm it arrived in their Onebox account.

 

Managing the Onebox Connection

  • Update the mapping when the operator changes products, options or units in Onebox.

  • Replace the key on the operator if Onebox 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 Onebox.

 

Connection Features Detailed

This section is for anyone who wants to know exactly how the Onebox connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Onebox, using Onebox Distribution API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.

 

In short: Ventrata asks Onebox for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's Onebox account. Onebox doesn't send changes back to Ventrata.

 

Timings are typical for Onebox and rounded, and they can change.

 

Product Mapping

✅

You map each Ventrata product, option and unit to the operator's Onebox product in the Ventrata Dashboard.

This works as follows:

  • Products – Ventrata reads the operator's Onebox products, options and units to fill the dropdowns on the Mappings tab.

  • Paths seen: GET /catalog-api/v1/events/{n}/sessions, GET /catalog-api/v1/sessions/{n}/availability.

 

What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in Onebox. Ask them to.

Content Sync

❌

Ventrata doesn't import product content from Onebox.

Ventrata doesn't import product content from Onebox. You create and describe the products in Ventrata yourself.

Availability Sync

✅

With Backend Availability on, Ventrata checks the operator's live availability in Onebox.

This works as follows:

  • Availability – when someone uses the availability calendar in Ventrata, for example in the Dashboard, your web checkout or a terminal, Ventrata asks Onebox live for the dates on screen.

  • Syncs live availability from Onebox.

  • Paths seen: GET /catalog-api/v1/sessions/{n}/availability, GET /catalog-api/v1/sessions/{n}/prices.

 

Typically with Onebox:

  • Requests cover 8 days at a time, from today up to about a year ahead, as people browse and as Ventrata loads the calendar.

 

What this means for you: customers book against the operator's live Onebox availability, so you can't oversell a slot the operator has already sold elsewhere.

Pricing Sync

✅

With Backend Pricing on, Ventrata takes prices from Onebox.

This works as follows:

  • Static pricing is synced from Onebox.

  • With Backend Pricing off, the product uses the prices you set in Ventrata, and bookings still post to Onebox.

Onebox sends net prices only. With Backend Pricing ticked, Ventrata records the net price as your cost price and calculates the retail price using the cost percentage set on the operator in the Ventrata Dashboard.

Promotions Sync

❌

Promotions aren't sent to Onebox.

Promotions aren't sent to Onebox. 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 Onebox account.

This works as follows:

  1. Hold and confirm: when the product is added to the cart, Ventrata checks the booking with Onebox, and after payment it creates the booking in the operator's Onebox account with the customer's details.

  2. Tickets: the reference or tickets Onebox returns are stored on the Ventrata booking.

  3. Calls seen: Confirm Booking, Create Booking.

Posts bookings from Ventrata to Onebox. Booking updates and cancellations from Ventrata to Onebox are not supported.

 

‼️ IMPORTANT – Bookings sync one way, from Ventrata to Onebox. If the operator changes or cancels a booking in Onebox, 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 Onebox.

Pickup and drop-off details aren't passed to Onebox. Share them with the operator another way if a product needs them.

Custom Questions Sync

❌

Answers to your booking questions aren't passed to Onebox.

Answers to your booking questions aren't passed to Onebox. Share them with the operator another way if they need them.

Extras Sync

❌

Extras and add-ons aren't booked in Onebox.

Extras and add-ons aren't booked in Onebox. Only the main product, option and units are.

Redemption Sync

❌

Redemptions and other status changes in Onebox aren't sent back to Ventrata after a booking is confirmed.

Redemptions and other status changes in Onebox aren't sent back to Ventrata after a booking is confirmed.

Pass Walkup Scanning Sync

❌

Pass walk-up scanning isn't available with Onebox.

Pass walk-up scanning isn't available with Onebox.

Gift Card Sync

❌

Ventrata gift cards aren't passed to Onebox.

Ventrata gift cards aren't passed to Onebox. Gift card payments stay in Ventrata.

✅ supported · ❌ not supported

 

Good to know: limits and details of the Onebox connection

  • Live availability: availability comes from Onebox as people browse.

  • One-way bookings: changes the operator makes in Onebox don't reach Ventrata.

  • Custom API: Onebox's API isn't OCTO, so some features may be limited compared with OCTO backends.

  • Onebox is a centralized ticket distribution system (TDS) that gives access to live event inventory, pricing and assigned seating maps from multiple venues through a single API gateway.

 

FAQs

I get an error when I save the operator's backend configuration.

The Channel ID and Client Secret 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.

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 dropdowns list what the operator has made available to you in Onebox. Ask the operator. If the issue persists, contact our Technical Support.

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 Onebox. If the issue persists, contact our Technical Support.

 

Useful Resources

 

 

Partner Information

ONEBOX IBERICA, S.L.

Via Augusta 21 - 23

08006 Barcelona, Spain

 

Ventrata Partner ID: 4b72f238-0436-4b6a-ae39-5849d1f7740c

Did this answer your question?