Access the EG Connectivity Hub and confirm your integration uses the Booking Notification API model, where Expedia pushes new and modified reservations to your designated endpoint
Implement a receiver endpoint that accepts Expedia reservation notification payloads and returns an HTTP 200 acknowledgement within the required response time
Parse each inbound reservation message to extract booking ID, property code, room type, rate plan, guest details, check-in and check-out dates, and payment information
Confirm the booking by returning the required confirmation response to Expedia so the booking status transitions from pending to confirmed in the Expedia system
For cancellations, process the inbound cancel notification, update your PMS, and respond with the confirmation of cancellation receipt
Use the sandbox test environment to simulate booking, modification, and cancellation flows before connecting live Expedia inventory
Known gotchas
Expedia requires your endpoint to confirm each booking within a defined window; delayed confirmation causes Expedia to retry delivery and may result in Expedia auto-cancelling the booking if no confirmation is received in time
Expedia assigns its own booking IDs that are separate from any PMS or channel manager reference numbers; both must be stored and cross-referenced to support modification and cancellation lookups
Test reservations sent from the sandbox use a different authentication context from production; credentials and endpoint URLs must be switched correctly when moving from sandbox to live environment
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