Execute a hotel search and room booking through the Expedia Rapid 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
Authenticate with the Expedia Rapid API using HMAC-based API key authentication; generate the correct Authorization header format as specified in the Rapid API documentation
Call the Property Availability endpoint with check-in/check-out dates, occupancy, and optionally a geographic bounding box or property ID list to receive available properties and rates
Select a property and rate plan; call the Room Price Check endpoint with the selected rate ID to confirm live availability and price before initiating a booking
Call the Create Booking endpoint with the confirmed rate token, guest details, and payment information; Expedia Rapid uses a tokenized payment flow — use the payment session token from the Rate Check step
Parse the booking response for the Expedia itinerary ID and confirmation number; store both and relay them to the guest along with the hotel's own confirmation number if returned
Known gotchas
The HMAC signature must be regenerated per request with the current Unix timestamp — pre-signed or cached authorization headers will be rejected
Rate tokens from the Room Price Check step expire; the booking must be completed within the validity window returned in the response
Expedia Rapid returns content in a specific locale and currency tied to your account configuration — ensure POS and currency settings are aligned with the end user's market to avoid rate mismatches
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?