Amadeus Self-Service: Retired API Platform and Migration

This profile covers the retired Self-Service product, not the whole Amadeus business. The official portal announces that Self-Service was decommissioned on 17 July; the current site serves Enterprise APIs. The platform profile's discontinued status applies only to Self-Service.

New projects need to evaluate Enterprise access and its commercial agreement separately. A historical API example is not evidence of current credentials, entitlement, coverage or pricing.

What the former product covered

The Self-Service model separated property identity, cached discovery, live offer search, price confirmation and order creation. These boundaries remain useful when migrating an adapter; the retired service is not a new production dependency.

Authentication and access

Historical integrations used short-lived OAuth client-credentials tokens. Inventory all applications, token-refresh jobs and secret references before replacing an adapter. Confirm current access with Amadeus rather than retrying a retired entitlement indefinitely.

Hotel identity before availability

The former hotel flow resolved property IDs before searching stay-specific offers. Preserve the canonical property mapping when changing suppliers; a provider ID is not a universal hotel identifier.

Search, reprice and order

The legacy flight flow separated Flight Offers Search, Flight Offers Price and Flight Create Orders. During migration, keep offer provenance, price expiry and booking-attempt identity explicit. Existing orders require a servicing plan even after new searches move elsewhere.

Cached discovery and coverage

Inspiration and cheapest-date data had a different freshness and coverage contract from live shopping. Historical carrier or fare limitations describe the old product, not the current Enterprise inventory.

Migration boundary

Map each former capability to a confirmed replacement, measure coverage and price differences, and reconcile outstanding bookings before removing the adapter. Enterprise onboarding and replacement-provider contracts must be evaluated independently.

The linked integration guide provides the detailed migration workflow. The official-document link now points to the Enterprise portal and its Self-Service retirement announcement, not to a still-operating Self-Service developer programme.