Mohammad Fahim
An airport services API lets an OTA or travel app search, price and book business lounge access, Fast Track lanes and Meet & Greet escorts, and sell them beside a flight. Tripgic is a unified travel API that returns all three in the same normalized JSON as its flights and hotels, so they sit in one checkout.
This guide is for the team that already sells trips and wants to earn more on each one. It explains what an airport services API is, how the three products differ, why they matter, how the booking flow works, where to place the offer in your checkout, how pricing and margin work, and how to choose a provider. It ends with how Tripgic does it and a short list of other providers.
What Is an Airport Services API?
An airport services API is a booking interface for the things a traveller can buy at the airport itself, not on the plane. Your system sends a search with an airport code, a terminal, a direction (departure, arrival or transit), a date and the number of passengers. The API returns bookable options with a price, the terms and the details of what is included. You book the one the traveller chooses, and the API confirms it and returns a voucher, usually a QR code.
Three products make up most of this market:
- Business lounge access. A pass into an airport lounge with seating, food and drink, Wi-Fi and often showers.
- Fast Track. Priority lanes at security, passport control or customs, often with an agent who walks the traveller through.
- Meet & Greet. A personal agent who meets the traveller, helps with bags and escorts them through each checkpoint.
The industry calls these airport ancillaries: products sold on top of the core booking, which is why the same tool is sometimes called an airport ancillary services API. They are different from airline ancillaries such as bags and seats, which only the airline can sell. An airport service belongs to the airport visit, so any travel seller can offer it, whatever airline the traveller flies.
One warning about the name. Search “airport API” and you will find many airport data APIs, which return airport codes, locations, gates or flight status. They are useful, but they do not sell anything. If your goal is revenue, you need a booking API that returns products with prices and confirms orders.
Why Should an OTA Sell Airport Add-ons Beside Flights?
In short: every traveller passes through an airport, travellers already pay for extras, and an airport add-on adds a second product to an order whose fare leaves a thin margin. It also gives you a reason to contact the traveller again before departure, and it does not depend on which airline they fly.
The audience is large. Airports Council International forecast 9.8 billion passengers at the world’s airports in 2025. Each of them queues at security, and many wait at a gate or change planes, which is the moment an airport service is built for.
Travellers also pay for extras. IdeaWorksCompany projected that airlines worldwide would earn 157 billion US dollars in ancillary revenue in 2025, up from 148.4 billion in 2024, and that ancillaries would reach 15.7% of total airline revenue, up from 9.1% in 2016. Its 2026 Yearbook reports that ancillary revenue grew nearly twice as fast as overall airline revenue.
Those are airline numbers, and they are context, not a forecast for airport services. The lesson for an OTA or agency is narrower: travellers are used to paying for comfort and time on top of the fare. A flight ticket usually leaves the seller a thin margin, because fares are compared side by side on every metasearch screen. An airport add-on tends to be less price-compared, because the traveller is choosing comfort and time rather than the cheapest seat.
Airport services help with five problems that flight-only sellers face:
| Problem | How an airport add-on helps |
|---|---|
| Thin margin on the ticket | Adds a second product to the same order, priced with your own margin |
| The traveller leaves after payment | Gives you a reason to contact them again before departure |
| Every OTA sells the same fares | Lets you build a travel experience, not only a price |
| Corporate clients ask for duty of care | Meet & Greet and Fast Track help a travel manager look after staff on tight connections |
| Loyalty and card programmes need rewards | Lounge passes are a common card and loyalty reward |
IATA’s Dynamic Offers work on airline retailing points the same way: it pairs continuous pricing with dynamic bundling, and an airport add-on placed at the right checkout step is a small version of that bundle.
What Is the Difference Between Lounge, Fast Track and Meet & Greet?
In short: a lounge sells comfort while the traveller waits, Fast Track sells time saved in the security and immigration queues, and Meet & Greet sells a personal escort that saves time and removes stress. Each suits a different traveller, so knowing which one to offer to whom is the start of selling them well.
| Business lounge access | Fast Track | Meet & Greet | |
|---|---|---|---|
| What the traveller gets | Seating, food and drink, Wi-Fi, often showers and work areas | Priority lanes at security, passport control or customs | A personal agent from arrival at the airport to the gate, or from the aircraft to the exit |
| Main value | Comfort while waiting | Time saved in queues | Time saved and stress removed |
| Direction | Mostly departure and transit | Departure, arrival and transit | Departure, arrival, transit and round trip |
| Typical buyer | Long-haul, early-morning and layover travellers | Business travellers, tight connections, busy hub airports | First-time flyers, elderly parents, families, VIPs |
| Key data to match | Airport, terminal, airside location, opening hours | Airport, terminal, direction, date | Airport, terminal, flight time, language |
| Typical voucher | QR code shown at the lounge door | Booking reference or QR code for the agent | Booking reference; agent holds a name-board |
Business lounge access
A lounge pass is the easiest airport add-on to understand and the easiest to sell. The traveller sees a clear benefit: a quiet seat, a meal and Wi-Fi instead of a crowded gate. Lounge passes come in two kinds. A pre-book pass guarantees entry once confirmed, but must be booked a minimum number of hours ahead. A walk-in pass is accepted at the door subject to capacity, which can mean a wait at busy times. Your checkout should show which kind the traveller is buying.
Fast Track
Fast Track is about time. On departure it covers priority security and often express check-in and passport control. On arrival it can cover the immigration fast lane and customs. In transit it can mean an escort to the connecting gate and a fast lane at re-screening. It sells best where queues are known to be long and where connections are tight.
Meet & Greet
Meet & Greet is the most personal of the three. An agent meets the traveller with a name-board, helps with bags and stays with them through each checkpoint. It is the product a family books for parents flying alone, or a company books for a senior visitor. Language matters here more than anywhere else, so look for a provider that assigns agents by the traveller’s language.
Who Uses an Airport Services API?
In short: OTAs and travel agencies sell airport services beside a flight, while travel apps, banks, loyalty programmes and tour operators often sell them on their own or as a benefit. The use case decides where the product appears, how it is priced and what data you have when you search.
| Business | How they use airport services | What matters most |
|---|---|---|
| OTA | Add-on after the flight is chosen, and again in manage-booking | Coverage on top routes, instant confirmation, simple checkout copy |
| Travel agency or TMC | Added by an agent or in the corporate booking tool for executives and new joiners | Meet & Greet for VIPs, group bookings, clear cancellation terms |
| Travel app or super-app | A standalone “airport” tab, or a push message before departure | Search by airport and date without a flight, fast QR delivery |
| Bank, fintech or card programme | Lounge passes as a card benefit or a points redemption | Voucher format, per-pass cost control, reporting |
| Loyalty programme | Lounge access and Fast Track as rewards in a catalogue | Wide airport list, simple redemption, no complex servicing |
| Tour operator or DMC | Meet & Greet on arrival, bundled into a package | Arrival service, language, link to the transfer |
The first two sell beside a flight. The last four often sell without one, which changes the data you have. With a flight, you already know the airport, terminal, direction and time. Without one, the traveller must enter them, and your interface has to make that easy.
Banks, fintechs and super-apps that add travel to their own product can read our guide to the embedded travel API. Points and rewards teams should see our guide to travel APIs for loyalty programs, where lounge passes are a common redemption.
If you also sell rides from the airport, read our guide to the airport transfer API. For connectivity, see the eSIM API. Both pair naturally with airport services in one trip.
How Does an Airport Services API Work?
In short: you search by airport, terminal, direction, date and passengers; read the options with their price and terms; drop the ones that do not fit the flight; add your margin; book; and deliver the voucher. Every provider names its fields differently, but the flow is almost always these six steps.
- Search. Send the airport code, terminal, direction, date and passengers (adults and children). Some APIs also accept a flight number or time to filter options that fit the schedule.
- Read the options. Each option comes with a product type, the airport and terminal, what is included, the price per passenger, the confirmation type, the voucher type and the cancellation terms.
- Match to the flight. Drop options that do not fit. A departure lounge in Terminal 5 is no use to a traveller leaving from Terminal 3. A pre-book option with a 24-hour notice period cannot be sold for a flight in six hours.
- Price and display. Add your margin, convert currency if needed, and show the option with its terms in plain words.
- Book. Send the booking with the passenger names and contact details. Most providers confirm instantly; some confirm on request. The response tells you which.
- Deliver and service. Send the voucher to the traveller, store the booking reference, and handle changes and cancellations within the returned terms.
Two details cause most of the problems after launch: the confirmation type and the cancellation terms per option. Both are covered in the rules table further down. The short version is to read them from each option and show them before payment, not in an email afterwards.
How Do You Match an Airport Add-on to a Flight?
In short: copy the airport, terminal, direction, date, passengers and language from the flight booking into the airport service search, and drop every option that does not fit. The difference between a good airport add-on and a refund is this data matching.
| Flight booking field | Airport service search field | Why it matters |
|---|---|---|
| Departure airport code | Airport, direction = departure | Lounge and departure Fast Track |
| Departure terminal | Terminal | Lounges are terminal-specific and often airside |
| Departure date and time | Date, minimum notice check | Pre-book options need advance notice |
| Arrival airport and terminal | Airport, direction = arrival | Arrival Fast Track and Meet & Greet |
| Connection airport and gap | Airport, direction = transit | Transit escort or a lounge on a long layover |
| Passenger list | Adults, children | Per-passenger pricing |
| Traveller language (from profile) | Language preference | Meet & Greet agent assignment |
An illustrative example. A family of four books a flight from London to a city in South East Asia with a connection in Dubai, the kind of one-stop trip our guide to Gulf airlines’ NDC fares covers. They leave early in the morning and have a long layover.
- London, departure: search Fast Track for the departure terminal for two adults and two children, and a lounge in the same terminal. A family with small children values both.
- Dubai, transit: search a transit lounge for the layover. If the gap is short, search a transit escort instead.
- Destination, arrival: search Meet & Greet for the arrival terminal, with the family’s language. If they have also booked a car from the airport, the agent can hand them over to the driver.
The seller does not show all of this at once. It offers the two most relevant options in checkout and saves the rest for a pre-departure message. The rule is simple: offer what fits this traveller’s flight, not the whole catalogue.
Where Should You Place Airport Add-ons in Checkout?
In short: place the offer where the traveller is already thinking about the airport. That is just after the flight is chosen, on the confirmation and manage-booking pages, and in a message two to three days before departure. The same product placed at the wrong step looks like an upsell and gets ignored.
| Placement | What to show | Why it works |
|---|---|---|
| After the flight is chosen, before payment | One or two options that fit the flight, with a clear benefit line | The traveller is already thinking about the trip, and the price is small next to the fare |
| Confirmation page | “Add a lounge for your layover” with one tap | The main decision is done; a small extra feels easy |
| Manage-booking page | All available airport services for each leg | Travellers return here to check details and are open to extras |
| Pre-departure message, two to three days out | Fast Track and lounge for the departure airport | The traveller is now thinking about queues and waiting time |
| Arrival-focused message | Meet & Greet and the transfer together | Answers “how do I get out of the airport?” in one place |
| Standalone airport tab in an app | Search by airport and date, no flight needed | Serves travellers who booked their flight elsewhere |
Three practical rules help conversion:
- Lead with the benefit. “Skip the security queue” says more to a traveller than “Fast Track service”.
- Show the terms next to the price. Confirmation type and cancellation terms build trust.
- Bundle where it is natural. A long-haul fare with a lounge and Fast Track can be sold as one “smooth departure” bundle with one price. Our guide to the dynamic packaging API covers how bundles are priced and built.
How Do Pricing and Margin Work for Airport Add-ons?
In short: you buy each airport service at the provider’s rate and either add your own margin, fold it into a bundle, or give it away as a benefit that a card, employer or loyalty programme pays for. Your real margin depends as much on the provider’s fee model and settlement as on the net rate itself.
There are two layers of pricing: what the provider charges you, and what you charge the traveller.
What you charge the traveller. Most sellers take one of three approaches.
| Model | How it works | Suits |
|---|---|---|
| Net plus margin | You buy at the net rate and add a fixed amount or a percentage | OTAs and agencies selling single add-ons |
| Bundle | The add-on is folded into a fare or package price | Tour operators, premium fare bundles |
| Benefit or reward | The traveller pays nothing; the card, employer or loyalty programme pays | Banks, fintechs, corporate travel, loyalty programmes |
What the provider charges you. Provider models vary widely:
- Wholesale net rates, sometimes with volume tiers and monthly invoicing.
- Commission on each sale, where the provider sets the retail price.
- Subscription or platform fee, sometimes on top of per-booking costs.
- A flat fee per booking, where the cost does not grow with the price of the item.
Ask each provider four questions: Is there a setup fee? Is the per-booking cost fixed or a percentage? How is settlement done, by invoice or by a prepaid wallet? Can you set your own selling price? The answers decide your margin more than the headline net rate does.
For a deeper look at how travel APIs charge, read our guide to travel API pricing models.
What Do Pre-book, Walk-in and Cancellation Rules Mean?
In short: each option carries its own rules. Pre-book or walk-in decides whether entry is guaranteed, the confirmation type decides when you can say “confirmed”, and the cancellation terms decide whether you keep the money. Read them from each option, never from a fixed template.
| Rule | What it means | What to do in your product |
|---|---|---|
| Pre-book | Entry guaranteed once confirmed; must be booked a minimum number of hours ahead | Hide the option when the flight is closer than the notice period |
| Walk-in | Voucher accepted at the door, subject to capacity | Say clearly that entry depends on space at busy times |
| Instant confirmation | The booking is confirmed in the API response | Show “confirmed” and send the voucher at once |
| On-request confirmation | The provider confirms later | Show “pending” and notify the traveller when confirmed; never show “confirmed” early |
| Free cancellation window | Cancel without charge up to a set time before the service | Show the deadline in the booking and in reminders |
| Non-cancellable | No refund once booked | Show this before payment, in plain words |
| Voucher type | QR code, booking reference or printed pass | Make the voucher easy to find on a phone, offline |
A common mistake is to treat every option the same. Two lounges at the same airport can have different rules, and hidden terms turn into disputes and chargebacks. Your interface should read the rules from each option.
Flight changes add one more case. If the traveller’s flight moves to another day or terminal, the airport service booked for the old flight may no longer fit. Build a check into your schedule-change process that flags linked airport services and offers to rebook or cancel them within their terms.
How Do You Choose an Airport Services API? 10 Questions
In short: ask for coverage airport by airport on your own routes, check that every option carries terminal, direction, confirmation type and cancellation terms, and test it in a free sandbox. Then compare the fee model with your volume. Use these ten questions in every provider call; they separate a real booking API from a brochure.
- Which airports and terminals do you cover on my top routes? Ask for the list, airport by airport. A headline count tells you little.
- Which products do you sell at each airport? Lounge only, or Fast Track and Meet & Greet as well?
- Do options carry terminal and direction? Without them, you cannot match the add-on to a flight.
- What is the confirmation type? Instant, or on request? Is it returned per option?
- Are cancellation terms returned per option? Or do you have to read them from a contract?
- What voucher do you issue? QR code, reference, or both?
- Can I book for a group in one request, with adult and child prices?
- Is it the same API as my flights and hotels? One schema means one integration, one error model and one reconciliation.
- Is there a free sandbox with realistic data? Can my team build before paying?
- How do you charge, and how do I settle? Setup fee, per-booking fee, percentage or flat, invoice or wallet?
For general guidance on comparing providers, see how to choose a travel API provider.
How Tripgic Does This
Tripgic is a unified travel API that returns airport services in the same normalized JSON as its flights, hotels, transfers, activities and tours. Tripgic describes itself as a technical intermediary and aggregator, not a direct travel operator: it provides the infrastructure layer, and bookings are fulfilled by the underlying suppliers. Airport services can be sold as checkout add-ons or on their own.
What does Tripgic’s airport services API cover?
Tripgic sells Business Lounge access, Fast Track and Meet & Greet through one API, with Meet & Greet at 180+ airports in the partner network and agents in 40+ languages. Lounge and Fast Track coverage is returned per airport, so a search only shows options that can be booked.
| Product | Search by | Directions | Cancellation | Coverage |
|---|---|---|---|---|
| Business Lounge | Airport and terminal | Tied to a terminal and a direction, per option | Terms returned with each option | Varies by airport and terminal; only bookable lounges are returned |
| Fast Track | Airport, direction and travel date | Departure, arrival and transit | Terms returned with each option | Varies by airport; check the availability checker |
| Meet & Greet | Airport, terminal and flight time | Arrival, departure, transit and full round trip | Terms returned with each option | 180+ airports, agents in 40+ languages |
Business Lounge. Tripgic’s airport lounge API returns lounge access per airport and per terminal, with each lounge’s amenities in the response, such as premium seating, food and beverages, Wi-Fi and shower suites, subject to what each lounge offers. Most passes confirm instantly with a digital voucher or QR code, and the confirmation type is returned in the booking response.
Fast Track. Tripgic’s airport Fast Track API covers three stages: departure (priority security lane, express check-in, immigration assist), arrival (immigration fast lane, customs assist, baggage support) and transit (transfer escort, re-security fast lane, gate-to-gate support). A dedicated agent walks the traveller through. Pricing is per passenger for adults and children, and solo and group bookings go in one request. Tripgic’s Fast Track page states that all partners are officially airport-authorised.
Meet & Greet. The Meet & Greet API matches agents to the traveller’s preferred language at booking. An agent meets the traveller with a name-board, helps with bags and gives fast-lane access at check-in, security and immigration. Booking confirms instantly, and the cancellation terms come back with each option, so you can show them before payment.
What a response looks like. The Fast Track page publishes an abbreviated sample response. Here it is with the price field left out:
{
"product_id": "fasttrack_7qXe",
"airport": "LHR",
"direction": "departure",
"services": ["priority_security", "express_checkin", "immigration_assist"],
"agent": "dedicated",
"pax": { "adults": 2, "children": 1 },
"confirmation": "instant"
}The product pages mark these field names as illustrative, so confirm them against the production API spec during your kick-off.
Check coverage before you build. The availability checker lets you search by IATA code, airport name, city or country and see every option at each airport, grouped by service, with its terminal, direction and booking rules, such as pre-book or walk-in and the cancellation terms. Besides lounges, Meet & Greet and Fast Track, the checker lists two more airport services sold through the same API: Dining Vouchers (pre-paid meals at airside restaurants and cafés) and VIP Service (private terminal zones with formalities handled for the traveller). The checker is indicative; live availability, pricing and terms come from the API at booking time.
One integration for the whole trip. The same API sells flights from 700+ airline and LCC connections, 2M+ hotel properties, transfers and travel eSIM, across 8 API product families. The API docs list 73 endpoints with code samples in PHP, Node.js and Python.
How you start. You request access or book a short call. The team walks through your use case, and a free sandbox lets your developers build and test the airport services flow before going live. Once your account is activated, live credentials typically arrive within 3–5 business days.
How you pay. Tripgic charges a flat fee per booking, never a percentage of the fare, and settlement runs on a prepaid e-wallet. The current details are on the pricing page.
Which Other Providers Offer Airport Services APIs?
In short: several companies sell airport lounge access by API, and a few also sell meet and assist services. Most are lounge-only, which means a separate integration from your flights and hotels. The right one depends on what else you sell.
The facts below come from each company’s own website, read on 3 November 2026. Tripgic is listed first because this is our blog, not because of a ranking.
| Provider | Products | What it offers, in its own words | Suits |
|---|---|---|---|
| Tripgic | Lounge, Fast Track, Meet & Greet | All three in the same normalized JSON API as flights, hotels and transfers | Sellers who want airport services and the rest of the trip in one integration |
| Holiday Extras | Lounge | Public lounge API documentation with endpoints to check lounge availability at an airport and to book a lounge | Teams that want a lounge-specific API |
| Airport.Online | Lounge | Wholesale lounge passes with QR vouchers via a REST API or a white-label widget, drawing on partner networks including DragonPass | Agencies, TMCs and loyalty programmes focused on lounges |
| DreamFolks | Lounge, meet and assist, transfers | Airport services for OTAs and airlines by API, self-booking portal or white label | Sellers wanting a managed airport services programme |
| Xoxoday | Lounge | A Lounge API for discovering and booking airport lounges, within its rewards platform | Rewards and benefits platforms |
| LoungeReview | Lounge information | Lounge content (amenities, access rules, locations) to display in an app or website | Apps that need lounge content to display |
The key difference is scope. A lounge-only API is a separate integration from your flights and hotels, with its own schema, contract and reconciliation. A unified travel API puts airport services in the same response format as the flight they belong to.
How Should You Roll Out Airport Add-ons?
In short: start with your top airports and one product, build the flight match, test two placements, and expand only once the first one shows a steady attach rate. You do not need to launch every airport and every product at once, and a phased rollout shows you what sells before you scale.
- Pick your top airports. Take the departure and arrival airports that carry most of your bookings. Check coverage there first in your provider’s checker or sandbox.
- Start with one product. Lounge access is the easiest to explain and to fulfil. Add Fast Track and Meet & Greet once the flow works.
- Build the flight match. Map airport, terminal, direction, date and passengers from your booking into the search. Filter out options that do not fit.
- Design two placements. Usually one in checkout and one in a pre-departure message. Measure attach rate (the share of bookings that add the service) for each.
- Handle the after-sale. Voucher delivery, cancellations within terms, and schedule-change checks. Train support on the difference between pre-book and walk-in.
- Expand. Add more airports, more products and bundles once the first placement shows a steady attach rate.
Three launch mistakes are not covered by the rules above, and each one costs sales rather than causing refunds:
| Mistake | What happens | Fix |
|---|---|---|
| Offering every option at every airport | Long, confusing lists; low conversion | Show one or two options that fit the flight |
| No pre-departure reminder | Missed sales and forgotten vouchers | Send the voucher and the offers before departure |
| Generic product names | Low interest | Lead with the benefit: time saved, comfort, help |
If you are building the flight side at the same time, our flight booking API guide covers that integration, and our guide to travel APIs for OTAs covers the whole stack. Corporate sellers can also read about the corporate travel API, where Meet & Greet and Fast Track help with duty of care.
The Bottom Line
An airport services API turns the airport visit into a product you can sell: a lounge for the long wait, Fast Track for the queue, Meet & Greet for the traveller who needs a hand. Most of the work is in the matching. Offer each option only where it fits the traveller’s airport, terminal, direction and time, show its terms before payment, and service it when the flight changes.
If you want airport services in the same API as your flights and hotels, check coverage on the Tripgic availability checker, then book a kick-off call and start building in the free sandbox.
