Transfer
Add airport pickups, private and shared transfers, and chauffeur rides to the booking platform you already run. We connect your system to one ground transportation supplier or several, so travellers book the ride in the same checkout as their flight, hotel or package.
Transfer API integration connects your travel platform to a ground transportation supplier's API, so you can search, price, book and manage pre-booked rides inside your own system. It covers airport pickups and drop-offs, port and station transfers, and point-to-point rides with a driver, sold as private, shared or chauffeur services.
Once transfers run through an API instead of email or a supplier portal, three things change:
Transfers sit in the same checkout. Travellers add the ride while they book the flight, hotel or package, not afterwards on another website.
No details are typed twice. Arrival airport, flight number, hotel address and passenger count come from the booking you already hold.
One booking record. The transfer's supplier reference, voucher and status live next to the rest of the trip, where your team and your reports can see them.
Transfer integration usually starts with a business that already sells travel and wants the ride from the airport to be part of the same booking. These are the four most common setups.
Your packages already contain the flight, the hotels and the itinerary. We add arrival and departure transfers as package components, priced from the supplier at the moment of booking and filled in from the hotel and flight already in the package. Multi-centre trips can carry a transfer between each stop, and the rides appear in the same package pages and checkout your travel portal already shows.
Transfers work as an ancillary in three places: during checkout, in the confirmation email, and in the traveller's manage-my-booking page. We connect the transfer search to your flight API integration and hotel data, so the traveller sees rides for their actual arrival airport and hotel without retyping either.
Agents need to book transfers the way they book hotels: net rates, your markup, their commission and a voucher they can send. We add transfers to your B2B portal with agent-level pricing rules, booking on credit or wallet balance, and vouchers in your brand.
Corporate travellers need chauffeur and car service that fits the travel policy and appears in reporting. We connect premium and chauffeur suppliers to your booking tools, and where your agents work in a GDS, we align the transfer flow with your GDS integration.
A transfer API looks simple from the outside: send two locations and a time, get prices back. In practice each supplier models locations, prices, vehicles and post-booking changes its own way. Each capability below starts with that supplier-side difference and then says what we build to handle it.
One supplier rarely covers every airport you sell, at the price and service level you want. We connect one or several transfer suppliers behind a single search, map their responses into one data model, remove duplicate results, and apply your rules for supplier priority and fallback when a supplier is slow or returns nothing.
Suppliers identify places differently. Some take an IATA airport code, some a Google Place ID or coordinates, and others their own hotel and terminal codes from a static content feed. Booking.com's transfer API, for example, accepts an airport code, a Place ID or coordinates but not a mix in one location, while Hotelbeds publishes a separate cache API for its hotel, terminal and route codes. We build the geocoding and mapping layer that turns your hotel, address or airport into what each supplier expects, and we cache static content so search stays fast.
A private transfer is priced per vehicle; a shared shuttle is priced per seat. Results also depend on passenger count, luggage, child seats and accessibility needs. We normalise prices so options compare fairly on screen, filter out vehicles that cannot carry the party, and re-check the live price before booking so the traveller pays what they were shown.
An airport pickup booked for the scheduled landing time is only useful if the driver adjusts when the flight is late. Many transfer suppliers ask for the flight number for this reason, but waiting-time and delay policies differ by supplier. We capture the flight number once, from the flight in the booking or from the traveller, pass it to the supplier, and print that supplier's waiting policy on the voucher.
We build the booking step with the passenger, contact, flight and pickup details each supplier requires, store the supplier's reference against your booking, and generate a voucher with the meeting point, pickup time and supplier contact. Confirmation emails and itineraries pick the transfer up automatically.
Post-booking support is where suppliers differ most. Some offer amendment endpoints and push status changes by webhook; others support cancellation only, or need polling for updates. We implement whatever each supplier offers, keep your booking record in sync, apply cancellation cut-offs in your own interface, and route anything the API cannot handle to your operations team.
Transfer suppliers pay in different ways: a net rate you mark up, a commission on a retail price, or a fee per transaction. We add rules for markup by supplier, channel, vehicle type or agent, and keep the figures your finance team needs to reconcile supplier invoices and commissions.
Many operators already have local transfer companies they trust in key destinations. We let you load those contracted routes and prices next to API results, so you can sell your own supply where you have it and API supply everywhere else.
Which of these you can sell depends on the suppliers you connect; private airport transfers are a sensible first phase, with the rest added as you need them.
| Transfer Type | Priced By | Typical Use | Usually Supplied By |
|---|---|---|---|
| Private airport transfer | Vehicle | Arrival and departure for one party, door to door | Transfer aggregators, bed-bank transfer products |
| Shared shuttle | Seat | Budget airport-to-hotel rides with several stops | Bed-bank transfer products, aggregators |
| Chauffeur and black car | Vehicle (often fixed or hourly) | Corporate, VIP and premium leisure | Chauffeur networks |
| Point-to-point and intercity | Vehicle, by route or distance | Hotel to hotel, city to city on multi-stop trips | Aggregators, chauffeur networks |
| Port and station transfers | Vehicle or seat | Cruise embarkation, rail arrivals | Aggregators, bed-bank transfer products |
| Hourly hire with driver | Hour | Business days, sightseeing at the traveller's pace | Chauffeur networks |
| Coach and minibus for groups | Vehicle | Group arrivals, tours and events | Local operators, specialist suppliers |
Transfer suppliers fall into a few distinct types, and the right mix depends on where you sell, who your customers are and how you want to be paid. Access to every supplier below is granted by the supplier under its own commercial agreement; we work with you through onboarding and the technical integration.
Aggregators connect many local transfer companies behind one API, which gives the widest coverage from a single integration.
If you already buy hotels from a wholesaler, its transfer product can reuse the same commercial relationship. Hotelbeds (HBX Group) Transfers API offers availability, booking, booking detail, cancellation and amendment, plus a cache API for hotels, terminals, vehicles and transfer types. HBX Group also owns Holiday Taxis. Where your hotel API integration [LINK: Hotel API page] already uses Hotelbeds, transfers to and from those hotels can be added under the same supplier account.
Chauffeur networks supply sedans, business vans and premium vehicles for corporate and luxury travel. Blacklane provides API connectivity for TMCs, booking agents and corporate travel teams, and is also bookable through Sabre, Amadeus and Travelport. Talixo offers pre-booked rides to OTAs, wholesalers, agencies and TMCs through API, GDS or agency accounts; technical access is arranged with the supplier.
Some ground transportation is booked where agents already work. Amadeus offers transfer content through its Enterprise APIs under contract; its Self-Service developer APIs, including transfer search and booking, were retired on 17 July 2026. Corporate ground transportation platforms such as GroundSpan distribute chauffeur and car service content into GDS and corporate booking tools. If your agents book in a GDS, we align the transfer flow with your GDS integration.
You don't need a new booking platform to sell transfers. Most established travel businesses already have a booking engine, a package catalogue, customer data and live bookings they cannot put at risk. We build the transfer layer into what you have and connect it at the points that matter:
| Your System | What the Transfer Integration Does There |
|---|---|
| Booking engine or checkout | Adds transfer search and booking to the flight, hotel or package flow of your travel booking engine, prefilled from the booking |
| Package and itinerary builder | Attaches arrival, departure and between-stop transfers as package components |
| B2B agent portal | Gives agents transfer search with net rates, markups and vouchers in your brand |
| CRM | Writes transfer bookings, changes and traveller contacts to the customer record in your travel CRM |
| Payment gateway | Takes payment for the transfer in the same checkout, or settles with the supplier on account |
| Accounting and back office | Records supplier costs, markups and commissions for reconciliation |
| Operations or dispatch tools | Sends contracted-transfer jobs to your own local operators |
Most transfer suppliers offer three ways in. A white label or widget gets you live quickly; an API integration is the only option that puts transfers inside your own checkout, data and reporting.
| API integration | White label | Widget or affiliate link | |
|---|---|---|---|
| Where the traveller books | Your checkout | A supplier-hosted page in your branding | The supplier's flow, embedded or linked |
| Control of design and flow | Full | Limited to branding options | Minimal |
| Booking data in your systems | Yes, every booking and status change | Usually via reports or exports | Usually commission reports only |
| Bundled with flight, hotel or package | Yes, in one booking | Separate booking | Separate booking |
| Your pricing and markup rules | Yes | Depends on the supplier | Rarely |
| Merchant of record | Usually you (net rate) — check the supplier's terms | Often the supplier | The supplier |
| Development effort | Highest | Low | Lowest |
Every transfer integration follows the same seven steps; the length of each depends on the number of suppliers and how much of your platform the transfers touch.
We map where you sell, the transfer types you need, your channels (B2C, B2B, corporate) and the systems transfers must connect to.
We shortlist suppliers against your coverage and commercial needs, and support you through registration, agreements and API credentials.
We review each supplier's endpoints, authentication and static content, and design how locations, vehicles and prices map into your data model.
We build the supplier connections, search and booking flow, pricing rules, vouchers, notifications and back-office updates.
We test search, booking, amendment, cancellation and status updates against each supplier's test environment, including failure cases.
Where the supplier requires a certification or go-live review, we prepare and pass it, then switch to production credentials and monitor the first live bookings.
We watch error rates and response times, and update the integration when suppliers change or retire API versions
We build travel integrations into platforms that are already running, and we understand both sides of a transfer: the booking flow your traveller sees and the dispatch side a transfer company runs.
We have connected multiple hotel suppliers into one search for a growing travel agency, expanding hotel choice by 50%, and built an OTA platform on Sabre's flight, hotel and car APIs. The same normalisation, caching and booking-lifecycle work applies to transfer suppliers.
We add capabilities to live booking systems without taking them offline, the same approach behind our group travel management modules for established operators.
We also build taxi booking and dispatch apps, so we know what a transfer supplier needs from your booking to deliver the ride.
We monitor integrations after launch and keep them current as supplier APIs change. All engagements are covered by an NDA.
We have fulfilled the demands of clients working in different industries. For more details, check what our clients say about us.
An airport transfer API is a supplier’s set of web services that lets a travel platform search, price and book pre-booked rides between an airport and a hotel, address or other location. It returns private and shared options with vehicle types and prices, and booking creates a pickup with a supplier reference and voucher.
A transfer API covers driver-included rides such as airport, port and point-to-point transfers. “Ground transportation API” is broader and can also include bus, rail and ferry tickets, which are priced and booked per seat on a scheduled service.
Yes. We map each supplier’s locations, vehicles and prices into one data model, remove duplicates and apply your rules for which supplier to show or prefer.
Yes. Suppliers issue API credentials under their own agreements, and some require a certification or go-live review. We help you through onboarding, but the commercial relationship is between you and the supplier.
Yes, where the supplier sells on a net rate. We build markup rules by supplier, channel, vehicle type or agent. Commission-based suppliers set the retail price, so the margin comes from the commission instead.
When the flight number is included in the booking, many suppliers adjust the pickup to the actual arrival. Waiting time and delay policies differ by supplier, so we show each supplier’s policy on the voucher.
A private transfer is priced per vehicle and takes one party directly to its destination. A shared shuttle is priced per seat and carries several parties, with more stops and a lower price.
Yes. We can load your local operators’ routes and prices into the same search, so you sell your own supply where you have it and API supply elsewhere.