Transfer API vs Car Rental API
Both put a traveller in a car, but they sell different products, carry different data and fit different trips. Here is how they differ and when to use each.
Short answer
A Transfer API sells a driven, point-to-point ride — a vehicle with a driver from an airport, hotel or address to another, priced per journey. A Car Rental API sells a self-drive vehicle for a rental period, collected and returned at set locations and times, priced for the whole rental.
What each API sells
Transfer API — a driven ride
A transfer is ground transport with a driver: the supplier collects the traveller at an airport, hotel or address and drops them at another. The traveller never takes the wheel, and the product ends when the journey ends.
- Airport-to-hotel and hotel-to-airport rides
- Private point-to-point journeys in a city or between cities
- Priced per vehicle per journey
Car Rental API — a self-drive vehicle
A car rental gives the traveller a vehicle to drive themselves for a set period. They collect it at a rental location, use it for as many journeys as they like, and return it at the same or a different location.
- Rental periods from a day to several weeks
- Same-location and one-way rentals
- Priced for the whole rental, plus optional extras
Side-by-side comparison
The differences that change how you search, price, collect data and support the booking.
| Dimension | Transfer API | Car Rental API |
|---|---|---|
| Who drives | A professional driver supplied with the vehicle | The traveller, as the named renter or an added driver |
| What is sold | A single journey from point A to point B | Use of a vehicle for a rental period |
| Booking unit | One ride, per direction (return = two journeys) | Pick-up date/time to drop-off date/time, often several days |
| Pricing basis | Per vehicle per journey, set by route and vehicle type | For the whole rental, set by duration, vehicle class and location |
| Locations | Exact pick-up and drop-off: airport, hotel or street address | Rental stations: airport desks and downtown branches; one-way rentals return elsewhere |
| Vehicle choice | Vehicle type sized to passengers and luggage | Vehicle class (economy to luxury), transmission and seat count; model is “or similar” |
| Traveller data | Lead traveller name and contact; flight details matter for airport pick-ups | Driver details; minimum age and licence rules apply per offer |
| Extras | Usually none — the price covers the ride | Insurance, GPS, child seats, additional drivers, mileage terms |
| Main risk to manage | Flight delays and meeting the driver on time | Deposits, licence eligibility, fuel and mileage conditions |
| Typical buyers | Airport arrivals, corporate travel, city breaks, groups | Road trips, multi-stop holidays, long stays, rural destinations |
| On Tripgic | Transfer API — 6 documented endpoints; Essential and Enterprise plans | Car Rental API — search, book, modify and cancel; Enterprise plan |
When to use each
Choose the Transfer API when
- The traveller only needs to get from A to B — usually the airport and the hotel
- They cannot or do not want to drive: business travel, late arrivals, unfamiliar cities
- Groups need one larger vehicle rather than several cars
- You want to attach ground transport to a flight booking as a simple add-on
Choose the Car Rental API when
- The trip has many stops or several days of local travel
- The destination has limited public transport or taxis
- The traveller wants freedom over timing and route
- You sell holidays where the car is part of the experience — road trips, islands, countryside
Traveller scenarios
Which product fits the trip — and why.
| Traveller scenario | Best fit | Why |
|---|---|---|
| Business traveller landing at night, meetings in the city centre next morning | Transfer | Only needs one reliable ride to the hotel; no driving or parking in an unfamiliar city. |
| Family of four flying in for a week-long road trip along the coast | Car Rental | Needs a vehicle every day across many stops; child seats added to the rental. |
| Group of 12 delegates moving from airport to a conference venue | Transfer | One larger vehicle with a driver is simpler and cheaper than several rentals. |
| Couple staying in a countryside villa with limited public transport | Car Rental | Daily freedom to move matters more than a single A-to-B journey. |
| Traveller who will drive themselves but lands after the rental desk closes | Both | Transfer to the hotel tonight, collect the rental car from a downtown branch in the morning. |
Integration differences
Both follow the normalized Tripgic JSON approach, so the same integration patterns carry over. What changes is the data each step needs.
Transfer booking flow
- Search transfers for a route and date
- Open a single transfer offer for full details
- Add the lead traveller’s information
- Create the booking
- Retrieve booking details
- Cancel the booking if needed
Key inputs: exact pick-up and drop-off points, date and time, passengers and luggage, and flight details for airport pick-ups.
Car rental booking flow
- Search by pick-up and drop-off location, date and time
- Filter offers by vehicle class, transmission and seats
- Review supplier terms: driver age, licence, mileage
- Add extras such as insurance, GPS or child seats
- Create the reservation
- Modify or cancel the reservation over the API
Key inputs: rental locations and times, driver details and age, and the extras the traveller selects.
Endpoint and field reference: see the API documentation.
Selling both in one trip
Transfers and car rentals are complements, not competitors. A common pattern is a transfer for the arrival — the traveller is tired, it is late, or the rental desk is closed — followed by a self-drive rental for the days that follow. Offering both lets a platform cover the whole ground segment instead of sending the traveller elsewhere.
Because Tripgic returns flights, hotels, transfers and car rentals through one integration, the ground options can be shown next to the flight and hotel in the same checkout. See solutions for how OTAs and TMCs package this, and pricing for which plan includes each product.
Related products
Frequently asked questions
What is the difference between a transfer and a car rental?
A transfer is a ride: the supplier provides the vehicle and the driver and takes the traveller from one point to another. A car rental is a self-drive hire: the traveller collects a vehicle, drives it themselves for the rental period and returns it.
Is an airport transfer the same as renting a car at the airport?
No. An airport transfer is a one-off driven journey from the airport to a hotel or address. Renting a car at the airport means the traveller picks up a self-drive vehicle at the airport desk and keeps it for days, with licence, age and insurance conditions attached.
Which API should a travel platform integrate first?
It depends on the traveller. Platforms selling city breaks, corporate trips and airport arrivals usually start with transfers, because the traveller only needs to get from A to B. Platforms selling road trips, multi-stop holidays and long stays in regions with limited public transport get more value from car rental.
Does the Car Rental API include a driver?
No. Car rental offers are self-drive. If the traveller needs a driver, sell a private transfer through the Transfer API instead.
Can I sell transfers and car rentals in the same booking flow?
Yes. Both use the same normalized JSON approach as Tripgic flights and hotels, so a platform can offer an airport transfer on arrival and a self-drive rental for the rest of the trip from one integration.
Which Tripgic plans include each API?
The Transfer API is included in the Essential and Enterprise plans. The Car Rental API is available on the Enterprise plan.
Add transfers and car rental to your platform
Book a short kick-off call, get sandbox credentials at no charge, and build both products against one normalized schema.