Amadeus Enterprise APIs: GDS, NDC and Travel Platform Profile
Understand the current Amadeus Enterprise API Portal, Travel Platform and NDC content in the travel-distribution ecosystem.
Platform facts
- Platform type
- API
- Role / capability
- GDS · NDC · API
- Ecosystem layer
- Connectivity & Distribution · Booking / Transaction
- Turkey relevance
- Global / Turkey context
- Service status
- Active
- Ecosystem audience
- B2B · industry partners
- Business model
- Not yet verified
- Integration method
- API
- Company
- Not yet verified
- Parent company
- Not yet verified
- Direct supplier participation
- Not yet verified
- Developer documentation
- Yes
- Pricing / availability model
- Not yet verified
- Booking ownership
- Not yet verified
- Attribution model
- Not yet verified
Commercial models and integration paths may belong to different partner programmes; access and market eligibility depend on provider approval.
Sources for these facts
How is this entity connected?
Follow the same entity across integration, architecture, comparison, research and glossary layers. Links are generated from content metadata and topic similarity.
Amadeus Enterprise API Portal is the current API-access surface for travel companies with scale requirements. It exposes request-based access to Air, Booking Management, Hotel, Cars & Transfers and other Enterprise API families.
Ecosystem role
Amadeus spans GDS/distribution network, API connectivity and NDC aggregation/retailing roles. Travel sellers can access traditional and NDC-sourced content through the Amadeus Travel Platform.
Separation from Self-Service
Amadeus Self-Service was decommissioned on 17 July 2026. This profile covers the current Enterprise surface and should not be merged with the historical Self-Service profile.
Technical modeling
Keep product family, content source, entitlement, offer/reference and booking/order lineage distinct. NDC and traditional GDS content can normalize into one canonical itinerary while retaining source-specific servicing capability.
See the Amadeus Enterprise APIs integration guide.
Boundaries
The public portal does not define one universal quota, endpoint or authentication contract for the full Enterprise portfolio. The active commercial and technical entitlement remains the source of truth.
Evaluating this technology or provider approach?
We can assess integration, architecture and operational trade-offs against your requirements.
Sources
Related content
Amadeus Enterprise APIs and NDC Integration Guide
Design Amadeus Enterprise API Portal and Travel Platform/NDC integrations around access, entitlement, offer/order lifecycle, servicing, quota boundaries and observability.
Explore →Amadeus Self-Service: Retired API Platform and Migration
Legacy Amadeus Self-Service API scope, portal retirement and migration to separately contracted Enterprise access.
Explore →Amadeus Self-Service API Integration and Migration Guide
Operate and migrate Amadeus Self-Service integrations after the 17 July 2026 decommissioning, with clear OAuth, offer-lifecycle, booking-recovery and coverage boundaries.
Explore →Sabre vs Amadeus vs Travelport: GDS and NDC Comparison
Compare Sabre, Amadeus and Travelport across content sources, NDC/GDS capabilities, booking lifecycle, entitlement and servicing.
Explore →ENUYGUN: Turkey OTA and Travel Marketplace Profile
A profile of ENUYGUN's role in Turkey's travel-distribution ecosystem across flights, buses, hotels, car rental and transfers.
Explore →NDC Offer/Order Lifecycle: Search to Servicing
Model NDC Offer/Order lifecycle across search, offer, revalidation, order creation, payment, ticketing, servicing and reconciliation states.
Explore →