Amadeus Enterprise APIs and NDC Integration Guide

Amadeus Self-Service was decommissioned on 17 July 2026. New integrations should be evaluated through the current Enterprise API Portal and relevant Amadeus Travel Platform / NDC product surfaces. This guide does not treat legacy Self-Service endpoints as current contracts.

Provider companion snapshot

Access and onboarding

The Enterprise Portal provides request-based access to more than 100 Enterprise APIs for organizations with scale requirements, with sandbox/testing and consultant-supported onboarding. Capability depends on entitlement, commercial agreement and customer setup.

Keep versioned configuration such as:

provider = amadeus-enterprise
product_family = air | hotel | booking-management | ...
content_source = edifact/gds | ndc | other
credential_scope = provisioned contract
environment = test | production

Capability boundary

Do not model Amadeus as one flight-search endpoint:

Enterprise product family
   -> entitlement
   -> shopping/content contract
   -> source-specific offer/reference
   -> booking/order
   -> servicing / exchange / cancel

For travel sellers, Amadeus exposes NDC content that can be searched, booked and managed through the Travel Platform. NDC and traditional GDS content can normalize into one itinerary UI, but servicing capabilities must not be assumed identical.

Canonical mapping

Provider identity is not domain identity:

canonical itinerary != Amadeus offer/reference
canonical order      != provider booking/order reference
canonical traveler   != provider passenger reference

Preserve source lineage, offer expiry, servicing capability and content source alongside normalized fields.

Polling and pagination

The Enterprise portfolio contains multiple API families. Pagination or asynchronous polling should only be implemented when the specific endpoint contract defines it. Do not automatically carry generic helpers from the retired Self-Service product into new Enterprise integrations.

Rate limits and quotas

The public Enterprise landing page does not expose one account-independent QPS/quota for the full portfolio. Verify quota and concurrency in the active product contract, sandbox and entitlement.

Keep limits by:

product + operation + environment + credential scope

rather than a provider-wide constant.

Freshness, cache and offer lifecycle

Flight/NDC shopping output is not transaction truth. Price, availability, ancillaries and eligibility may change before booking. Preserve source, offer/reference ID, observation time, expiry where available, itinerary fingerprint, price components, fare/brand and ancillary context.

Idempotency and ordering

A booking/order create timeout is not proven failure. Create an internal attempt ID, retain provider correlation/reference data and retrieve/reconcile ambiguous outcomes.

CREATING -> CONFIRMED
         -> REJECTED
         -> UNKNOWN -> RETRIEVE/RECONCILE

Never blindly duplicate a create while state is UNKNOWN.

Error taxonomy

Useful internal classes include:

• AMADEUS_AUTH_OR_ENTITLEMENT
• AMADEUS_VALIDATION
• AMADEUS_NO_CONTENT
• AMADEUS_OFFER_EXPIRED
• AMADEUS_PRICE_CHANGED
• AMADEUS_RATE_LIMIT
• AMADEUS_UPSTREAM
• AMADEUS_TIMEOUT
• AMADEUS_BOOKING_UNKNOWN
• AMADEUS_SERVICING_UNSUPPORTED

Do not expose provider errors directly as UI business state.

Booking / NDC Offer & Order lifecycle

NDC is more than itinerary plus price. Preserve offer ownership and selected-offer state, then retain order/servicing lineage after booking.

SHOP
 -> OFFER
 -> SELECT / VALIDATE
 -> ORDER / BOOK
 -> RETRIEVE
 -> CHANGE / CANCEL / SERVICE

Manage carrier/content-source differences with an explicit capability matrix.

Failure modes

• treating retired Self-Service as current,
• assuming GDS and NDC servicing parity,
• dropping offer/reference lineage during normalization,
• booking an expired offer,
• duplicate order after ambiguous timeout,
• treating product-specific quota as a universal Amadeus limit.

Observability

Measure by product/source:

• auth/entitlement rejection,
• search latency and result count,
• source/content mix,
• offer age,
• revalidation/price-change rate,
• booking success/unknown rate,
• servicing failure,
• reconciliation gaps.

Go-live checklist

• current Enterprise entitlement verified
• no historical Self-Service dependency
• test/prod configuration separated
• source/content capability matrix available
• provider references preserved
• freshness/offer expiry modeled
• UNKNOWN booking recovery implemented
• retries are operation-specific
• NDC/GDS servicing differences tested
• quotas verified from active contract
• observability segmented by product/source

Historical note

Use the Amadeus Self-Service migration guide only for legacy migration context. It is not the source of truth for a new integration.