Meet us at ATM Dubai | Booth TT2019
DWTC, Dubai
17 – 20 Aug 2026
DWTC, Dubai
17 – 20 Aug 2026
Table of Contents
GDS-grade hotel inventory. Deep corporate rates. OAuth 2.0 architecture. Here is exactly what the Amadeus hotel API delivers — and where it fits in your OTA’s supplier stack in 2026.
Amadeus is not an OTA. It does not compete with you for end customers, and it has no interest in your margin. What it does have is something bedbanks don’t — GDS-grade corporate hotel rates, deep chain hotel content, and a direct connection to the global travel infrastructure that has powered travel agencies for decades. For OTAs targeting business travellers, TMCs, or European markets, the Amadeus hotel API is a supplier worth understanding precisely.
This guide covers every dimension of the Amadeus hotel API — what it actually contains, how its OAuth 2.0 authentication works, what the self-service vs enterprise tiers give you, where it outperforms bedbanks, and where it doesn’t. Plus exactly how ZentrumHub makes it accessible without the integration overhead.
Amadeus (Amadeus IT Group S.A.) is one of the world’s three major Global Distribution Systems (GDS), alongside Sabre and Travelport. Founded in 1987 and headquartered in Madrid, Amadeus is a pure travel technology infrastructure company — it does not operate an OTA, does not sell directly to consumers, and does not compete with travel agencies or booking platforms for end-customer revenue.
The Amadeus hotel API is part of the Amadeus for Developers platform — a self-service API portal launched in 2018 that opened Amadeus’s technology stack to developers and travel tech companies beyond traditional GDS-connected travel agencies. Before 2018, accessing Amadeus required a full enterprise GDS agreement; the developer portal changed that.
Amadeus hotel API is a set of RESTful APIs within the Amadeus for Developers platform that gives travel businesses programmatic access to GDS-connected hotel inventory — covering hotel search, availability, rate confirmation, booking, and hotel ratings data. It is distinct from bedbank APIs in that its primary inventory strength is branded chain hotels with corporate and negotiated rates, not independent leisure properties.
One critical distinction: the Amadeus GDS API available through the self-service developer portal gives access to a subset of total GDS hotel content. Full corporate rate content — including negotiated rates from Fortune 500 travel programmes — requires a direct Amadeus Enterprise commercial agreement, not just a developer account.
Unlike single-endpoint suppliers, Amadeus provides a suite of distinct hotel API products. Understanding which ones your integration needs — and which are optional — is important for scoping the build correctly:
Search by city code, geo-coordinates, or hotel ID. Returns rates, room types, and availability. Core search endpoint — required for any hotel booking flow.
Retrieves specific offer details for a property. Price and availability confirmation step before committing to a booking. Equivalent to Expedia’s price check endpoint.
Creates hotel reservations. Requires traveller profile data and payment information. Returns booking confirmation with PNR and hotel confirmation number.
Retrieves hotel sentiment scores and review category breakdowns (cleanliness, service, location, etc.) from Amadeus’s proprietary review aggregation. Useful for property detail pages.
Type-ahead search for hotel names — useful for the search bar UX on your booking platform. Returns matching hotels as user types, reducing friction at the search entry point.
Returns nearby attractions, restaurants, and activities for a location. Complementary data for hotel detail pages — helps travellers contextualise a property’s location.
With 150,000+ hotels, the Amadeus hotel API has the smallest raw property count of any major supplier API. That number is not a weakness — it reflects a deliberate focus. Amadeus GDS coverage skews heavily toward branded hotel chains with a strong GDS presence — precisely the inventory that corporate travel managers and TMCs need.
Amadeus is not a bedbank replacement — it is a complement. OTAs that want complete hotel inventory coverage need both GDS connectivity (Amadeus, Sabre) for corporate chain rates AND bedbank connectivity (Hotelbeds, RateHawk) for leisure wholesale rates. Using Amadeus alone leaves a significant gap in independent hotel coverage.
The most important technical distinction of the Amadeus hotel API — compared to Expedia, Hotelbeds, or RateHawk — is its authentication method. Amadeus uses OAuth 2.0, not a simple API Key. This adds meaningful engineering complexity that OTAs must plan for.
The 30-minute token expiry means your integration must implement an automatic token refresh mechanism — every API call must first check if the current token is still valid, and refresh it if not. Failing to handle this correctly results in 401 errors in production at seemingly random intervals. Build token management as a dedicated service layer in your architecture, not inline with individual API calls.
Amadeus operates two fundamentally different access tiers — and understanding this distinction upfront saves OTAs from investing engineering time in a test integration that doesn’t reflect what production actually delivers.
Amadeus occupies a specific niche in the hotel supplier API landscape. Here is how it compares against the four other major suppliers on the dimensions that matter for OTA decision-making:
| Factor | Amadeus | Expedia Rapid | Hotelbeds | Agoda | RateHawk |
|---|---|---|---|---|---|
| Properties | 150K+ | 700K+ | 250K+ | 2M+ | 2.5M+ |
| Rate Type | GDS + Corporate | Net + Commission | Net wholesale | Commission | Net only |
| Auth Method | OAuth 2.0 | API Key + Secret | API Key | API Key | API Key + HMAC |
| Regional Strength | Europe, Corp Global | N. America, Global | Mediterranean | APAC | Europe, CIS, MEA |
| Free Test Access | Yes — self-serve portal | Sandbox (post-approval) | Sandbox (post-approval) | Sandbox (post-approval) | Sandbox (post-approval) |
| IATA Required | Sometimes (Enterprise) | No | No | No | No |
| Key Differentiator | Corporate rates + GDS ecosystem | Brand trust, dual payment | Leisure rate depth | APAC exclusives | Widest coverage |
The Amadeus GDS integration is one of the more technically demanding supplier integrations — not because the API is poorly documented, but because the architecture decisions it requires are more complex than key-based APIs. Here are the recurring issues:
ZentrumHub is a hotel API integration provider and travel technology company. The Amadeus hotel API is already built, normalised, and maintained inside Zentrum Connect — alongside 100+ other hotel suppliers including Expedia, Hotelbeds, Agoda, RateHawk, and Priceline. View the full list of hotel suppliers available via ZentrumHub.
The model is straightforward: OTAs that have a commercial agreement with Amadeus bring their supplier contract to ZentrumHub. ZentrumHub activates it inside Zentrum Connect — and it immediately becomes part of your combined hotel inventory feed. No OAuth implementation on your side. No token refresh engineering. No separate integration build. The booking engine receives one unified, deduplicated, normalised feed.
Amadeus is one of the more technically demanding supplier integrations due to OAuth complexity and the content tier distinction. By enabling it through ZentrumHub’s Hotel Supplier Connect, your team bypasses the OAuth management layer entirely — ZentrumHub handles authentication, token refresh, error handling, and API versioning. Your OTA gets Amadeus GDS inventory without the GDS integration complexity. See the RateHawk & ZentrumHub partnership case study for a real example of how supplier activation works at scale.
ZentrumHub activates your Amadeus supplier agreement inside Zentrum Connect, combining it with 100+ other hotel suppliers in one clean inventory feed.
Talk to Our Integration Team →ZentrumHub combines Amadeus GDS, Expedia, Hotelbeds, Agoda, RateHawk, and 95+ more suppliers into one hotel inventory feed — with sub-500ms response, real-time deduplication, and direct activation inside your booking engine. 3M+ room nights booked. $650M+ revenue generated for clients.
