Transfers API
Transfers API
Airport and point-to-point ground transport, priced per vehicle.
On the roadmapSpecified and architected. Not yet built — timeline agreed per partner.
Transfers are the most commonly attached ancillary to a hotel booking and the easiest incremental margin in the stack. The interface is specified and slotted behind the hotel path.
Coverage
Planned through ground-handling aggregators and direct DMC contracts. No coverage claim until the first contract.
Latency behaviour
Not published before implementation.
Authentication
OAuth 2.0 client credentials
Stated plainly:This API is not implemented. The endpoints below describe the intended contract so you can design against it; calling them today will not return live travel data.
Capabilities
- Airport to hotel, hotel to airport, and point-to-point
- Vehicle classes with passenger and luggage capacity
- Flight-number linkage for arrival monitoring
- Meet-and-greet and child-seat options
What it does not do
- — Not implemented.
- — Live arrival monitoring depends on a flight-data source that is not yet contracted.
Reference
Endpoints
The full surface, with real request and response shapes where the endpoint is implemented.
GET
/v1/transfers/searchSearch available transfer products for a route and time.
POST
/v1/transfers/bookingsIdempotency-Key requiredBook a transfer.
POST
/v1/transfers/bookings/{bookingId}/cancelIdempotency-Key requiredCancel a transfer booking.