Flight Booking API
A flight booking API lets your platform sell a real airline ticket, not just show a fare. Tripgic is one REST integration to search, price, book and ticket flights across Amadeus, Sabre and Travelport, airline-direct NDC offers and 100+ low-cost carriers. Every source returns the same normalized JSON, so you build one booking flow instead of one per supplier.
Last updated
800+
airlines reachable
3
GDS networks
100+
low-cost carriers
15
documented endpoints
What the Flight API gives you
One integration, one JSON envelope — authenticated with the same credentials as every other Tripgic product.
Flight search
Search flights by route, date, traveller mix, cabin, preferred carrier, non-stop and baggage preference across every connected source at once.
Branded fares
Read the fare families an airline offers for a flight, so travellers can choose between fare brands instead of a single price.
Price and itinerary validation
Validate the selected itinerary and price before booking, and read the validation status back by tracking ID.
Baggage, seats and meals
Read and update baggage options, seat maps and seat selections, and meal options through dedicated endpoints.
Booking and ticketing
Add traveller details, create the booking and issue tickets over the API — no manual ticketing step on your side.
Retrieve and cancel
Pull booking details at any time and cancel a flight booking through the same integration.
Three flight sources, one response
GDS, NDC and low-cost carrier content normally mean three integrations and three data models. Tripgic searches them together and returns one result set.
GDS content
Amadeus (1E), Sabre (1S) and Travelport (1G/1V) — full-service carrier schedules, fares and ticketing.
GDS connectivityNDC airline-direct
IATA NDC offers straight from airlines — branded fares, dynamic pricing and ancillaries, blended with GDS results.
NDC connectionsLow-cost carriers
100+ low-cost carriers that sit outside traditional GDS distribution, returned alongside full-service airlines.
LCC directoryCoverage spans 51,519 commercial air routes. Search the route directory or open the route atlas.
Flight booking API vs flight search and flight data APIs
"Flight API" covers three different products. Only a booking API creates a reservation and issues a ticket under your brand — search APIs hand the traveller to someone else, and data APIs return schedules or prices with nothing to sell.
| Flight booking API | Flight search / affiliate API | Flight data API | |
|---|---|---|---|
| What it does | Search, price, book and issue the ticket | Shows fares, then redirects the traveller to an airline or OTA | Returns schedules, historical prices or live flight status |
| Issues a ticket | Yes — you sell and own the booking | No | No |
| Who owns the customer | You | The site the traveller is sent to | Not applicable |
| How you earn | Your own margin on each sale | Referral commission | None from the API itself |
| Typical users | OTAs, TMCs, B2B agent portals, travel apps | Metasearch and content sites | Analytics, airport and flight-tracking apps |
Tripgic is a flight booking API. For the full comparison read the flight API guide.
Booking flow
15 documented endpoints. Every call is a POST to the base URL issued with your credentials, and returns a tracking_id you carry into the next step.
- 1Search — search flights and, where offered, read branded fare options
- 2Validate — confirm the selected itinerary and price, then read the validation status
- 3Travellers — add passenger details to the validated itinerary
- 4Create booking — create the flight booking
- 5Issue ticket — issue tickets for the validated booking
- 6Manage — retrieve booking details or cancel the booking
Ancillaries: baggage, seat and meal each have a read endpoint and an update endpoint — six of the 15.
Pricing: the validated price is final — supplier net fare plus a flat per-passenger markup of USD 5 (Starter), USD 3 (Growth) or USD 2 (Enterprise), never a percentage. Markup policy.
Full request and response fields are in the API documentation.
Request — POST /flight/search
Response envelope (abbreviated)
Abbreviated from the flight search example in the documentation.
All 15 flight endpoints
Every call is a POST and returns the same JSON envelope. Field-level detail is in the API documentation.
| Step | Endpoint | What it does |
|---|---|---|
| Search | /flight/search | Search GDS, NDC and LCC content by route, date, travellers, cabin and carrier |
| Fare families | /flight/branded-fare | Read the branded fares an airline offers for the selected flight |
| Validate | /flight/validate | Confirm the itinerary and lock the final price |
| Validation status | /flight/validation-get-status | Read the validation result back by tracking ID |
| Travellers | /flight/update-travellers | Add passenger names, documents and contacts |
| Baggage | /flight/get-baggage-option · /flight/update-baggage | Read and sell extra baggage |
| Seats | /flight/get-seat-plan · /flight/update-seat | Show the seat map and save seat selections |
| Meals | /flight/get-meal-option · /flight/update-meals | Read and sell meal options |
| Book | /flight/create-booking | Create the reservation |
| Ticket | /flight/issue-ticket | Issue the e-ticket for the booking |
| Manage | Booking details · /flight/cancel-booking | Retrieve the booking at any time or cancel it |
Direct GDS integration vs the Tripgic flight API
Connecting to each GDS yourself means a contract, a certification and a different data format per network — before NDC and low-cost carriers are even added.
| Direct GDS connection | Tripgic Flight Booking API | |
|---|---|---|
| Content | One GDS per integration | Amadeus, Sabre, Travelport, NDC and 100+ LCCs in one search |
| Contracts | A separate agreement with each GDS | One Tripgic agreement |
| Certification | Per GDS, before you can go live | No per-GDS certification |
| Data format | Different schemas per network (EDIFACT, SOAP/XML, REST) | One normalized JSON response |
| Time to first booking | Typically 6–12 months | Sandbox in days after a kick-off call |
| Pricing | GDS fees, minimum segments and integration cost | One-time plan activation plus a flat USD 2–5 per passenger, never a percentage |
What a direct connection really costs: GDS API cost breakdown · how NDC aggregators work.
Migrating from the Amadeus Self-Service API
Amadeus closed its Self-Service APIs on 17 July 2026 and disabled the self-service keys; only the contract-based Enterprise APIs remain. If your app used Flight Offers Search, Flight Offers Price or Flight Create Orders, each call has a direct equivalent in the Tripgic flight booking API — and you also get Sabre, Travelport, NDC and low-cost carriers through the same integration.
Full Amadeus migration guide| Amadeus Self-Service | Tripgic endpoint |
|---|---|
| Flight Offers Search | /flight/search |
| Branded Fares Upsell | /flight/branded-fare |
| Flight Offers Price | /flight/validate |
| SeatMap Display | /flight/get-seat-plan |
| Flight Create Orders | /flight/update-travellers → /flight/create-booking → /flight/issue-ticket |
| Flight Order Management | Booking details · /flight/cancel-booking |
Who uses a flight booking API
Online travel agencies
Sell GDS, NDC and low-cost fares side by side in one results page and keep the margin on every ticket.
TMCs and corporate tools
Add flights to a corporate booking tool with branded fares and ancillaries, without a GDS contract per market.
B2B agent portals
Give sub-agents live fares and instant ticketing on a portal you brand and price yourself.
Apps, super-apps and loyalty
Run flight booking inside a private-label app or rewards programme, with your brand on every screen. Loyalty travel API · Embedded travel.
Explore more inventory
Frequently asked questions
What is the Tripgic Flight API?
The Tripgic Flight API is a single REST integration for searching, pricing, booking and ticketing flights. It returns Amadeus, Sabre and Travelport GDS content, airline-direct NDC offers and 100+ low-cost carriers in one normalized JSON format, so you build one booking flow instead of one per supplier.
Which flight sources does it cover?
Three GDS networks — Amadeus (1E), Sabre (1S) and Travelport (1G/1V) — plus IATA NDC airline-direct content and 100+ low-cost carriers. Together that is 800+ airlines reachable from one integration.
Do I need my own GDS contract to start?
No. Tripgic gives you sandbox access to Amadeus, Sabre and Travelport content, NDC and low-cost carriers through one API, without a direct GDS contract or certification. Access starts with a short kick-off call.
How does a flight booking work end to end?
Search, validate the selected itinerary and price, add traveller details, create the booking, issue the ticket, then retrieve or cancel the booking. Each response returns a tracking_id that you pass to the next call.
Can I sell baggage, seats and meals?
Yes. The Flight API has separate endpoints to read and update baggage options, seat maps and seat selections, and meal options, alongside a branded-fare endpoint for fare families.
How is the Flight API priced?
Fares are the supplier net fare plus a fixed markup per passenger — USD 5 on Starter, USD 3 on Growth and USD 2 on Enterprise. It is a flat amount, never a percentage commission, and the price returned at validation is final.
What is a flight booking API?
A flight booking API lets a travel platform search live airline fares, confirm the price, create a reservation and issue the e-ticket from its own website or app. Unlike a flight search or flight data API, it completes the sale, so the booking, the customer and the margin stay with you.
Can the Tripgic flight API issue tickets, or does it only show fares?
It issues tickets. After validation and traveller details, the create-booking call makes the reservation and the issue-ticket call issues the e-ticket over the API, with no manual ticketing step on your side.
How long does flight booking API integration take?
Sandbox credentials are issued after a short kick-off call, and most teams reach a working sandbox integration in days rather than months. A direct GDS connection usually takes 6–12 months because each GDS needs its own contract and certification.
Is there a free flight booking API to test with?
Yes for testing: Tripgic issues free sandbox credentials before activation so you can build and validate the full search-to-ticket flow. Live booking runs on a paid plan with a one-time activation and a flat per-passenger markup.
What replaces the Amadeus Self-Service Flight Offers Search API?
Amadeus closed its Self-Service APIs on 17 July 2026. In Tripgic, Flight Offers Search maps to /flight/search, Flight Offers Price to /flight/validate and Flight Create Orders to the update-travellers, create-booking and issue-ticket calls, with Sabre, Travelport, NDC and low-cost carriers in the same results.
Ready to sell flights from one API?
Book a short kick-off call, get sandbox credentials at no charge, and build against the same schema you'll use in production.