Push live hotel room availability updates to Expedia Lodging Connectivity via the Property API
domain: developers.expediagroup.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Expedia Group Partner API using OAuth 2.0 client credentials for the supply scope
Retrieve the Expedia property ID and room type IDs using GET /supply/lodging/properties/{propertyId}
Build a RoomAvailability payload with dateRanges, roomTypeId, and availableRooms count
PUT or PATCH to /supply/lodging/properties/{propertyId}/room-types/{roomTypeId}/availability
Confirm the update by checking the response status and parsing any warning messages about date overlaps
Subscribe to the Expedia reservation notification webhook to receive new bookings triggered by updated availability
Known gotchas
Expedia Lodging Connectivity distinguishes between stop-sell (availableRooms: 0) and closed (closed: true); using stop-sell when the intent is to close a rate plan leaves the rate plan visible but unBookable, which can cause partner support issues
Date ranges in the request must not overlap existing update transactions; concurrent writes to the same room type and date range result in last-write-wins behavior without conflict errors
The Property API uses Expedia property IDs, not GIATA or OTA supplier codes; mapping from internal property codes requires a one-time lookup via the property catalog endpoint
Give your agent this knowledge — and 15,600+ 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?