Amadeus API Shutdown: Your 2026 Migration Guide

Avatar photo Tripgic Team,

The Amadeus self-service API shuts down on July 17, 2026. On that day, self-service API keys stop working and the developer portal closes. Any app built on those keys will fail. This guide shows you exactly what breaks, your best alternatives, and a step-by-step plan to migrate safely and on time.

Key takeaways

  • The Amadeus for Developers self-service portal is decommissioned on July 17, 2026. After that date, self-service keys are deactivated.
  • Enterprise customers are not affected — only the self-service portal closes.
  • Your main alternatives are a travel API aggregator, a modern self-service flight API (such as Duffel), a direct airline NDC link, or the Amadeus Enterprise portal.
  • An aggregator is often the safest choice because it spreads risk across many suppliers, so you migrate once.
  • Start now. Most teams need a few weeks to map calls, test, and go live before the deadline.

What the Amadeus API Shutdown Means

Amadeus is closing its self-service developer portal. After July 17, 2026, the portal and its keys go dark. As a result, your search and booking calls will return errors.

Enterprise customers are not affected. Only self-service users must act. Amadeus confirmed the change in a letter to developers, first reported by PhocusWire in February 2026, and the notice now appears on the Amadeus for Developers site itself.

Amadeus Shutdown Timeline: Key Dates

The shutdown is not a single event. It rolls out in stages, so knowing the dates helps you plan.

  • February 2026: Amadeus announces the self-service portal will close.
  • Spring 2026: new self-service user registration is paused, so no new keys are issued.
  • July 17, 2026: the self-service portal is fully decommissioned. Existing API keys are deactivated and stop returning data.

If your platform still calls the self-service API after July 17, searches and bookings will fail. That is why the migration window matters.

Why You Should Not Wait

Migration always takes longer than planned. You must rebuild calls, test, and re-launch. Moreover, support queues fill up as the deadline nears.

So start now. An early move gives you time to test. As a result, you avoid a rushed switch that breaks live bookings.

Amadeus Self-Service API Alternatives

There is no single “correct” replacement. The right choice depends on your coverage needs, your team size, and how much supplier risk you want to carry. Here are the four main options.

Alternative Best for Trade-off
Travel API aggregator (e.g. Tripgic) Teams that want flights, hotels, and more from one API with supplier risk spread out You rely on the aggregator’s supplier mix, but you migrate only once
Modern self-service flight API (e.g. Duffel) Flight-only apps that want a fast, developer-friendly signup like the old Amadeus flow Narrower content than a full aggregator or GDS
Direct airline NDC High-volume platforms with engineering resources to manage each airline link Heavy to build and maintain one connection per airline
Amadeus Enterprise portal Larger businesses that can meet Amadeus enterprise requirements Higher commitment and onboarding than self-service

For a deeper look at flight-specific options, see our guide to Amadeus self-service API alternatives.

Step-by-Step Amadeus Migration Plan

  1. Audit your app. List every Amadeus endpoint you use.
  2. Choose a new provider. Pick one with wide coverage and fair pricing.
  3. Get sandbox access. Test the new API before you commit.
  4. Rebuild your calls. Map old fields to the new ones.
  5. Test end to end. Check search, pricing, and booking.
  6. Go live early. Switch traffic well before July 17, 2026.

This plan pairs well with our travel API integration timeline. It shows how long each phase really takes.

Six-step Amadeus migration: audit, choose, sandbox, rebuild, test, go live

How to Pick the Right Replacement

Do not just swap one supplier for another. Instead, think about long-term risk. A single supplier can change terms again.

  • Does it cover flights, hotels, and more?
  • Is the pricing clear and pay as you go?
  • Is there a sandbox and good documentation?
  • Will support help during the migration?

For the full list of checks, see our guide on how to choose a travel API provider. Additionally, an aggregator can spread your risk across many suppliers.

Migration checklist: coverage, pricing, sandbox, and support

Why an Aggregator Makes Migration Safer

An aggregator gives you one API for many suppliers. So if one source fails, others fill the gap. To learn how this works, read what a travel API aggregator is.

As a result, you migrate once and stay safe. You will not face another forced move when a single supplier changes its plan — which is exactly the situation the Amadeus shutdown created.

Common Amadeus Migration Pitfalls

Most migration problems come from a few mistakes. So watch for these before you go live.

  • Field mismatches: the new API names fields differently. Map each one with care.
  • Date and currency formats: small format gaps can break a booking.
  • Error handling: the new API returns different error codes. Update your checks.
  • Rate limits: test under heavy load before launch day.

Old vs New Request: A Simple Example

The shape of a search request often changes. Here is a simple before and after.

// Old Amadeus self-service style
{
  "originLocationCode": "DXB",
  "destinationLocationCode": "LHR",
  "departureDate": "2026-08-01",
  "adults": 1
}

// New aggregator style
{
  "origin": "DXB",
  "destination": "LHR",
  "depart_date": "2026-08-01",
  "passengers": { "adults": 1 }
}

The data is the same. However, the field names and structure differ. Therefore, you must map each field during the migration.

Amadeus API Shutdown FAQ

When does the Amadeus self-service API shut down?

The Amadeus self-service API portal shuts down on July 17, 2026. After that date, self-service API keys stop working and the portal closes.

Are enterprise users affected by the Amadeus shutdown?

No. Only the self-service portal closes. Amadeus enterprise customers keep their access through the enterprise portal.

What should I use instead of the Amadeus self-service API?

You can move to a travel API aggregator, a modern self-service flight API such as Duffel, a direct airline NDC link, or the Amadeus Enterprise portal. An aggregator is often safest because it spreads risk across many suppliers.

How long does an Amadeus API migration take?

It depends on your app size. Most teams need a few weeks to map calls, test, and go live. Start early to avoid a rushed switch.

Is the Amadeus self-service API still free to sign up for?

No. New self-service registration has been paused ahead of the July 17, 2026 shutdown, so you can no longer create new self-service keys. Use an alternative provider instead.

Final Thoughts

The Amadeus self-service API shutdown is fixed for July 17, 2026. Treat it as a deadline, not a surprise. Plan early, test well, and pick a provider that lowers future risk.

Tripgic connects you to many suppliers through one travel API. You can migrate fast and stay protected. Talk to our team to start your migration today.

Travel Tech