Amadeus API Shutdown: Your 2026 Migration Guide

Avatar photo Tripgic Team,

The Amadeus API shutdown is set for July 17, 2026. On that day, self-service keys stop working. As a result, any app built on them will fail. This guide shows you how to migrate safely and on time.

The change sounds scary. However, a clear plan makes it simple. First, you will learn what the shutdown means. Then, you will follow a step-by-step migration path.

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. Therefore, your search and booking calls will return errors.

Enterprise customers are not affected. But self-service users must act. You can confirm the details in this guide to the Amadeus shutdown.

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 bookings.

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.

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 an aggregator, a direct airline NDC link, or another provider. 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.

Final Thoughts

The Amadeus 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