.svg){kind=small}
Bring your Levy fleet to Bokun.
One connection, your whole reseller network.
A lot of rental operators already run distribution through a channel manager: one inventory, many marketplaces, one place to change a price. The Levy connection is live. Bokun reads your mapped catalogue, checks real availability on every request, and books straight into your fleet—and the vehicle on the other end unlocks from the traveler's phone.
Distribution channels
One inventory, many places to sell it
Connected and selling
Battery
94%
Zone
In bounds
Return
4:00 PM
One connected operating path
Bokun to Levy to the vehicle.
Channel manager API
Bokun
Aggregates reseller demand and submits the mapped booking
Reservation and fleet system
Levy Fleets
Exposes live catalogue, availability, and booking endpoints
Physical fulfillment
Connected vehicle
Turns the reseller order into a connected rental
How It Connects
Three endpoints. Connect it from the dashboard.
Open Dashboard → Distribution channels, add the Bokun connection, and map your Bokun product and rate codes to specific vehicle models or departure schedules. The key is shown once and stored only as a hash. From there Bokun talks to three endpoints and everything it sends becomes a reservation in the fleet you already run.
You can leave the connection in testing while you shake it out against your real catalog—it accepts real calls without being switched on to the world, and you decide the moment it goes live.
Bokun reads what you mapped
Bokun pulls your bookable catalogue to map it onto its own experiences. Only the products you explicitly mapped for this connection appear, so connecting Bokun never exposes the whole fleet.
Every check hits live capacity
Availability is answered live, not from a nightly export, so Bokun’s cache and its checkout re-check both see true capacity: your inventory caps, minus confirmed reservations, minus in-flight holds taken by every other channel seconds earlier.
Reserve and confirm in one call
Bokun commits on behalf of whichever reseller in its network made the sale, so the booking runs reserve and confirm together and lands as a real Levy reservation. A cancel releases the capacity immediately.
A retry returns the original booking
Bokun's confirmationCode is the idempotency key, enforced by a unique index. When a downstream reseller times out and Bokun retries—which it does—the retry returns the booking that already exists instead of selling the vehicle a second time.
You see which reseller sold it
Bokun fronts a whole network, so the reseller that actually made the sale is recorded on every booking. “A Bokun booking” is not one undifferentiated bucket—you can tell which partner is producing.
The Flow
One sale, followed all the way through.
From a reseller you have never spoken to, to a vehicle unlocking in your city, to the line on a statement six weeks later. This is the whole path, in the order it happens.
- Step 1
A reseller in the network makes the sale
A traveler books on a marketplace, an agent's site, or an activity desk somewhere in the Bokun network. Nothing in your business has to be awake for this to happen.
- Step 2
Bokun is the one system talking to Levy
Whoever sold it, Bokun is the counterparty on the wire. It reads only the catalogue you explicitly mapped for this connection, so adding Bokun never exposes the whole fleet.
- Step 3GET /api/channels/bokun/v1/availability
Levy answers with live capacity
Not a nightly export. Your inventory caps, minus confirmed reservations, minus in-flight holds taken by every other channel seconds earlier, minus this channel's inventory ceiling. Bokun's cache and its checkout re-check both see the same true number.
- Step 4POST /api/channels/bokun/v1/booking
Reserve and confirm, in one call
Bokun commits on behalf of the reseller rather than holding first, so Levy runs reserve and confirm back to back. Capacity is taken at reserve, not at confirm — waiting until confirm is exactly how two channels sell the same vehicle to two travelers.
- Step 5
It becomes a real Levy reservation
No re-keying into a second system. The booking lands as a reservation against a specific vehicle model at a pickup location, with gross, commission, and net recorded on it. A cancel releases the capacity immediately.
- Step 6
Check-in chases what the channel did not send
Channels forward very little — often a first name and nothing else. Levy issues a check-in link that collects the missing contact details and gets the rental agreement signed before pickup. It chases; it never turns away a traveler who already paid.
- Step 7
The vehicle unlocks at pickup
The traveler taps their phone at the rack. Live GPS, telemetry, and geofencing run for the length of the rental, overtime bills itself, and return is proven with a timestamp, a location, and a photo.
- Step 8
The statement reconciles line by line
Weeks later the remittance arrives. Levy reconciles it into matched, variance, unmatched — and the one that quietly costs money every month, a confirmed booking the statement left out entirely.
Capacity is taken inside a locked Postgres transaction
The recount and the write happen in the same transaction, at reserve. Read-then-write in application code is what once let two requests for the last vehicle both pass the availability check before either wrote a hold.
The idempotency key is Bokun's confirmationCode
Enforced by a unique index. When a downstream reseller times out and Bokun retries — which it does — the retry returns the booking that already exists rather than selling the vehicle a second time.
The selling reseller is recorded per booking
Bokun fronts a whole network, so the partner that actually made the sale is stored on every booking. “A Bokun booking” is not one undifferentiated bucket — you can tell which partner is producing.
Who This Is For
You already run
distribution through Bokun.
That is the whole reason this page exists. Some operators evaluating Levy are not looking for another marketplace integration—their inventory, rates, and reseller agreements already sit in a channel manager, and they want their Levy fleet to show up there rather than move.
Bokun is a good system and plenty of operators are happy on it. The question this page answers is not whether to leave it—it is how a connected fleet gets distributed through it.
One inventory, many storefronts
A channel manager exists so you stop maintaining the same twelve products in six different back offices. Change a price once; it propagates.
Breadth without a build per marketplace
Adding a reseller becomes a configuration step inside a system you already use, instead of a new integration project every time.
You already have the workflow
Contracts, rate agreements, and reseller relationships already live there. Migrating that off to gain a vehicle platform is a bad trade — you should not have to.
Levy plugs in underneath
Levy takes the reservation-system role — the slot FareHarbor and Rezdy occupy: the system that answers availability, accepts the booking, and owns the reservation underneath it.
The Difference
A channel manager moves bookings. None of them touch the vehicle.
Bokun, FareHarbor, Rezdy—they are very good at getting a confirmed booking from a marketplace into your back office. Then it stops. Somebody still has to be at the shop, find the right vehicle, hand over a key, and hope it comes back. Levy is the reservation system where the booking is attached to a connected vehicle, so the half of the rental that happens after the booking runs itself.
The booking is not a row in a list. It is a scooter that unlocks.
Distribution, reservation, check-in, unlock, ride, billing, return—one system, one record. A booking can become a completed rental without a staff member touching it, which is what makes a 2 a.m. booking for a 7 a.m. pickup a non-event.
Remote unlock at pickup
The traveler taps their phone. No counter, no key handoff, no staff member waiting for a 7 a.m. arrival.
Live GPS and telemetry
Location, battery, speed, and vehicle health streaming for the whole time the rental is out.
Geofencing
Define where the vehicle may go. Get alerted the moment it leaves the zone, not when it fails to come back.
Automatic ride billing
Overtime, extensions, and per-minute usage bill themselves against the rental instead of becoming an awkward conversation.
Return proof
Timestamped end-of-ride photos and location, so a return dispute has an answer instead of two opinions.
Remote lock
Close the rental out from the dashboard. The vehicle secures itself wherever it is.
The Foundation
The adapter is thin because the core is real.
The hard problems in channel distribution are not wire formats. They are: never overselling when two channels race, never double-booking on a retry, and knowing to the cent what a reseller owes you. Levy solved those once, generically, and every adapter—OCTO, Viator, GetYourGuide, Bokun—is a thin translation on top of the same core.
Live availability that cannot oversell
Capacity is your inventory caps, minus confirmed reservations, minus in-flight holds from every other channel and from Levy's own checkout. And capacity is taken at reserve rather than at confirm, under a database lock—so two channels cannot sell the same vehicle in the same second.
An OCTO supplier API
Levy ships a conformant OCTO surface—the open connectivity standard for tourism. Any reseller that speaks it can connect without a bespoke build on either side.
Two-phase reserve → confirm
A reserve holds the real vehicle while the traveler finishes checkout, and a reaper hands the capacity back if they abandon it. Nothing sits held forever.
Idempotent by design
The reseller's own booking reference is the idempotency key, enforced by a unique index. A retried call returns the original booking instead of selling a second vehicle.
No double entry
A channel booking becomes a real Levy reservation automatically. Nobody re-keys it into a second system, so nothing gets mistyped, dropped, or entered twice.
Sells both shapes of product
Fixed-duration rentals—a “4-hour e-bike” where the channel sends only a start time and your mapping supplies the duration. And per-person timed departures, sold by seat against a real schedule. Most rental operators run both, so both are first-class rather than one bolted onto the other.
Bokun is one connection of several.
Levy connects to Viator directly, and TripAdvisor Experiences sells Viator inventory—so that one connection reaches both. GetYourGuide has a native adapter, and any reseller that speaks OCTO connects without a bespoke build on either side. Run Bokun alongside them or on its own; the inventory, the ceilings, and the money model are shared.
The Money
Distribution is only
good if you get paid.
A channel booking is paid—just not through your card processor. The traveler pays someone else, a commission is retained somewhere in the chain, and the remainder arrives weeks later on a statement. Levy records all three numbers on every booking, and the database refuses to store a split where gross does not equal commission plus net.
A commission percentage, or a fixed net rate per unit regardless of what the channel retails it for.
A confirmed booking the statement left out is the one that quietly costs you money every single month.
The conservation identity is a database constraint, so a bad split cannot be written at all.
What the channel reported is preserved alongside the accounting figure, so a dispute has evidence.
Gross
traveler paid
$4,180
Commission
retained
$1,045
Net
you are owed
$3,135
CH-70118
Harbor E-Bike, 4 hr
CH-70133
Coastal Tour, 2 pax
CH-70147
Scooter, full day
CH-70151
Harbor E-Bike, 4 hr
Illustrative figures. Reconciliation and money tracking are part of Levy's shipped channel layer.
Control
Reach is worth having only if you stay in charge of it.
The failure mode of easy distribution is a channel quietly consuming your best vehicles on your best weekend. These guardrails live in the channel layer, and the Bokun connection inherits every one of them.
Per-channel inventory ceiling
Cap how much of the fleet any one channel may consume. Your walk-ups, your own website, and your direct bookings keep the inventory you set aside for them — distribution should not eat the business it was meant to grow.
Explicit product mapping
Every external product code points at a specific vehicle model or departure schedule. An unmapped code is refused outright rather than guessed, because guessing hands a traveler the wrong vehicle and you find out at pickup.
Check-in that chases, never blocks
Channels forward very little — often a first name and nothing else. Levy issues a check-in link that collects the missing contact details and gets the rental agreement signed before pickup. It never turns away a traveler who has already paid.
Cancellations release capacity
A cancelled booking hands its capacity straight back to the pool, guarded so it can only be released once. A cancelled seat becomes sellable again instead of silently shrinking the day.
Your own credentials
Each connection gets its own API key, shown once and stored only as a hash. Keys are rotated, never recovered, and outbound secrets live where the dashboard cannot read them back.
Test before you go live
A connection runs in testing while a channel certifies it, accepting real calls without being flipped on to the world. You decide the moment it goes live.
The Rest Of It
Distribution is a feature,
not the product.
Channel bookings land in the same fleet you already run on Levy—same vehicles, same zones, same dashboard, same rider app, same billing. A new sales channel is an attachment to an operating platform, not a separate stack you now have to reconcile against.
Managed plans start at $250/mo. If you are weighing Levy against a booking system plus a channel manager plus a telematics vendor, that is the comparison worth running.
One platform underneath every channel
Whether a booking arrives from your own app, your website, a marketplace, or your channel manager, it becomes the same reservation against the same connected vehicle.
Questions
The obvious ones, answered plainly
Is the Levy Bokun integration available right now?
Yes. The Bokun connection is live. You add it from Dashboard → Distribution channels, map your Bokun product and rate codes to specific vehicle models or departure schedules, and Bokun starts reading your catalogue, checking availability, and booking into your fleet.
What does the connection actually do?
Three things. Bokun reads the bookable catalogue you mapped for this connection. It checks live availability. And it books — reserve and confirm in a single call, because Bokun commits on behalf of whichever reseller in its network made the sale. Cancels come back on the same booking and release the capacity immediately.
What happens when Bokun retries a booking?
Nothing is sold twice. The confirmationCode Bokun sends is the idempotency key, enforced by a unique index, so a retry after a downstream reseller times out returns the original booking instead of taking a second vehicle. The reseller that made the sale is recorded on the booking too, so a Bokun booking is not one undifferentiated bucket.
Can a Bokun booking oversell my fleet?
No. Availability is live rather than a nightly export, so Bokun’s cache and its checkout re-check both see true capacity: your inventory caps, minus confirmed reservations, minus in-flight holds from every other channel and from Levy’s own checkout. Capacity is taken inside a locked Postgres transaction, so two channels cannot sell the same vehicle in the same second, and a per-channel inventory ceiling caps how much of the fleet Bokun may consume.
What if Bokun sends a product code I have not mapped?
It is refused outright rather than guessed. Every external product code has to point at a specific vehicle model or departure schedule, because guessing hands a traveler the wrong vehicle and you find out at pickup. Unmapped codes also surface on the catalogue response, so a broken mapping shows up there instead of as an unexplained booking failure later.
Would I have to leave Bokun to use Levy?
No. If Bokun is where your rates and reseller relationships live, they stay there. Levy takes the reservation-system role underneath — the slot FareHarbor or Rezdy would occupy — answering availability, accepting the booking, and owning the reservation against a real connected vehicle.
What makes Levy different from a booking system plus a channel manager?
A channel manager moves bookings between systems. It does not touch the vehicle. In Levy the booking is attached to a connected vehicle, so the traveler unlocks it from their phone at pickup, you get live GPS and telemetry and geofencing during the rental, overtime bills automatically, return proof is captured, and the vehicle can be locked remotely.
Operator implementation snapshot
The reseller network reaches the fleet without creating another system of record.
Bokun remains the distribution layer while Levy remains the operational layer, with every reseller order visible beside direct reservations and active rides.
Without the connected workflow
A channel manager can distribute the product while still leaving vehicle assignment, guest readiness, and ride completion outside the booking record.
With the Levy connection
- Mapped catalogue and capacity stay current
- Retries return the original booking
- Connected-vehicle fulfillment stays in Levy
Unified distribution dashboard
Live Levy Fleets operator interface
Related Integrations
Bokun is one way in. It is not the only one.
Levy connects to the big marketplaces directly as well, so an operator can run a channel manager and a direct connection at the same time. The product mappings, the inventory ceilings, and the money model are shared, and availability is computed once against the whole fleet.
Direct alternative
Rezdy
Rezdy solves the same problem Bokun solves: one inventory, many resellers, one place to change a price. Both are good at it, and Levy connects to both the same way — so if your rates and reseller agreements live in Rezdy instead, nothing here changes except the adapter.
Compare the Rezdy connectionDirect connection
Viator
Levy connects to Viator natively as well, so you can run it through Bokun or straight from Levy. Same fleet, same availability calculation either way.
Read moreDirect connection
TripAdvisor
TripAdvisor Experiences sells Viator inventory, so the direct Viator connection reaches both marketplaces without a second integration.
Read moreDirect connection
GetYourGuide
A native GetYourGuide adapter on the same core. Run it through your channel manager or beside it — availability is computed once against the whole fleet either way.
Read moreThe full list
All integrations
Every distribution channel, PMS, and IoT platform Levy connects to, including the conformant OCTO supplier API any OCTO-speaking reseller can read.
Read moreSee the Bokun integration in action
Tell us how you distribute today. We'll show you the Bokun connection and exactly what changes on your side.
Levy Fleets is an independent fleet management platform. Bokun, Viator, TripAdvisor, GetYourGuide, FareHarbor, and Rezdy are trademarks of their respective owners, and Levy Fleets is not affiliated with, endorsed by, certified by, or partnered with any of them. Channel connections require your own account and contract with the channel or marketplace.