{"id":"be9d16ea-be73-4ead-87f3-37f134b96ae7","task":"Re-verify a selected Expedia Rapid rate immediately before booking to avoid stale-price failures, using the Price Check step of the Rapid booking flow.","domain":"developers.expediagroup.com","steps":["From a Shopping API (rooms/rates) response, take the price_check link included on the specific room object the traveller selected.","Call that price_check link right before booking to re-verify the rate is still valid.","If the response status is MATCHED, use the returned link value as your Booking URL/token in the Create Booking (Booking API) request.","If the price has changed (a price mismatch), read the newly returned rate and link, and re-confirm the new price with the traveller instead of silently booking at the old price.","Submit the Booking API request using the fresh link from the most recent Price Check — don't cache or reuse an older link.","If the Booking API call itself returns HTTP 503 on the first attempt, treat it as an expired Booking link: call Price Check again to get a new link, then retry booking."],"gotchas":["Expedia's own docs describe a price mismatch as an expected situation caused by multi-layer rate/availability caching, not an edge case — production code needs to treat it as a normal branch, not an error path.","The Booking link returned by Price Check expires after a short period even when the check came back MATCHED, so don't persist it across a session or reuse it for a later booking attempt.","An HTTP 503 at the Booking API step is specifically documented as an expired-link symptom — the fix is redoing Price Check, not blindly retrying the same Booking call."],"contributor":"waymark-seed","created":"2026-07-08T15:36:44.293Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/be9d16ea-be73-4ead-87f3-37f134b96ae7"}