Frekuent is a Barcelona-based self-service ticketing company, formerly Orain, selling through unattended points such as kiosks at bus stops, devices on board vehicles and terminals at transport hubs, with more than 10,000 installed systems and over 2.5 million users in vending, fuel and unattended retail. For operators, it brings walk-up, in-destination demand captured at the point of interest instead of through search or advance planning.

Connecting Frekuent to Ventrata will push your product content, sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Frekuent, visit frekuent.com.

Primary website	frekuent.com
Tags	Reseller System · Offline & Retail Channel
Destination markets	🇪🇸 Spain
Source markets	🌎 Global
Specialties	Unattended kiosk and on-board self-service ticket sales
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Content Sync
Developed by	Frekuent (using Ventrata's OCTO API)

This reseller connection lets you sell your products through Frekuent without managing availability, pricing and bookings by hand. Features of this connection include:

Availability Sync – Frekuent checks your live availability in Ventrata.
Pricing Sync – Frekuent gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Frekuent are created in Ventrata instantly, and customers get Ventrata tickets.
Content Sync – Frekuent uses your product content from Ventrata.

Creating the Frekuent Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

You must have a commercial agreement with Frekuent for them to sell your products. To inquire about partnering with them, contact them via frekuent.com. To start one, contact Javier Gumà, Partnership Manager at Frekuent ([email protected]).
You must have Frekuent created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Frekuent from the list of partners.
Select Frekuent Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Frekuent connections and would like to differentiate between them more easily in the future.
Press the Create Octo Connection button.

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

Mapping Products to Frekuent

Securely share the OCTO API key shown on the connection you've created with your Frekuent contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Frekuent team to complete this.

Your Ventrata configuration is complete. You do not need to take any further steps.

📗 TIP

Frekuent can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

Managing the Frekuent Connection

Allow or disallow products: limit which destinations, products and options Frekuent can access. See how to allow or disallow products.
Rename the connection to tell several Frekuent connections apart.

Connection Features Detailed

This section is for anyone who wants to know exactly how the Frekuent connection works: which Ventrata OCTO API calls Frekuent makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Frekuent pulls everything it needs from Ventrata. It reads your products, checks your availability and prices, and sends bookings and cancellations. Ventrata doesn't push changes to Frekuent, so anything you change in Ventrata reaches Frekuent the next time it checks.

Timings are typical for Frekuent and rounded, and they can change if Frekuent changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Frekuent maps them on its side, through your account manager or Frekuent's portal. This works as follows: Get Products (`GET /products`) – when Frekuent sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child). Get Product (`GET /products/{productId}`) – Frekuent re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Frekuent's side – Frekuent links each Ventrata option and unit to its own listing and ticket types. Your Frekuent account manager does this for you, or you do it in Frekuent's own portal if Frekuent offers one. You only share the connection's API key. Typically with Frekuent: Frekuent reads your full product list about every 12 hours. It re-reads each product about every 20 minutes. What this means for you: Frekuent can only sell what it has mapped. When you add a product, option or unit in Ventrata, Frekuent may see it on its next refresh, but it won't sell it until it's mapped. So tell your Frekuent account manager whenever you add one.
Content Sync	✅	Frekuent can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Frekuent adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach Frekuent on its next product refresh. Typically with Frekuent: Frekuent requests `octo/content`.
Availability Sync	✅	Frekuent checks your live availability in Ventrata. Ventrata doesn't push availability changes to Frekuent. This works as follows: Availability Check (`POST /availability`) – Frekuent sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (`AVAILABLE`, `LIMITED`, `SOLD_OUT`, `CLOSED` or `FREESALE`), the remaining vacancies, the booking cutoff and an `availabilityId`, which Frekuent needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Frekuent can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Frekuent: Availability Check: Frekuent checks your products throughout the day, usually starting 2 days ahead and covering a single day per request, looks up to about 2 months ahead and re-checks the same product and dates about every 16 hours. Availability Calendar: Frekuent checks your products throughout the day, usually starting today and covering about 7 months per request, looks up to about 7 months ahead and re-checks the same product and dates about every 6 hours. Checks are busiest between 11:00 and 17:00 UTC, which suggests most checks are live, as customers browse Frekuent. What this means for you: when you close a date, change capacity or sell out in Ventrata, Frekuent shows it after its next check. For dates it checks regularly, that's within about 6 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Frekuent asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Frekuent asks for prices by adding `octo/pricing` to the `Octo-Capabilities` header of its requests. Without it, Ventrata sends availability with no prices at all. Availability Check (`POST /availability`) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Frekuent, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Frekuent also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing. Booking Reservation (`POST /bookings`) and Booking Confirmation (`POST /bookings/{uuid}/confirm`) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at. Typically with Frekuent: Frekuent requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Frekuent sends the number of people per unit type, so group prices are calculated for the actual booking. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Frekuent to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Frekuent's portal. Otherwise it may be off, and Frekuent won't receive your Ventrata prices. 📗 TIP – If prices on Frekuent look wrong, check the Frekuent reseller's pricing in Ventrata first: that's what Frekuent reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on Frekuent. Prices on Frekuent don't include promotions you create in Ventrata. Set up any promotions with Frekuent directly.
Bookings Sync	✅	Bookings, changes and cancellations made on Frekuent are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Frekuent, Frekuent sends the product, option, chosen slot (`availabilityId`) and one unit item per person. Ventrata checks capacity again and creates an `ON_HOLD` booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Frekuent confirms the hold, with its own booking reference and the customer's contact details. The booking becomes `CONFIRMED` in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Frekuent gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Frekuent never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Frekuent, Frekuent cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Frekuent has to contact you. Change: Booking Update (`PATCH /bookings/{uuid}`) – Frekuent changes existing bookings in place, for example a new date, time or number of people. Typically with Frekuent: Frekuent doesn't set a hold time, so the default hold time applies. A typical Frekuent booking is for about 6 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. Frekuent also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about every 4 hours, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Frekuent to Ventrata. If you cancel, change or rebook a booking from Frekuent in Ventrata, for example in the Dashboard, Frekuent isn't notified. Contact Frekuent so the booking is cancelled or changed on their side too, or ask the customer to cancel through Frekuent.
Pickups/Dropoff Sync	❌	Frekuent doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Frekuent how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Frekuent doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Frekuent how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Frekuent. Customers can only book your main products and options on Frekuent. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Frekuent. Ventrata doesn't notify Frekuent when a ticket is scanned or redeemed. Frekuent only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Frekuent pass holders can't be scanned at your entrance without a booking. Customers from Frekuent need a booking made through Frekuent before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Frekuent. Gift cards bought in Ventrata can't be used on Frekuent, and Frekuent can't sell Ventrata gift cards.

✅ supported · ❌ not supported

Good to know: limits and details of the Frekuent connection

Delays: availability and prices reach Frekuent only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Frekuent can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Frekuent can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.
Tickets: Frekuent issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Frekuent can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Frekuent.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

📚 More about Ventrata connections

Partner Information

Frekuent

frekuent.com

Ventrata Partner ID: 019fea35-b524-78c0-95c9-2111bacf3871

Frekuent: Reseller Connection