.svg){kind=small}
Sell on Viator.
Travelers unlock with their phone.
Levy is your reservation system and your vehicle platform at the same time. Viator books against live Levy availability, the booking becomes a real reservation automatically, and the traveler unlocks a connected scooter, bike, or car at pickup—no counter, no keys, no re-keying.
4-Hour E-Bike Rental
Marketplace booking · Prepaid
Checked In
Agreement signed · Ready
Battery
94%
Zone
In Bounds
Return
4:00 PM
Booked on marketplace
Capacity held instantly
Reservation created
No manual entry
One connected operating path
Viator to Levy to the vehicle.
Supplier API
Viator
Requests live inventory and creates the booking
Reservation and fleet system
Levy Fleets
Holds capacity, creates the reservation, and starts check-in
Physical fulfillment
Connected vehicle
Appears in the operator dashboard and unlocks at pickup
The Difference
Every other booking system stops at the booking.
FareHarbor, Bokun, Rezdy and the rest hand you a confirmed reservation and a customer name. What happens next is your problem: someone has to be at the shop, find the right vehicle, hand over a key, and hope it comes back. Levy is the only reservation system where the booking is attached to a connected vehicle—so the rest of the rental runs itself.
A traveler books a scooter on a marketplace and unlocks it with their phone.
That whole chain—marketplace booking, reservation, check-in, unlock, ride, return—is one system. A booking can become a completed rental without a staff member touching it, which means bookings that land at 2 a.m. still work.
Remote unlock at pickup
The traveler taps their phone. No counter, no key handoff, no staff required.
Live GPS and telemetry
Location, battery, speed, and vehicle health streaming while the rental is out.
Geofencing
Define where the vehicle may go. Get alerted the moment it leaves the zone.
Automatic ride billing
Overtime, extensions, and per-minute usage bill themselves against the rental.
Return proof
Timestamped end-of-ride photos and location, so return disputes have an answer.
Remote lock
Close out the rental from the dashboard. The vehicle secures itself.
The Integration
Levy implements Viator's Supplier API. You stay the supplier.
Levy plays the reservation-system role—the same slot FareHarbor and Bokun occupy. Your business remains its own Viator supplier with its own contract, its own commission, and its own product codes. Levy implements the required API surface underneath it: tour list, real-time availability, booking, booking cancellation, and the outbound batch availability push.
Live availability that cannot oversell
Capacity is computed from your inventory caps, minus confirmed reservations, minus in-flight holds from every other channel and Levy's own checkout. And capacity is taken at reserve, not at confirm—so two marketplaces cannot sell the same vehicle in the same second.
Single-call booking
Viator books in one shot. Reserve and confirm run back to back, so the traveler gets an answer immediately.
Idempotent by design
Viator's bookingRef is the idempotency key. A retried call returns the original booking instead of selling a second vehicle.
No double entry
A Viator booking becomes a real Levy reservation automatically. Nobody re-keys it into a second system, so nothing gets mistyped or missed.
Sells both shapes of product
Fixed-duration rentals—a “4-hour e-bike” where the marketplace sends only a start time and your mapping supplies the duration. And per-person timed tour departures, sold by seat against a real schedule. Most operators run both, so both are first-class.
The Flow
From a tap on Viator to an unlocked vehicle.
Eight things have to happen between a traveler paying on a marketplace and riding away on your scooter. On Levy all eight are one system—and because Viator books in a single call, the first six of them are one HTTP request.
- 01
Viator
Marketplace
- 02
Availability
Levy
- 03
Hold
Levy
- 04
Confirmation
Same call
- 05
Reservation
Levy
- 06
Check-in
Traveler
- 07
Vehicle unlock
Pickup
- 08
Reconciliation
Money
Steps 01–06 all happen inside that single Viator request. Steps 07 and 08 happen later, on their own.
A traveler books on Viator
Viator books in one call — there is no separate reserve step. The booking reference it sends becomes our idempotency key, which is what makes their retry behaviour safe.
POST /api/channels/viator/v1/bookingThe slot is re-checked, never assumed
The requested start must match a slot your calendar actually publishes. Capacity is your inventory caps minus overlapping reservations minus every in-flight hold — including Levy's own checkout.
Capacity is taken at reserve
The hold is written inside a locked Postgres transaction that re-counts reservations and live holds in the same breath. Two requests for the last vehicle cannot both pass.
channel_reserve_pooled_capacity()Reserve and confirm collapse into one step
Because Viator sends no second call, confirmation runs immediately after the hold and the traveler gets a yes or no on the spot. A retried booking reference returns the original booking rather than selling a second vehicle.
A real reservation lands on your calendar
The same calendar your walk-ups and website checkouts use, with gross, commission, and net recorded on it. The hold is consumed only after the reservation exists, so nothing can slip into the gap.
Levy chases what Viator did not forward
A check-in link collects the missing email and phone number and gets your rental agreement signed before pickup. It never turns away a traveler who has already paid.
The vehicle unlocks from their phone
No counter, no key handoff. Live GPS, geofencing, and automatic ride billing run for the rest of the rental, and the vehicle locks itself at the end.
The statement is matched line by line
Weeks later the remittance arrives. Every line is matched, flagged as a variance, or surfaced as a confirmed booking the statement left out entirely.
Capacity decisions live in the database
Reserve, confirm, and release each run inside a locked database function rather than as read-then-write in application code. That is the difference between an oversell that is unlikely and one that cannot happen.
A stalled booking never strands a vehicle
If the confirm half of that call cannot complete, the booking is handed back to reserved instead of being left in limbo, and a guarded sweep returns the capacity to inventory minutes later. It runs every few minutes, and it cannot release the same hold twice.
The Money
Know exactly what
you are owed.
A marketplace booking is paid—just not through your card processor. The traveler pays Viator, Viator keeps its commission, and the rest arrives weeks later on a statement. Levy tracks all three numbers on every booking so the gap is never a mystery.
Commission-percentage or a fixed net rate per unit. Whichever your contract says.
A confirmed booking the statement left out is the one that quietly costs you money.
Gross
traveler paid
$4,180
Commission
per your contract
—
Net
you are owed
—
BR-40218
Harbor E-Bike, 4 hr
BR-40233
Sunset Tour, 2 pax
BR-40247
Scooter, full day
BR-40251
Harbor E-Bike, 4 hr
Control
A marketplace should
not run your fleet.
Distribution is worth having only if you stay in charge of it. Levy gives you the guardrails: how much inventory a channel can touch, exactly what each product code sells, and what a traveler has to complete before a vehicle unlocks.
Traveler check-in that does not block
Marketplaces 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 the missing data; it never turns away a traveler who already paid.
Per-channel inventory ceiling
Cap how much of the fleet a single marketplace may consume. Your walk-ups, your own website, and your other channels keep the inventory you reserved for them.
Explicit product mapping
Every Viator product code maps to a specific vehicle model or tour schedule. An unmapped code is refused outright rather than guessed — because guessing hands a traveler the wrong vehicle.
Cancellations release capacity
A cancelled booking hands its capacity straight back to the pool, so a cancelled seat is sellable again instead of stranded.
How It Works
Three steps to distribution
Connect the channel
Open Distribution channels in your dashboard, add Viator, and set the commission your contract specifies. Levy mints an API key for your account — yours alone, not a shared one.
Map your products
Point every Viator product code at a vehicle model or a tour schedule, and set an inventory ceiling if you want one. Nothing sells until the mapping exists, which is deliberate.
Go live and stay hands-off
Viator reads live availability and books against it. Reservations, check-in links, unlock, billing, and the money trail all run without anyone re-typing a thing.
Reach
One connection,
two marketplaces.
Viator is the largest experiences marketplace in the world, and TripAdvisor Experiences sells Viator inventory. Connecting Viator through Levy puts your fleet in front of travelers on both—from a single set of product mappings and one live availability feed.
Travelers plan the trip before they land. Being bookable at that moment—rather than hoping they find your shop—is the whole point.
The rest of the platform
Marketplace bookings land in the same fleet you already run on Levy. Same vehicles, same zones, same dashboard, same rider app—now with an extra sales channel attached to it.
Operator implementation snapshot
A Viator booking becomes an operable ride, not an inbox task.
The operator sees the incoming reservation beside direct bookings, with its assigned inventory, check-in status, channel money, and ride state attached.
Without the connected workflow
A marketplace confirmation still has to be reconciled with inventory, guest details, vehicle handoff, and the eventual remittance statement.
With the Levy connection
- Channel reservation visible immediately
- Guest check-in and agreement status attached
- Vehicle and remittance trail stay on one record
Reservations and rides
Live Levy Fleets operator interface
Related Integrations
Where operators go next.
Every channel runs on the same availability, the same holds, and the same money model. Adding one more is a mapping exercise, not another integration project.
TripAdvisor
TripAdvisor Experiences sells Viator inventory, so the connection on this page already reaches it. One mapping, one calendar, two audiences.
GetYourGuide
Deep European coverage on a true two-phase flow, where the vehicle is held while the traveler is still paying.
Klook
Inbound Asia-Pacific travelers who book same-day, served from the same live availability engine.
Google Maps
Free discovery with no marketplace commission. Travelers searching for a rental nearby book you direct instead.
Mews
Hotel demand. Guests add a scooter or e-bike to the room folio at the front desk, with no marketplace in the middle.
All integrations
Every marketplace, PMS, OEM, and IoT connection Levy speaks, in one directory.
See the Viator integration in action
Tell us how you sell today. We'll walk you through the Viator connection — live availability, automatic reservations, and keyless handoff.
Levy Fleets is an independent fleet management platform. Viator and TripAdvisor are trademarks of their respective owners, and Levy Fleets is not affiliated with or endorsed by them. Marketplace connections require your own supplier account and contract with the marketplace.