Guide · Travel APIs

Amadeus Self-Service API shutdown. What changed and where to migrate.

For years the Amadeus Self-Service portal was the default way for startups and developers to try flight and hotel APIs. It is now closed. Here is what that means and how to move a live integration.

Updated 7 min read By the Reservationhub team
Short answer

Amadeus decommissioned the Self-Service section of its Amadeus for Developers portal on 17 July 2026. Self-service API keys were disabled and new sign-ups closed, while Amadeus Enterprise APIs remain available under contract. Affected teams can move to Amadeus Enterprise, another GDS or NDC connection, or a unified travel API.

What happened to the Amadeus Self-Service APIs?

  • February 2026: Amadeus told Self-Service users by letter that it would pause new registrations and shut the self-service portal down, as reported by PhocusWire.
  • 17 July 2026: the Self-Service portal was decommissioned. Self-service API keys stopped working, and the official Amadeus for Developers SDK repositories on GitHub were archived the same day.
  • Unchanged: the Amadeus Enterprise portal and Enterprise APIs, which require a commercial agreement with Amadeus.

If your app still calls the self-service endpoints, it is already failing. Check your logs for authentication errors against the self-service token endpoint.

Who is affected?

  • Startups and small OTAs that ran production search or booking on self-service keys.
  • Travel apps, chatbots and AI agents that used Flight Offers Search, Flight Offers Price or Airport & City Search for live data.
  • Tools built on the official SDKs (Python, Node, Java, PHP and others), which are no longer maintained.
  • Teams that used the free test environment for prototypes and demos.

What are the alternatives?

OptionFits whenWatch out for
Amadeus EnterpriseYou want to stay on Amadeus and have volume to justify a contractSales process, commercial minimums, different API surface from self-service
Another GDS directly (Sabre, Travelport)You have a travel business and a dev team to certify itSeparate contract and certification per GDS (how GDSs work)
NDC aggregatorsYou mainly need network airlines with rich fares and ancillariesAirline coverage varies (what is NDC?)
Unified travel APIYou want GDS, NDC, low-cost and hotels behind one integrationCheck which suppliers are actually live for your markets
Metasearch or affiliate APIsYou only show prices and send users elsewhere to bookNo booking or ticketing, and you do not own the customer

Migration checklist

Self-service endpoints map onto the standard booking flow that every provider uses, so migration is mostly re-mapping rather than redesign:

Amadeus Self-Service APIStep in any travel API
Flight Offers SearchFlight search / shopping
Flight Offers PricePrice or revalidate an offer
Flight Create OrdersBook (create PNR or order)
Flight Order ManagementRetrieve and cancel
Seatmap DisplaySeat map / ancillaries
Hotel List, Hotel Search, Hotel BookingHotel search, rate check and booking
Airport & City SearchLocation autocomplete / reference data
  1. Inventory what you call: endpoints, request volume, and which responses your UI depends on.
  2. Swap authentication: self-service used OAuth2 client credentials; your new provider may use API keys or its own token flow.
  3. Re-map data models behind an adapter layer, so the next provider change stays in one place.
  4. Decide on ticketing: self-service booking did not issue tickets for you. If you need real ticketing, you need a provider or consolidator that handles it.
  5. Re-test servicing: cancellations and changes, not just search and book.

Moving to the TripGic travel API

The TripGic travel API from Reservationhub covers 700+ airlines across Amadeus, Sabre and Travelport GDS content, NDC and low-cost carriers, plus 2M+ hotels, transfers, cars and activities, in one REST/JSON contract with a sandbox. If you would rather not maintain a booking front end at all, see SaaS vs source code vs API.

Frequently asked questions

Is the Amadeus API still available?

Yes, through Amadeus Enterprise under a commercial agreement. Only the Self-Service section of the Amadeus for Developers portal was decommissioned on 17 July 2026.

Do my Amadeus self-service API keys still work?

No. Self-service keys were disabled when the portal was decommissioned on 17 July 2026, and new sign-ups are closed.

Is there a free replacement for Amadeus Self-Service?

Free options mostly cover search or affiliate links. Bookable flight and hotel APIs generally need a commercial agreement, because the provider carries supplier contracts, ticketing and payment risk.

How long does it take to migrate off Amadeus Self-Service?

For a search-and-book integration behind an adapter layer, re-mapping to one new provider is usually the fastest path. Adding real ticketing and servicing takes longer, because those were not part of most self-service integrations.

Are the official Amadeus SDKs still maintained?

No. The Amadeus for Developers GitHub organisation, including the Python, Node, Java and other self-service SDKs, was archived on 17 July 2026.

Replace your Amadeus self-service integration

Tell us which endpoints you used and we will map them to the TripGic API.

Talk to the API team

Sources

  1. PhocusWire — Amadeus to shut down self-service APIs portal for developers (9 February 2026)
  2. Amadeus for Developers on GitHub (archived 17 July 2026)
Chat on WhatsApp