Meet us at ATM Dubai | Booth TT2019
DWTC, Dubai
17 – 20 Aug 2026
DWTC, Dubai
17 – 20 Aug 2026
Table of Contents
700,000+ hotels. Two payment models. One API that powers a significant share of global online hotel bookings — and ZentrumHub already has it live. This is your complete guide to Expedia Rapid API integration in 2026.
Expedia isn’t just a consumer travel site — it’s one of the world’s largest hotel inventory networks, and its B2B division powers a significant share of the hotel bookings appearing on competing OTAs, airline loyalty portals, and corporate booking tools. The Expedia Hotel API — officially known as Expedia Rapid API — is how travel businesses programmatically access that inventory. If your OTA doesn’t have Expedia in its supplier stack, you’re missing coverage that your competitors almost certainly have.
This guide covers exactly what the API delivers, how its two payment models work, the real integration timeline, the technical requirements — and precisely how ZentrumHub makes it possible for OTAs to get Expedia inventory live without building the integration from scratch.
The Expedia Hotel API is officially called Expedia Rapid API — the successor to the deprecated EAN (Expedia Affiliate Network) XML API, which was switched off in 2019. It is the primary B2B product from Expedia Partner Solutions (EPS), the division of Expedia Group that serves travel technology businesses rather than end consumers.
Expedia Group is not just Expedia.com. The parent company owns Hotels.com, Vrbo, Orbitz, Travelocity, Wotif, and ebookers. The Rapid API surfaces hotel inventory consolidated from across all these brands through a single endpoint — which is why its 700,000+ property count carries genuine weight.
Expedia Rapid API is a RESTful JSON API that gives approved travel partners — OTAs, agencies, corporate travel platforms — programmatic access to Expedia Group’s hotel inventory for search, pricing, booking, and cancellation. It replaced the legacy EAN XML API and is the only supported Expedia hotel connectivity product today.
Access to the Expedia Hotel API is not open — it requires a commercial agreement with Expedia Partner Solutions. It is available to OTAs, white-label travel platforms, airline loyalty portals, corporate booking tools, and financial services travel programs. Individual developers and non-travel businesses do not qualify.
Raw property count is only useful if the inventory matches your OTA’s target markets and traveller types. According to AltexSoft’s technical analysis of the Expedia Partner API, Expedia’s strongest coverage is in North America and Europe, with solid presence across APAC and the Middle East. Here is what the inventory actually contains:
Expedia recommends pre-loading hotel content — images, descriptions, amenities — using the Content API’s bulk data feed rather than pulling it in real time with each search. Pulling content on demand adds 200–400ms per search response. Build a nightly content sync job into your hotel API integration architecture from day one.
Expedia Rapid API is a RESTful JSON API — no XML, no SOAP. Authentication uses an API Key plus Secret passed in request headers — simpler than OAuth-based systems like Amadeus. The core endpoint groups every Expedia hotel API integration must implement:
| Endpoint Group | Method & Path | What It Does |
|---|---|---|
| Shopping / Search | GET /properties/availability | Multi-property availability by dates, location, occupancy. Returns rates, room types, cancellation policy. |
| Price Check | GET /properties/{id}/rooms/rates | Validates rate before booking. Confirms price hasn’t changed since search. Required step before booking. |
| Booking | POST /itineraries | Creates reservation. Returns itinerary ID. Requires guest info, payment details, rate token. |
| Retrieve Booking | GET /itineraries/{id} | Retrieves full booking details, status, hotel confirmation number. |
| Cancel | DELETE /itineraries/{id}/rooms/{roomId} | Cancels individual room or full itinerary. Applies cancellation policy rules automatically. |
| Content API | GET /properties/content | Bulk static content download: names, images, amenities, descriptions. Use for nightly cache sync. |
| Payment Session | POST /payment-sessions | Handles payment tokenization for Partner Collect model. PCI-compliant token exchange. |
This is the decision most OTAs underestimate when planning their Expedia hotel API integration. The two payment models have fundamentally different implications for cash flow, pricing control, and technical complexity.
Under Expedia Collect, commission is paid post-stay — a customer booking 3 months ahead means you wait 3+ months for revenue. For OTAs with constrained working capital, this creates real pressure. Partner Collect collects payment at booking but requires scheduled settlement with Expedia. Factor this into your financial model before choosing a structure.
Building a direct Expedia hotel API integration is a multi-phase project. from initial application to production launch, the full process typically runs 12–20 weeks for a competent engineering team — and that is for Expedia alone. Here is the realistic breakdown:
Multiply this 12–20 week process by 10 suppliers and you are looking at 2+ years before your OTA has competitive inventory depth. This is precisely why most OTAs in 2026 use a hotel API aggregator — one integration that gives access to all suppliers simultaneously, with the deduplication, content matching, and maintenance already handled.
Expedia is one of many hotel suppliers OTAs need to evaluate. Here is how it compares against the four other major suppliers covered in this series:
| Factor | Expedia Rapid API | Hotelbeds | Amadeus | Agoda | RateHawk |
|---|---|---|---|---|---|
| Properties | 700K+ | 250K+ | 150K+ | 2M+ | 2.5M+ |
| Rate Model | Net + Commission | Net wholesale | GDS + corporate | Commission | Net only |
| Auth Method | API Key + Secret | API Key | OAuth 2.0 | API Key | API Key + HMAC |
| Regional Strength | N. America, Global | Mediterranean, leisure | Europe, corporate | APAC | Europe, CIS, MEA |
| Integration Timeline | 12–20 weeks total | 8–16 weeks | 10–18 weeks | 8–14 weeks | 3–6 weeks |
| IATA Required | No | No | Sometimes | No | No |
| Key Differentiator | Brand trust + dual payment models | Leisure rate depth | Corporate rates | APAC exclusives | Widest coverage |
These are the recurring issues OTA development teams face when building a direct Expedia Rapid API integration — and the practical fixes:
ZentrumHub is a travel technology company and hotel API integration provider. The Expedia Hotel API is already built, tested, and maintained inside Zentrum Connect — ZentrumHub’s universal hotel inventory feed that aggregates 100+ supplier APIs into a single connection point for OTAs.
Expedia is one of those 100+ suppliers. So are Hotelbeds, RateHawk, Amadeus, Agoda, WebBeds, Priceline, and dozens more. See the full list of hotel suppliers available via ZentrumHub. The integration work is done. The normalisation, deduplication, and content matching are live. What ZentrumHub provides is the single connection that gives your OTA access to all of them.
OTAs that already have a commercial agreement with Expedia Partner Solutions bring their supplier contract to ZentrumHub. ZentrumHub activates it inside Zentrum Connect — and it immediately becomes part of your combined hotel inventory feed alongside all other suppliers you have enabled. No separate integration build. No redevelopment. Your hotel booking engine receives one unified, deduplicated, normalised inventory feed. See exactly how this works on the Expedia API integration with ZentrumHub page.
OTAs that don’t yet have an Expedia contract can still access Expedia inventory through ZentrumHub’s existing supplier relationships — subject to commercial terms. Either way, the integration overhead that would cost your team 12–20 weeks is eliminated. See how TravClan scaled to 4x daily bookings using this model, or review the Hotel Supplier Connect solution for full details on how supplier activation works.
ZentrumHub activates your Expedia supplier agreement inside Zentrum Connect — combining it with 100+ other hotel suppliers in one inventory feed delivered directly to your booking engine.
Talk to Our Integration Team →ZentrumHub’s Zentrum Connect combines Expedia, Hotelbeds, Amadeus, Agoda, RateHawk, and 95+ more suppliers into one hotel inventory feed — with real-time deduplication, sub-500ms response, and direct activation inside your OTA booking engine.
