Push property rates, availability, and inventory to Expedia via the EG Connectivity Hub Property API
domain: developers.expediagroup.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note that hotel-supply integration with Expedia lives under the EG Connectivity Hub (developers.expediagroup.com/supply/lodging) — distinct from the demand-side "Rapid API" used by sites that consume Expedia inventory.
Apply for supply partner access and obtain credentials for the Property API (RESTful JSON) covering property/room content and ARI.
Push availability, rates, and inventory updates through the Property API's ARI resources.
For older integrations still on the legacy Availability & Rates (AR) API, build SOAP requests using OTA-style messages (OTA_HotelAvailNotifRQ) with Expedia's RequestorId/ResponderId header authentication.
Validate ARI changes reflect correctly in Expedia's partner-facing property management tools before going live.
Known gotchas
"Expedia Rapid" and the supply-side Connectivity Hub are commonly conflated but are separate products with different domains, auth, and message formats — Rapid uses EAN APIKey/SHA-512 signature auth for demand-side shopping/booking, not for pushing PMS ARI.
The legacy AR API is SOAP/XML while the current Property API is JSON REST — confirm which one your partner tier is actually certified against before building.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?