The Amadeus self-service API shut down on 17 July 2026. Amadeus disabled every self-service API key and closed the developer portal, so any app still built on those keys can no longer search or book. The fix is a new provider. The closest match to self-service is a multi-product travel API such as Tripgic; the other paths are a developer-first flight API, Amadeus Enterprise, another GDS, or direct airline NDC.
This guide covers what closed, who it hit, the alternatives side by side, how each old endpoint maps to a new one, and a step-by-step migration plan. Facts about Amadeus, Duffel and Sabre come from their own websites and from PhocusWire’s report, read on 10 October 2026 and linked in the sources at the end. The Amadeus decommission notice was checked again on 26 October 2026.
What Happened to the Amadeus Self-Service API
Amadeus closed the self-service section of its Amadeus for Developers portal on 17 July 2026. That was the route where a developer could sign up alone, get a key in minutes and start testing for free. On that date, every self-service key was disabled, and the portal became inaccessible.
The developer site now opens with a single announcement: “Amadeus for Developers self-service portal has been decommissioned on July 17th, this website is for Amadeus Enterprise API Portal only.”
Amadeus did not give a reason in its letter to users. A spokesperson told PhocusWire: “We are decommissioning only the self‑service section of the Amadeus for Developers portal. The Enterprise portal and Enterprise APIs remain fully available.”
So the Amadeus API business did not close. The free, developer-first door into it did. Search and booking calls made with a self-service key now return errors, and they will keep doing so. There is no plan to bring the tier back, so the only fix is a new source of content.
Amadeus Shutdown Timeline: Key Dates
The shutdown came in three stages over about five months.
| Date | What happened |
|---|---|
| February 2026 | Amadeus told self-service users in a letter that the portal would close. PhocusWire reported it on 9 February |
| March 2026 | New self-service registration was paused. No new keys were issued after this |
| 17 July 2026 | The self-service portal was decommissioned. All existing self-service keys were disabled and stopped returning data |
| Today | The developer site serves the Enterprise API Portal only. Access starts with a request and a travel consultant |
If your platform still calls the self-service API, its searches and bookings are failing now, not later. Every week of delay is a week of lost bookings, so the first job is to get a working sandbox, not to plan the perfect replacement.
Is Amadeus Down? Self-Service vs the GDS
Many people search “Amadeus down” or “Amadeus closing” after their app stops working. The answer is no, and the difference matters.
| Status since 17 July 2026 | |
|---|---|
| Amadeus self-service APIs | Closed for good. Keys disabled, portal gone |
| Amadeus Enterprise APIs | Open. Access by request, contract and certification |
| The Amadeus GDS used by travel agents | Running as before. Agents still book through it |
| Amadeus as a company | Operating normally |
If your app returns authentication errors or empty responses from an Amadeus self-service endpoint, that is the shutdown. Checking a status page or waiting will not help. The keys will not be switched back on.
If you are a travel agent working in an Amadeus terminal, nothing in this guide affects you. This change hit developers who built software on the free self-service tier, not the agencies that use the Amadeus GDS every day. For what a GDS is and how agents use it, see our guide to GDS for travel agents.
Amadeus API Key Not Working? Here Is Why
If you created your key by signing up on Amadeus for Developers, it was a self-service key. Amadeus disabled every one of those keys on 17 July 2026, when it decommissioned the self-service portal. That is why token requests and API calls made with it now fail, in test and in production alike.
Three things follow from that:
- It is not your code. Regenerating the secret, creating a new app or changing the host will not help, because Amadeus switched off the self-service keys themselves.
- There is no new key to sign up for. Registration was paused in March 2026 and the portal is gone. The developer site now points only to the Enterprise API Portal, where access starts with a request and a travel consultant.
- Enterprise credentials are a different thing. If your company holds an Amadeus Enterprise contract, its credentials were not affected. Ask your account manager, not the developer site.
For everyone else, the practical step is a provider that issues sandbox credentials quickly, so search and booking can be rebuilt this week. Tripgic issues them right after a short kick-off call, with access to Amadeus, Sabre and Travelport content through one API. The alternatives below compare all five options.
What Amadeus Closed, and What It Kept
Amadeus closed only the self-service developer portal. What remains is the Amadeus Enterprise API Portal. The developer site describes “over a 100 Enterprise APIs” that you can test in an Enterprise APIs 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, not a sign-up form. Enterprise customers kept their access without interruption. Amadeus told Enterprise customers who also used self-service APIs to contact their account managers and move those parts across.
According to AltexSoft, the gap between the two tiers is wide:
| Self-service (closed) | Enterprise (open) | |
|---|---|---|
| Getting in | Sign up, register an app, get a key | Request access, talk to a consultant, sign a contract |
| API style | REST and JSON | Mostly SOAP, with some REST |
| Content | Public fares only; no American Airlines, Delta, British Airways or low-cost carriers | Broader inventory, including negotiated fares |
| Free testing | 1,000–10,000 free calls per API each month | Enterprise sandbox, after approval |
| Who it suited | Startups and solo developers | Accredited, established travel sellers |
For a large business, Enterprise may be the natural next step. For a solo developer or an early startup, it is usually the reason to look elsewhere. Our Amadeus API guide covers the Enterprise path in full: requirements, certification, SOAP and pricing.
What the Self-Service APIs Did
The self-service catalogue was broad. Amadeus’s own Python SDK, now archived on GitHub, lists the calls it supported. They fall into six groups:
| Group | Self-service APIs |
|---|---|
| Flight shopping | Flight Offers Search, Flight Offers Price, Branded Fares Upsell, Flight Availabilities, Flight Inspiration and Cheapest Date Search |
| Flight booking | Flight Create Orders, Flight Order Management (retrieve and cancel), SeatMap Display |
| Hotels | Hotel List, Hotel Search, Hotel Booking, Hotel Ratings |
| Activities and transfers | Tours and Activities, Transfer Search, Transfer Booking and Cancellation |
| Reference data | Airport and City Search, Airline Code Lookup, Airport Routes, Check-in Links |
| Flight data and analytics | On-Demand Flight Status, Flight Delay Prediction, Air Traffic Analytics, Trip Purpose Prediction |
Two practical points follow. First, the official SDKs for Python, Node.js and Java are archived, so they are read-only and will get no fixes. Second, the self-service documentation went with the portal. The old Flight Offers Search reference page now sends you to the developer site’s home page. What you find in search results are copies and tutorials, not a live reference you can build on.
This list is also your migration checklist. Most apps used three to six of these calls, not all of them. Mark the ones yours used, because each one needs a replacement, and some groups need a different kind of provider.
Who the Shutdown Hit
The free self-service tier existed for small teams, so the closure lands on them hardest:
- Travel startups that built their first product on a free key and planned to scale later.
- Solo developers running side projects, tutorials and portfolio apps.
- Small OTAs that sold flights without an Enterprise contract.
- AI and agentic travel apps that used the free tier to test booking flows.
- Any app, at any size, that still calls a self-service key.
The timing drew criticism. Travel consultant Martijn van der Voort, quoted by PhocusWire, called the timing “wild”: just as AI agents start to reshape how people book travel, experimenting with Amadeus now needs enterprise approval and budget. If you are building one of those agents, our AI travel agent API guide covers what such an app needs from a booking API.
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.
If Your App Is Down Right Now
A migration under pressure still has to be tested, or the first live booking becomes the test. Three things keep it short.
First, rebuild the calls your users hit most. That is flight search, pricing and booking. Seat maps, airport lookups and the rest can follow a week later. A working search with a simple booking flow beats a broken app with every feature planned.
Second, use a provider with a free sandbox. You want to build and test today, without signing a contract first. With Tripgic, sandbox credentials are issued right after a short kick-off call, with no commitment to start, so you can rebuild search and booking the same week.
Third, tell your users. A short status message, “flight search is being upgraded”, costs nothing and keeps trust while you rebuild. Silence while search returns errors looks like the product has been abandoned.
Our guide to free travel APIs compares what other providers offer for free, including hotel bedbanks, affiliate APIs and free data APIs.
Amadeus Self-Service API Alternatives Compared
Five 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 | Flight-focused apps | Narrower product range |
| Amadeus Enterprise | Amadeus | Enterprise sandbox, after an access request | Larger businesses that want to stay with Amadeus | Contract, accreditation and certification first |
| Another GDS directly | Sabre, Travelport | Developer programmes with test access | Teams with GDS skills that want one network | One contract and one certification per GDS |
| Direct airline NDC | One link per airline | Varies by airline | High-volume sellers with engineering capacity | One connection to build and maintain per airline |
Each path is explained below. The facts about each company come from its own website, and none of this is a ranking. The right choice depends on what your app sells and how big your team is.
Tripgic: the closest match to self-service
Self-service gave a small team three things: one REST API, a free place to test, and flights and hotels in the same catalogue. Tripgic keeps all three, and adds content the free tier never had.
Tripgic gives developers sandbox access to Amadeus, Sabre and Travelport content, plus NDC and low-cost carriers, through one normalized REST API, without a direct GDS contract or certification. In practice that means:
- Flights from every source in one search. The three GDS networks, NDC airlines and 100+ low-cost carriers — 800+ airline and low-cost connections in total. Self-service returned public fares only, with no low-cost carriers.
- Hotels in the same API. 2M+ hotel properties from 50+ suppliers, so the old Hotel Search and Hotel Booking calls have a place to land.
- More than flights and hotels. 73 endpoints across 8 product families, from activities and transfers to trains, tour packages, eSIM and visas. Every one returns the same JSON envelope — see the API documentation.
- A free sandbox, quickly. Credentials are issued right after a short kick-off call, with no commitment to start.
- No GDS contract and no GDS certification queue. Tripgic already holds the connections, which is why going live takes days or weeks rather than 6–12 months.
- A fee that does not grow with your fares. A one-time activation, then the supplier’s net fare plus a flat fee per transaction, never a percentage. Plans are on the pricing page.
The rest of this guide shows how the old calls map to Tripgic, endpoint by endpoint, and what changes in your code.
Developer-first flight API (Duffel)
Duffel focuses on flights and offers a test mode, so a flight-only app can start quickly. Its range is narrower than a multi-product API.
Amadeus Enterprise
This path keeps you on Amadeus with wider content, including negotiated fares. It also means a request, a consultant, a contract, IATA or ARC accreditation in most cases, a mostly SOAP build and a certification review. Our Amadeus API guide walks through each step.
Sabre or Travelport directly
The other two big GDS networks still let developers test: Travelport issues trial credentials, and Sabre runs a developer programme with sandbox access. Going direct still means one contract and one certification per network. See our Sabre API guide, our Travelport API guide and the Amadeus vs Sabre vs Travelport comparison.
Direct airline NDC
NDC lets you connect to an airline’s own offers. It gives rich content, but every airline is a separate build, contract and test cycle. It suits high-volume sellers with a large engineering team. Our NDC API integration guide explains the work involved.
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. Check five things before you commit:
- A real sandbox. You should be able to build search, pricing, 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, not twice.
- Clear live terms. Ask in writing how live bookings are charged, what search limits apply, and how long activation takes.
- Ticketing. Self-service needed a consolidator agreement before you could issue tickets in production. Ask who issues tickets on the new path, and whether you need your own IATA accreditation.
- Support during the switch. A migration raises questions the documentation does not answer. A named contact saves days.
Do not just swap one single-supplier API for another. The Amadeus closure shows that one supplier can change its terms at any time, with five months’ notice. For the full list of checks, read our guide on how to choose a travel API provider.
Amadeus to Tripgic: The Endpoint Map
Most self-service booking calls have a direct match. The table below maps the Amadeus self-service calls, as named in its SDK, to Tripgic endpoints, as listed in the Tripgic API documentation. Every Tripgic endpoint is a POST.
| Amadeus self-service API | Tripgic endpoint | Notes |
|---|---|---|
| Flight Offers Search | /flight/search |
Returns options and a tracking_id |
| Branded Fares Upsell | /flight/branded-fare |
Fare families for a chosen flight |
| Flight Offers Price | /flight/validate |
Confirms the itinerary and the final price |
| Flight Create Orders | /flight/create-booking |
Then /flight/issue-ticket to issue |
| Flight Order Management | /flight/cancel-booking and the booking details call |
Retrieve and cancel |
| SeatMap Display | /flight/get-seat-plan |
Then /flight/update-seat to select |
| Hotel Search | /hotel/search and /hotel/rooms |
Search by location, then one hotel’s rooms |
| Hotel Booking | /hotel/create |
Then /hotel/issue-voucher |
| Tours and Activities | /activity/search |
Then /activity/create-booking |
| Transfer Search and Booking | The Transfer API’s search and create calls | Six transfer endpoints in total |
| Flight Status, Delay Prediction, Analytics | No match | These are data products, not booking calls |
Two differences matter more than the names. Tripgic has separate calls for baggage and meal options, and for adding them to a booking, so you can sell ancillaries inside the same flow. And the last row has no match by design: flight status and analytics come from flight data APIs, not booking APIs. If your app used them, plan a separate data provider for that part.
How Authentication Changes
Authentication is the first thing that breaks in a migration, and it changes completely.
Amadeus self-service used OAuth 2.0. You created an app in the portal, got a client ID and a client secret, and exchanged them for a short-lived access token. The SDKs refreshed that token for you. Calls ran against a free test host first, then a pay-as-you-go production host.
On Tripgic, the base URL, the authentication method and your credentials are all issued to you during onboarding. They are not published in the public documentation. Every request goes over HTTPS as a POST with a JSON body, and every product family returns the same response envelope.
What this means for your code:
- Remove the token flow. Delete the code that requested and refreshed Amadeus tokens. Do not leave it in “just in case”.
- Store the new credentials as secrets. Use environment variables or a secrets manager, never source code.
- Keep sandbox and live separate. Use separate credentials and a configuration switch, so a test booking can never reach a live supplier.
Old vs New Request: A Real Example
The shape of a search request changes more than its content. Here is a one-way search for one adult, before and after.
The old Amadeus self-service call was a GET with query parameters, as shown in its SDK:
// Amadeus self-service: GET /v2/shopping/flight-offers
{
"originLocationCode": "DAC",
"destinationLocationCode": "DXB",
"departureDate": "2026-11-30",
"adults": 1
}
The Tripgic call is a POST to /flight/search with a JSON body. These field names come from the example in the Tripgic documentation:
// Tripgic: POST https://YOUR_BASE_URL/flight/search
{
"journey_type": "OneWay",
"segment": [{
"departure_airport_type": "AIRPORT",
"departure_airport": "DAC",
"arrival_airport_type": "AIRPORT",
"arrival_airport": "DXB",
"departure_date": "2026-11-30"
}],
"travelers_adult": 1,
"travelers_child": 0,
"travelers_infants": 0,
"booking_class": "Economy",
"partner_id": "1",
"language": "en"
}
Three changes stand out. The trip is a list of segments, not flat origin and destination fields. Children and infants are always stated, even as zero. And the search returns a tracking_id, which you pass to /flight/validate and to the booking steps after it. That one ID ties search, pricing, booking and ticketing together, so your code passes an ID along rather than re-sending a whole offer.
Step-by-Step Amadeus Migration Plan
Seven steps, in order. The first four can start today.
- Audit your app. Search your code for every Amadeus call. Use the self-service list above to name each one, and note which screens depend on it.
- Choose a provider. Match your list to what each provider covers. If you used hotel or activity calls, a flight-only API will leave gaps.
- Get sandbox access. Book the call, pass the short check, and get credentials. Build nothing against production until search, pricing and booking work in the sandbox.
- Rebuild the core calls. Start with search, pricing and booking. Map each field by hand, using the endpoint map above, rather than renaming in bulk.
- Rebuild the rest. Seat maps, cancellations, hotels and ancillaries. Add the new options, such as baggage and meals, if you want to sell them.
- Test end to end. Include a cancellation, a sold-out flight, a price change between search and booking, and a child and infant passenger. These four cases break most first versions.
- Go live in stages. Move a small share of users first, compare results and errors for a few days, then move the rest.
Activation of a Tripgic account usually takes 3–5 business days, so start step 3 while you do steps 1 and 2. Our travel API integration timeline shows how long each phase usually takes.

Common Amadeus Migration Pitfalls
Most migration problems come from a few mistakes. Watch for these before you go live.
- Treating a search price as final. Prices can move between search and booking. On Tripgic, the price returned at validation is final and can be shown to your customer as-is, so show that price at checkout, not the search price.
- Field mismatches. The new API names and nests fields differently. Map each one with care, especially passenger types and dates.
- Date and currency formats. A small format gap can break a booking. Check every date field and read the currency on every price.
- Error handling. The new API returns different error codes and messages. Update your checks, and log the
tracking_idwith every error so support can trace it. - Search volume. Live terms often include a look-to-book ratio, the number of searches allowed per booking. Cache common searches and avoid firing a search on every keystroke.
- Leftover Amadeus code. Remove the old client, tokens and keys once you switch, so nobody debugs the wrong integration later.

What Switching Costs
Testing is free on most paths. Costs start when you take live bookings, and each provider charges in a different way. Compare the model first, then the numbers at your expected volume.
| Path | How live use is charged |
|---|---|
| Tripgic | A one-time activation, then the supplier’s net fare plus a flat fee per transaction, never a percentage. Plans and fees are on the pricing page |
| Duffel | A fee per confirmed order, plus fees for some content and extras |
| Amadeus Enterprise | A negotiated monthly fee with a free request quota, then a charge per call, according to AltexSoft |
| Sabre or Travelport directly | Contracted terms per network, plus the cost of one certification each |
| Direct airline NDC | Separate terms per airline, plus the cost of building and running each link |
The cheapest option on paper is not always the cheapest in practice. A percentage grows with your fares, while a flat fee per transaction, like Tripgic’s, stays the same on a $200 fare and a $2,000 one. A fixed monthly fee only pays off at high volume. Write down your expected bookings per month and your average fare, then ask each provider for a quote on those numbers.
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 exactly where it was.
A multi-product travel API such as Tripgic connects you to many suppliers through one integration. If one source changes its terms, the others are still there, and your code does not change. Adding a product, such as hotels after flights, does not mean another migration either.
There is a time difference too. A direct GDS integration typically takes 6–12 months per network. Through an aggregator, the same content is live in days or weeks, because the GDS connections and certifications already exist. To learn how this model works, read what a travel API aggregator is.
Final Thoughts
The Amadeus self-service API closed on 17 July 2026, and it is not coming back. Amadeus itself is fine, and its Enterprise APIs are open to accredited businesses. But the free, sign-up-and-build door is gone.
The fastest way back to a working product is a provider with a free sandbox. Map your old calls, rebuild search, pricing and booking first, test the hard cases, and switch once everything matches. Then choose the path that lowers the risk of another forced move.
Tripgic connects you to Amadeus, Sabre, Travelport, NDC and low-cost carriers, plus 2M+ hotel properties, through one travel API. Get free sandbox access to start your migration today.
Golam Shahrier





