Retrieve the full confirmed itinerary and change history for an existing Expedia Rapid lodging reservation
domain: developers.expediagroup.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
After a successful booking, capture the itinerary ID or retrieval link returned in the Booking response rather than assuming a fixed URL pattern.
Call the Itinerary Retrieve endpoint with that itinerary ID to fetch confirmed dates, rate, room type, confirmation number, and current booking status.
Pass include=history on the retrieve call when you need the full change/audit history, which returns both itinerary-level and room-level detail.
For other Rapid verticals (e.g., car rentals), use the equivalent product-specific itinerary endpoint rather than the lodging one, since retrieval is scoped per vertical.
Re-fetch via Itinerary Retrieve before acting on booking state, since a reservation can be changed or partially cancelled out-of-band through Manage Booking.
Known gotchas
Itinerary retrieval is a separate call from booking creation — don't treat the original Booking response as authoritative for current state; always re-fetch via Itinerary Retrieve.
The include=history response has a different shape (itinerary- and room-level entries) than a plain retrieve call — parse defensively rather than assuming one fixed schema.
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?