Amadeus API Integration for Travel Agencies: What to Expect From Contract to Go-Live

An Amadeus API integration connects your travel agency's website or booking system to Amadeus, one of the largest global distribution systems, so you can search live flight fares, create bookings and manage tickets automatically. The work has two sides: a commercial side, where your agency agrees access and receives credentials, and a technical side, where your booking software is connected, tested and approved for live use. Understanding both before you start saves weeks of back-and-forth.

What Amadeus provides to a travel agency

Amadeus is a global distribution system (GDS): a large network that aggregates airline schedules, fares and seat availability and makes them bookable by travel sellers. Through its APIs, an agency's software can ask questions such as which flights are available between two cities on a given date, what they cost under which fare rules, and whether a selected itinerary can still be booked at that price.

For an online agency, that means customers can search and book flights on your website in real time, while your team keeps control of pricing, ticketing and after-sales work. If you are still comparing distribution options, our explainer on GDS vs NDC for travel agencies sets out how traditional GDS content differs from airlines' direct NDC offers.

Choosing your Amadeus API integration route

Amadeus offers more than one way in, and the right route depends on the size of your business, whether you issue tickets yourself and what your local Amadeus team agrees with you. Broadly, agencies meet two routes.

• Self-service developer access, aimed at developers and smaller businesses, with a public sign-up, documentation and a test environment. It is a quick way to explore the data, but it has narrower scope and ticketing usually needs to be arranged separately, for example through a consolidator.
• Enterprise access, arranged through the Amadeus commercial team that covers your market. This is the route most established agencies take. It is tied to a commercial agreement, your agency's Amadeus office identity and your ticketing arrangements, and it typically offers broader functionality for booking and servicing.

Scope, terms and any usage-related fees are set in your agreement, so confirm them directly with Amadeus rather than relying on assumptions. Ask in particular which booking and servicing functions are included, what testing and approval steps apply, and whether there are expectations about how many searches you make relative to bookings.

How a flight booking flows through the API

Whatever access route you use, a flight booking follows a similar sequence. Your booking engine guides the customer through each stage and calls Amadeus behind the scenes. For a broader view of how the pieces fit together, see how a flight booking engine works.

1. Search. The customer enters origin, destination, dates and passengers. The engine requests available itineraries and fares and displays them with your markup applied.
2. Price confirmation. When the customer picks an option, the engine re-checks the fare. Prices in search results can change quickly, so this step confirms the current price, fare rules and baggage before payment.
3. Passenger details and payment. The customer enters names exactly as they appear in passports, plus contact details, and pays through your gateway or agent wallet.
4. Booking. The engine creates the reservation in Amadeus, producing a passenger name record (PNR) with a booking reference the customer and your team can use.
5. Ticketing. The reservation is turned into an electronic ticket, either through your own accreditation or through a consolidator, within the ticketing time limit the airline sets.
6. After-sales. Changes, cancellations, voids and refunds are handled according to the fare rules and your agreement.

Booking is not the same as ticketing

New agencies are often caught out by the gap between a confirmed booking and an issued ticket. A PNR holds the seats, but the airline expects a ticket to be issued before a deadline. If that does not happen, the reservation can be cancelled automatically. Your process, whether automated or manual, must make sure every paid booking is ticketed in time, and your back office should flag any booking that is close to its deadline.

The stages of an Amadeus integration project

From the agency's point of view, the project usually moves through a predictable set of stages. Timelines vary, mostly because of commercial and approval steps rather than coding.

Test scenarios worth covering

Testing only a simple one-way adult booking gives false confidence. Before you ask for live access, work through a wider set of cases: return and multi-city itineraries, mixed passenger types including children and infants, domestic and international routes, fares with and without checked baggage, a booking that fails because the fare has changed, and a cancellation made shortly after booking. Record what happened in each case so that problems can be reproduced and fixed.

Preparing your agency before you start

The smoothest integrations happen when the agency has its own house in order first. Gather the following before the technical work begins, so that nobody is left waiting on a document or a decision.

• Company registration, travel agency licence and any accreditation documents your Amadeus team asks for.
• A clear decision on how tickets will be issued, either through your own accreditation or a named consolidator.
• Your markup policy for flights, including whether it differs by route, airline, cabin or customer type.
• The payment methods you will accept, and how a failed payment or a failed booking will be handled.
• A named person in your team who owns the integration and can answer questions from Amadeus and your developer.

Technical considerations that affect results

A working connection is only the start. The quality of the integration shows up in speed, accuracy and how gracefully it handles problems.

• Search efficiency. Flight searches are relatively heavy requests. Sensible caching of non-price data, avoiding duplicate requests and limiting automated searches keep the system fast and respect any usage expectations in your agreement.
• Fare accuracy. Taxes, fees, baggage allowances and fare rules must be shown clearly and consistently with what the airline will apply. Mismatches lead to disputes.
• Passenger data. Names, dates of birth and passport details must be captured in the format airlines require, especially for international routes.
• Error handling. Seats can sell out between search and booking. The engine should tell the customer clearly and offer alternatives rather than failing silently.
• Reconciliation. Your back office should match payments, bookings and tickets so that nothing is paid but unticketed, or ticketed but unpaid.

Mistakes that slow agencies down

A few problems come up again and again. Credentials are requested in a developer's personal name and later have to be reissued. Markups are applied to the base fare but not shown consistently against taxes. Ticketing deadlines are tracked in a spreadsheet rather than in the back office. Customer support staff are not trained on what a PNR is or how to read one. Each of these is easy to avoid when it is planned for at the start.

Costs to plan for

There are several separate cost areas in a GDS integration, and it helps to budget for them individually. Your agreement with Amadeus sets any fees or incentives that apply to your agency. Ticketing may involve consolidator fees if you are not accredited. Your booking software has its own cost, and you will need reliable hosting. Payment gateways charge their own processing fees. None of these should be hidden inside one another, so ask each provider to state its charges clearly.

Combining Amadeus with other flight sources

Many agencies connect more than one flight source. Some add a second GDS such as Sabre for coverage in particular markets, and some add an aggregator such as Duffel for direct airline content. A booking platform that can combine results from several sources, remove duplicates and apply one set of markup rules gives customers a single, clean list of options while you choose which source to book through.

Next steps

TravelBookingPanel's flight booking software supports Amadeus, Sabre and Duffel connections, using contracts and API credentials held in your agency's own name. It comes with full source code on a one-time licence, installed on your own domain and server, with no monthly fee or booking commission. Supplier, hosting and gateway fees remain separate. See the plans on our pricing page or contact us to discuss your Amadeus setup.