Otipass is a French platform for digitizing territorial passes, powering tourist, cultural, youth and citizen cards for more than forty cities and regions including Lyon, Toulouse, Bordeaux, Nantes, Helsinki and Matera, sold to tourist offices and municipalities. For operators, it brings holders of official city and regional passes who have prepaid a bundle of entries and pick venues once in the destination, with museums, monuments and local attractions the core content.
Connecting OTIPASS to Ventrata lets you scan, validate and redeem OTIPASS passes at your entrance, on Ventrata-powered turnstiles, kiosks, point-of-sale terminals, the mobile app or the Ventrata Dashboard, without a separate OTIPASS app.
To learn more about OTIPASS, visit otipass.com.
Primary website | |
Tags | Multi-Attraction Pass |
Connection type | Pass redemption: you scan OTIPASS passes at your entrance |
Connection features | Product Mapping · Redemption Sync · Pass Walkup Scanning Sync |
Developed by | Ventrata (using Otipass API) |
This connection lets you:
Scan or type an OTIPASS pass number in Ventrata and check it with OTIPASS in real time for your service.
Create a booking in Ventrata automatically for every valid pass.
Record the entry with OTIPASS at the moment you scan.
How It Works
Staff scan or type a pass number.
If the pass already has an active booking, Ventrata returns it.
Otherwise Ventrata sends a query entry to OTIPASS for your service (ID Service) to check the pass.
If the pass is valid, Ventrata sends a record entry to OTIPASS.
If OTIPASS confirms, Ventrata saves an open-dated booking for 1 unit of the product, option and unit mapped to the connection.
📒 NOTE
Any non-blank code is checked with OTIPASS; there is no format filter.
Creating the OTIPASS Connection
🔐 Required Role Permissions: See Connections, Modify Connections
Before you begin:
Have your OTIPASS ID, OTIPASS Api Key and OTIPASS ID Service ready.
Create OTIPASS as a reseller in Ventrata and select it on the connection. The form marks Reseller as optional, but lookups need it.
Plan one connection per OTIPASS service you accept.
Create the connection
Select your OTIPASS reseller.
Enter the OTIPASS ID, Api Key and ID Service.
Save. Ventrata checks the credentials and creates a single mapping row for the service.
The connection form has these options:
Reseller | The reseller that OTIPASS bookings are recorded under. Optional in the form, but needed in practice for lookups. |
OTIPASS ID / OTIPASS Api Key | Required. Checked on every save with a test query to OTIPASS; if it fails, the OTIPASS message is shown and all three fields are flagged invalid. |
OTIPASS ID Service | Required. The one OTIPASS service this connection checks and redeems passes for. It also becomes the title of the connection's single mapping row. |
Mapping Products
Each connection has exactly one mapping row, created or updated on every save.
Open the connection and select the mapping row.
Choose the Ventrata product, option and unit to book. Option and unit are required.
📒 NOTE
To accept several OTIPASS services, create one connection per service.
📒 NOTE
Until the row is mapped, scans fail with " is not mapped in ".
Redemption
Immediately: Always. Ventrata records the entry with OTIPASS at scan time; the booking is saved only if OTIPASS confirms.
On redemption or no-show: Not supported.
What's sent to OTIPASS: A record entry for the pass and service, with the date in Europe/Paris local time.
Connection Features Detailed
This section is for anyone who wants the detail. Click a row to see how each feature works.
Product Mapping | ✅ |
You map each OTIPASS pass listing to a Ventrata product in the Ventrata Dashboard. Each connection has exactly one mapping row, created or updated on every save. To accept several OTIPASS services, create one connection per service. Until the row is mapped, scans fail with " is not mapped in ". |
Content Sync | ❌ |
Product content isn't synced. OTIPASS sells its own pass. Your products and their content stay in Ventrata. |
Availability Sync | ❌ |
Your availability isn't shared with OTIPASS. There is no availability or capacity exchange with OTIPASS. |
Pricing Sync | ❌ |
Prices aren't synced with OTIPASS. The booking uses your Ventrata unit price and is settled by voucher. No price is sent to OTIPASS. |
Promotions Sync | ❌ |
Promotions don't apply to OTIPASS passes. Your Ventrata promotions don't apply to bookings made by scanning a pass. |
Bookings Sync | ✅ / ❌ |
Limited: bookings are created only when a pass is scanned. One open-dated booking per pass, with quantity 1 of the mapped unit, created at scan time. There is no cancel call to OTIPASS. |
Pickups/Dropoff Sync | ❌ |
Not part of this connection. Pass redemptions don't carry pickups. |
Custom Questions Sync | ❌ |
Not part of this connection. Booking questions aren't asked or sent for pass redemptions. |
Extras Sync | ❌ |
Not part of this connection. Extras can't be added to a pass redemption. |
Redemption Sync | ✅ |
Redemptions are sent to OTIPASS. Always. Ventrata records the entry with OTIPASS at scan time; the booking is saved only if OTIPASS confirms. Not supported. A record entry for the pass and service, with the date in Europe/Paris local time. |
Pass Walkup Scanning Sync | ✅ |
You scan OTIPASS passes at your entrance. Staff scan or type a pass number. If the pass already has an active booking, Ventrata returns it. Otherwise Ventrata sends a query entry to OTIPASS for your service (ID Service) to check the pass. |
Gift Card Sync | ❌ |
Not part of this connection. OTIPASS passes aren't Ventrata gift cards. |
✅ supported · ✅ / ❌ limited · ❌ not supported
Good to know: limits of this connection
Good to know: limits of this connection
One OTIPASS service per connection, mapped to one product, option and unit.
Adult and child passes can't be told apart within one service.
Every non-blank code scanned may be sent to OTIPASS, including codes meant for other connections.
Redemption can't be deferred to admission or no-show.
No pickups, extras, custom questions or resources.
Lookup results are cached for 5 minutes, and a timeout is treated as not found.
Troubleshooting
"%{title} is not mapped in %{connection}"
"%{title} is not mapped in %{connection}"
The connection's ID Service row has no Ventrata product, option and unit mapped. Map the row on the connection, then scan again.
"Redemption not allowed"
"Redemption not allowed"
FAQs
How do I accept passes for more than one OTIPASS service?
How do I accept passes for more than one OTIPASS service?
Create a separate connection for each OTIPASS ID Service and map each one to its own product, option and unit.
Useful Resources
📚 More about Ventrata connections
Partner Information
OTIPASS SAS
8 rue du 45e Regiment de Transmissions, batiment Le Septan, entree A, 26200 Montelimar
France
Ventrata Partner ID: 55b217b2-35ea-454c-ac15-4630ef1cd0b9