Amadeus API Integration
Reach the airlines distributed through Amadeus, MasterPricer low-fare search and the NDC content Amadeus carries, from one REST flight API. FlightOTA runs the Amadeus connection; you search, book, ticket and service bookings with the same calls you use for every other source.
Amadeus content without an Amadeus integration project
Amadeus is the GDS many agencies grew up on, and its MasterPricer search remains one of the broadest views of full-service airline fares. Integrating it directly means a commercial agreement, XML development and a certification project before the first live booking.
FlightOTA already queries Amadeus MasterPricer, and the NDC offers Amadeus distributes, inside the same POST /flights/search that shops Sabre, Travelport and our direct airline connections. Offers arrive as one JSON shape: price in integer minor units, times local to the airport, baggage per segment and fare rules on request. A booking held in Amadeus returns its Amadeus record locator as gds_reference beside our TFL- reference.
This page is for agencies and consolidators who know Amadeus and want its content inside a portal, booking engine or mid-office without maintaining the connection themselves.
An Amadeus booking, step by step
The calls are the Flights API's; the Amadeus specifics are the record locator and what MasterPricer returns.
- 01
Shop MasterPricer with every other source
One search request. Amadeus offers come back with the rest, and offers on the same flights share an itinerary_key so you can show one row per itinerary with its fare families behind it.
- 02
Confirm the price with the airline
POST /flights/offers/{offer_id}/price returns the airline's price now and, for offers marked conditions_on_request, the refund and change terms read from the filed fare rules.
- 03
Hold in Amadeus, issue from your deposit
The booking is created as held with hold_expires_at; issuing it before then pays the tickets from your FlightOTA deposit. gds_reference holds the Amadeus record locator.
- 04
Service and reconcile
Void, refund and reissue requests run through the booking; our desk handles those the airline does not answer by itself. Read GET /flights/bookings/{booking_ref} as the source of truth.
What the Amadeus integration covers
Amadeus content, sold through the Flights API and paid from your deposit.
- Amadeus MasterPricer low-fare search inside the unified flight search
- NDC offers distributed through Amadeus, in the same offer shape
- gds_reference: the Amadeus record locator on bookings held there
- Branded fare families, fare rules and baggage per segment
- Held bookings issued from your deposit before hold_expires_at
- Void, refund and reissue through the API, with our desk behind it
- Sandbox bookings on test systems before certification
- Your selling price next to your cost when markup rules are set
Amadeus integration questions
Related integrations and APIs
Put Amadeus content behind your own booking flow
We will show MasterPricer results, held bookings and the gds_reference on the sandbox, using your routes.