Golam Shahrier
Amadeus closed its self-service API on 17 July 2026. Its developer site now states that the self-service portal “has been decommissioned” and that the site “is for Amadeus Enterprise API Portal only”. If your app was built on self-service keys, its flight search and booking no longer work, and you need an alternative with a sandbox you can test in today.
This guide covers what closed, who it affects, the main alternatives side by side, and how to move a broken app over quickly. Facts about Amadeus and Duffel come from their own websites, read on 1 October 2026 and linked in the sources at the end.
What Amadeus Closed, and What It Kept
Amadeus closed only the self-service developer portal. That was the route where a developer could sign up alone, get a key and start testing for free. New self-service sign-ups were paused before the closure, and the portal itself was decommissioned on 17 July 2026.
What remains is the Amadeus Enterprise API Portal. Its site describes access to over 100 Enterprise APIs, which you can test in an Enterprise sandbox after you request access. A travel consultant then guides you through the portfolio and helps you choose an offer.
That is a sales process rather than a sign-up form. For a large business it may be the natural next step. For a solo developer or an early startup, it is usually the reason to look elsewhere. The independent PhocusWire report on the shutdown covers the background.
Who the Shutdown Hit
The free self-service tier existed for small teams, so the closure lands on them:
- Travel startups that built their first product on a free key.
- Solo developers running side projects and tutorials.
- Small OTAs without an Enterprise contract.
- Any app, at any size, that still calls a self-service key.
If you have an Enterprise contract, nothing changed for you. Everyone else needs a new source of flight content, and ideally one that does not put them back in the same position the next time a single supplier changes its terms.
Amadeus Self-Service API Alternatives Compared
Four main paths replace self-service. They differ in what you can sell, how fast you can start, and how much supplier risk you carry.
| Alternative | Example | Free to test? | Suits | Trade-off |
|---|---|---|---|---|
| Multi-product travel API | Tripgic | Yes — sandbox credentials at no charge after a short call | Teams that want flights, hotels and more from one API | You work through the provider’s supplier mix |
| Developer-first flight API | Duffel | Yes — test mode with the Duffel Airways test airline | Flight-focused apps that want a quick developer start | Narrower product range than a multi-product API |
| Amadeus Enterprise | Amadeus | Enterprise sandbox, after an access request | Larger businesses that want to stay with Amadeus | Higher commitment; starts with a consultant |
| Direct airline NDC | One link per airline | Varies by airline | High-volume sellers with engineering capacity | One connection to build and maintain per airline |
For a wider list, including hotel bedbanks, affiliate APIs and free data APIs, see our guide to free travel APIs.
What to Look for in a Replacement
The old self-service tier was easy to start and cheap to run. A replacement should keep the first part and be honest about the second.
- A real sandbox. You should be able to build search, booking and cancellation before you pay anything.
- Coverage in one API. If you plan to add hotels, cars or activities later, choose a provider that already has them, so you migrate once.
- Clear live terms. Ask in writing how live bookings are charged, what search limits apply, and how long activation takes.
- Support during the switch. A migration raises questions the documentation does not answer.
For the full checklist, read our guide on how to choose a travel API provider.
How to Move a Broken App Over Fast
If your app is down today, speed matters more than a perfect plan. Five steps, in order:
- List every Amadeus call your app made. Flight search, pricing, booking, seat maps, airport lookups — each one needs a replacement.
- Get sandbox access from your new provider. With Tripgic, sandbox credentials are issued right after a short kick-off call, with no commitment to start.
- Rebuild the calls. Field names and structures differ between providers, so map each one rather than renaming in bulk.
- Test search and booking end to end. Include a cancellation, a sold-out flight and a price change.
- Switch traffic once the results match. Start with a small share of users if you can, then move the rest.
Our travel API integration timeline shows how long each phase usually takes, and our Amadeus API shutdown migration guide walks through the field mapping in more detail.
Why One API for Many Suppliers Lowers the Risk
The self-service closure is a reminder that a single supplier can change its terms at any time. Replacing one single-supplier API with another leaves that risk where it was.
A multi-product travel API connects you to many suppliers through one integration. If one source changes, the others are still there, and adding a product does not mean another migration. Tripgic, for example, sells flights from Amadeus, Sabre and Travelport, NDC and 67 low-cost carriers, alongside hotels, cars, activities and more, through one API. Read what a travel API aggregator is for how the model works.
Final Thoughts
The free Amadeus self-service tier is gone, and it is not coming back. The fastest way back to a working product is a provider with a free sandbox: rebuild there, test with your own searches, and switch once everything matches.
