Clorian is a Barcelona-based ticketing platform for museums, monuments and cultural venues, handling online and on-site sales, timed-entry capacity and access control for sites including the Sagrada Família, La Pedrera and the Mezquita-Catedral de Córdoba. It reports more than 28 million tickets a year sold through its venues and a reseller network of more than 14,000.
Connecting Clorian to Ventrata lets you resell products from operators that use Clorian as their booking system. Ventrata reads their live availability and prices from Clorian, and every booking you take is created directly in the operator's Clorian account.
To learn more about Clorian, visit clorian.com.
📒 NOTE
If your product inventory needs both payment methods (Deferred Payment and Pre-payment), create two separate operators in Ventrata to handle payments correctly.
‼️ IMPORTANT
Mapping tells Ventrata which Clorian product to request availability for. If Backend Connected products are not mapped correctly, bookings of the product will fail. A red highlight across the product row means the product is not correctly mapped.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using Clorian B2B API) |
This operator connection (also called a backend) lets you resell products from operators that use Clorian as their primary booking system, with every booking created directly in Clorian. Features of this connection include:
Availability Sync – live availability comes from the operator's Clorian account.
Pricing Sync – prices come from Clorian, or you set prices in Ventrata.
Bookings Sync – bookings post from Ventrata to Clorian, and Clorian issues the tickets or vouchers.
Clorian'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 Clorian 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, Username and Password for the operator. See the steps below.
A commercial agreement with the operator whose products you want to resell through Clorian.
The Clorian products recreated in Ventrata, matching the Clorian 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: Get your Clorian credentials
Contact Clorian and request your API Key and your Clorian Username and Password.
API Key
Username
Password
Step 2: Configure the Operator in Ventrata
Contact Clorian and request your API Key plus your Clorian Username and Password.
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 Clorian and enter the API Key, Username and Password.
In the Backend Partner field, select Clorian.
Enter the API Key, Username and Password you received from Clorian (required).
Optional: choose the payment method for your products: Deferred Payment (Clorian default, invoiced later) or Pre-payment (deposit).
Press Create Operator.
Press Update Operator.
Step 3: 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 Clorian, and Backend Pricing to use prices from Clorian.
Press Update Product.
📒 NOTE
Clorian 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.
On the product, check Backend Connected and keep Backend Availability checked.
Check Backend Pricing if you want to inherit pricing from Clorian.
Click Update Product.
Mapping Products to Clorian
‼️ IMPORTANT
Mapping tells Ventrata which Clorian 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 Clorian product, option and units from the dropdowns, which Ventrata loads from Clorian. 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 Clorian account.
Managing the Clorian Connection
Update the mapping when the operator changes products, options or units in Clorian.
Replace the key on the operator if Clorian 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 Clorian.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Clorian connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Clorian, using Clorian B2B API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks Clorian for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's Clorian account. Clorian doesn't send changes back to Ventrata.
Timings are typical for Clorian and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's Clorian 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 Clorian. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from Clorian. Ventrata doesn't import product content from Clorian. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in Clorian. This works as follows:
What this means for you: customers book against the operator's live Clorian availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from Clorian. This works as follows:
Clorian 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 Clorian. Promotions aren't sent to Clorian. Your Ventrata promotions still apply to the price your customer pays in Ventrata. Not supported: products with promotions, including promotions via API. |
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's Clorian account. This works as follows:
Bookings and cancellations are posted from Ventrata to Clorian. Booking updates from Ventrata to Clorian are not supported.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Clorian. If the operator changes or cancels a booking in Clorian, 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 Clorian. Pickup and drop-off details aren't passed to Clorian. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Clorian. Answers to your booking questions aren't passed to Clorian. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Clorian. Extras and add-ons aren't booked in Clorian. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Clorian aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in Clorian aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Clorian. Pass walk-up scanning isn't available with Clorian. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Clorian. Ventrata gift cards aren't passed to Clorian. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Clorian connection
Good to know: limits and details of the Clorian connection
Live availability: availability comes from Clorian as people browse.
One-way bookings: changes the operator makes in Clorian don't reach Ventrata.
Custom API: Clorian's API isn't OCTO, so some features may be limited compared with OCTO backends.
Clorian is a ticketing platform for major cultural sites and venues, handling over 32 million tickets annually with a network of over 14,000 distributors.
Payment method per operator: Deferred Payment (default by Clorian) or Pre-payment (deposit).
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, Username and Password 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 Clorian. 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 Clorian. If the issue persists, contact our Technical Support.
Useful Resources
📚 More about Ventrata connections
Partner Information
Tiqueteo Spain, S.L.
Carrer de Veneçuela, 103, 1, Sant Martí
08019 Barcelona, Spain
Ventrata Partner ID: b4dc43c9-5155-4d6c-8861-a73a83fce30d