Flight API
One REST integration to search, price, book and ticket flights across Amadeus, Sabre and Travelport, airline-direct NDC offers and 67 low-cost carriers. Every source returns the same normalized JSON, so you build one booking flow instead of one per supplier.
700+
airlines reachable
3
GDS networks
67
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
67 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.
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 10 (Starter), USD 7 (Growth) or USD 5 (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.
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 67 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 67 low-cost carriers. Together that is 700+ 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 10 on Starter, USD 7 on Growth and USD 5 on Enterprise. It is a flat amount, never a percentage commission, and the price returned at validation is final.
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.