.svg){kind=small}
Every channel Levy connects.
One reservation system underneath.
Marketplaces, channel managers, a hotel PMS, and the open feed that puts your vehicles on a map. All eleven are live today, all eleven read the same live availability, and every booking lands on a connected vehicle the traveler unlocks with their phone.
The Architecture
Eleven connections. One engine.
The hard problems in distribution are not wire formats. They are: never overselling when two channels race for the last vehicle, never double-booking on a retry, and knowing to the cent what a channel owes you. Levy solved those once, generically. Every connection on this page — open standard or native adapter — is a translation layer on top of that same core.
Levy is the reservation system
Levy occupies the slot FareHarbor or Bokun would occupy — the system a marketplace queries for availability and books against. You stay the supplier, with your own account, your own contract, and your own product codes on every channel.
One OCTO connection, many marketplaces
OCTO is an open connectivity standard for tourism, maintained independently of Levy. Levy ships one conformant supplier API, and every marketplace that reads OCTO connects over it. Adding the next one is a product-mapping exercise, not another integration project.
Native adapters where a marketplace wants its own format
Viator, GetYourGuide, Rezdy and Mews publish their own APIs. Each gets a thin native adapter that translates on the outside and shares the same core inside: hold-aware availability, capacity claimed under a database lock, idempotent booking, and the same money model.
Every booking lands on a connected vehicle
This is the part other reservation systems stop short of. A confirmed booking becomes a real Levy reservation on a real vehicle — check-in link, signed rental agreement, remote unlock at pickup, telemetry while it is out, and remote lock at the end.
The Directory
Pick the channels that fit your fleet.
Every connection below has a working adapter and is live today. Filter by how it connects, or by what you need it to do.
Filter by category
Filter by capability
Direct OTA connections
3 connectionsThese marketplaces publish their own supplier API, so Levy ships a native adapter that speaks each one’s wire format. Same reservation engine underneath, different translation on the outside.
Viator
Direct OTA
The largest experiences marketplace, and a single-call booking flow — the traveler gets an answer immediately.
- Live availability that cannot oversell
- Single-call booking, idempotent on the booking reference
- Explicit product mapping per Viator product code
- Remittance reconciliation, line by line
TripAdvisor
Direct OTA
TripAdvisor Experiences is powered by Viator, so one connection reaches both marketplaces.
- Reached through the same Viator connection
- One set of product mappings covers both
- Single-call booking
- Live availability shared with every other channel
GetYourGuide
Direct OTA
Two-phase reserve → confirm, so the real vehicle is held while the traveler checks out. Europe-strong and mobile-first.
- Two-phase reserve → confirm holds the actual vehicle
- Abandoned checkouts expire and hand capacity back
- Live availability that cannot oversell
- Remittance reconciliation, line by line
OCTO marketplaces
4 connectionsOCTO — Open Connectivity for Tourism — is an open standard, maintained independently of Levy, that these marketplaces read. Levy serves one conformant supplier API, so a new OCTO channel is a mapping exercise rather than another integration project.
Klook
OCTO
Asia-Pacific inbound demand, frequently booking for the same day they ride.
- Served by the shared OCTO supplier API
- Two-phase reserve → confirm under a database lock
- Explicit product mapping per product code
- Remittance reconciliation, line by line
Expedia
OCTO
Trip context: the activity gets added alongside the flight, often months ahead of arrival.
- Served by the shared OCTO supplier API
- Month-level calendar plus per-request live availability
- Two-phase reserve → confirm under a database lock
- Remittance reconciliation, line by line
Tiqets
OCTO
Museums and attractions, with instant mobile tickets — the traveler expects redemption to be immediate.
- Served by the shared OCTO supplier API
- Day-level calendar plus per-request live availability
- Two-phase reserve → confirm under a database lock
- Remittance reconciliation, line by line
Headout
OCTO
Last-minute and in-destination: a curated shortlist for travelers who are already in the city.
- Served by the shared OCTO supplier API
- Two-phase reserve → confirm under a database lock
- Explicit product mapping per product code
- Remittance reconciliation, line by line
Discovery feeds
1 connectionNo marketplace, no commission, no supplier contract. Levy publishes an open feed and the rider ends up booking in your own app, on your own account, at your own price.
Channel managers & PMS
3 connectionsSystems that sit between you and demand you already have — a reseller network, or the guests asleep upstairs. Same availability rules and the same money model as every marketplace channel.
Bokun
Channel manager & PMS
A channel manager: one connection that opens onto a whole reseller network.
- One connection reaches the resellers in the network
- Reserve and confirm commit together in a single call
- Explicit product mapping per product code
- Remittance reconciliation, line by line
Rezdy
Channel manager & PMS
An independent channel manager with Australia and New Zealand roots and a distribution network of its own.
- Native RezdyConnect adapter on the shared channel engine
- Orders commit in a single call, inside a locked transaction
- Idempotent on Rezdy’s own order number
- Remittance reconciliation, line by line
Mews
Channel manager & PMS
A hotel PMS. The rental posts to the guest folio and settles at departure — no marketplace commission at all.
- Bills to the guest folio through the Mews Connector API
- Zero channel commission, so net equals gross
- Two-phase reserve → confirm under a database lock
- Live availability shared with every other channel
Side by Side
How the eleven differ.
Commercial terms are set by your own contract with each channel, so the commission column describes the model Levy tracks rather than a rate. Scroll the table sideways for the full comparison.
| Integration | Booking flow | Product shapes | Commission model | Reconciliation | Best for |
|---|---|---|---|---|---|
| ViatorDirect OTALive | Single call | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | Global reach; travelers who book before they land |
| TripAdvisorDirect OTALive | Single call (through Viator) | Rentals and tours | Whatever your Viator supplier contract sets | Reconciled alongside Viator remittances | Trip-planning traffic, at no second integration |
| GetYourGuideDirect OTALive | Two-phase reserve → confirm | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | European demand and mobile-first bookers |
| KlookOCTOLive | Two-phase reserve → confirm (OCTO) | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | Inbound Asia-Pacific and same-day bookings |
| ExpediaOCTOLive | Two-phase reserve → confirm (OCTO) | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | Long-lead bookings attached to a booked trip |
| TiqetsOCTOLive | Two-phase reserve → confirm (OCTO) | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | Attraction-adjacent rentals with instant mobile redemption |
| HeadoutOCTOLive | Two-phase reserve → confirm (OCTO) | Rentals and tours | Commission % or fixed net rate, per your supplier contract | Line-by-line remittance matching, with omissions flagged | In-destination travelers deciding in the moment |
| Google Maps & transit appsDiscoveryLive | No booking API — an open feed; the rider books in your app | Shared-vehicle rentals | None. Nobody takes a cut of a ride that started on a map | Not applicable — you collect the payment yourself | Local discovery inside trip planners and transit apps |
| BokunChannel manager & PMSLive | Single call (reserve and confirm commit together) | Rentals and tours | Commission % or fixed net rate, per your channel agreement | Line-by-line remittance matching, with omissions flagged | Reaching many resellers through one agreement |
| RezdyChannel manager & PMSLive | Single call (order commits at once) | Rentals and tours | Commission % or fixed net rate, per your channel agreement | Line-by-line remittance matching, with omissions flagged | AU/NZ distribution and agent networks |
| MewsChannel manager & PMSLive | Two-phase reserve → confirm | Rentals and scheduled departures | None — a zero-commission channel; the property owns the demand | Settles on the guest folio at departure | Hotels and resorts renting to guests already on property |
“Two-phase” means Levy holds the real vehicle at reserve and turns it into a reservation at confirm. “Single call” means the channel commits in one request and Levy runs reserve and confirm back to back. Either way, capacity is claimed at reserve inside a locked transaction, so two channels cannot sell the same vehicle in the same second.
Shared By All Eleven
The guarantees do not change per channel.
Whichever connections you turn on, they inherit the same engine. That is the point of doing it this way: adding a channel does not add a new class of accounting bug.
One availability calculation
Your inventory caps, minus confirmed reservations, minus in-flight holds from every other channel and from Levy’s own checkout, minus that channel’s ceiling. Every connection reads the same number.
Idempotent by design
The channel’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.
Gross, commission, net on every booking
Commission-percentage and fixed net-rate agreements are both supported, and the database refuses to store a split where gross does not equal commission plus net.
Remittance reconciliation
Statements reconcile line by line against bookings, flagging variances and — the one that quietly costs money — confirmed bookings the statement left out.
Explicit product mapping
Every external product code points at a specific vehicle model or scheduled departure. An unmapped code is refused with a reason rather than guessed.
Check-in, unlock, telemetry, return
A check-in link collects what the channel did not forward and gets the rental agreement signed. Then remote unlock, live GPS, geofencing, automatic billing, return proof, and remote lock.
How It Works
Same three steps for every channel
Add the connection
Open Distribution channels in your dashboard and add the channel. Levy mints an API key scoped to your account alone and records the commercial terms your own contract with that channel specifies.
Map your products
Point every external product code at a vehicle model or a scheduled departure, and set an inventory ceiling if you want one. Nothing sells until the mapping exists, which is deliberate.
Go live and stay hands-off
The channel reads live availability and books against it. Reservations, check-in links, unlock, billing, and the money trail run without anyone re-typing a thing — including at 2 a.m.
What Levy does not do
Levy does not sign you up to a marketplace. Every channel here requires your own account and contract with that company, which is also what sets your commercial terms. Levy is the reservation system that connection points at — it is not a reseller, an agent, or a party to your agreement. The one exception is the discovery feed: publishing GBFS needs no marketplace account at all, though each app decides independently whether and when to display a given system.
Ready to Launch Your Fleet?
Get started with a personalized consultation. We'll help you plan, launch, and scale your fleet with our complete ecosystem.
Levy Fleets is an independent fleet management and reservation platform. Viator, TripAdvisor, GetYourGuide, Klook, Expedia, Expedia Group, Tiqets, Headout, Google Maps, Apple Maps, Transit, Citymapper, Bokún, Rezdy, Mews and FareHarbor are trademarks of their respective owners, named here only to describe how Levy connects to or compares with those services. None of them has certified, approved, endorsed, or partnered with Levy Fleets. OCTO is an open connectivity standard maintained independently of Levy; GBFS is an open specification stewarded by MobilityData. Connecting a marketplace, channel manager, or PMS requires your own account and contract with that company, which sets your commercial terms. Publishing a GBFS feed makes your data available to any application that chooses to consume it; each application decides independently whether and when to display a given system, and Levy Fleets cannot guarantee inclusion in any specific app.