Register as an Expedia connectivity partner or technology provider and obtain API credentials via the EG Connectivity Hub developer portal
Authenticate requests using the credentials provided; Expedia Lodging Connectivity uses HTTPS with partner credentials for supply-side endpoints
Call the Availability and Rates API to update inventory and rates by property, specifying Expedia-assigned room type IDs and rate plan IDs as identifiers
Include the date range, availability count, nightly rate, and any restrictions such as minimum or maximum length of stay in a single batched payload to update multiple room types and rate plans at once
Use the Booking Notification API or Booking Retrieval/Confirmation API pair alongside availability updates depending on which reservation delivery model your integration uses
Test end-to-end in the sandbox environment at the test endpoint before promoting to production
Known gotchas
Room type and rate plan IDs are Expedia-assigned identifiers, not your own PMS codes; you must retrieve Expedia IDs via the property management APIs before referencing them in ARI updates
Simultaneous updates to multiple room types and date ranges are supported in a single call, but very large payloads can time out; batch by a reasonable date window per request
Expedia Rapid API is a demand-side shopping API for building booking flows, not the supply-side ARI update API; using Rapid endpoints for inventory push will fail
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp