Call OrderReshop with the existing order ID and the desired change parameters (new dates, new flight, or both) to retrieve repriced alternative offers
Compare the reshop offers against the original fare, noting any change fees, fare differences, or new conditions surfaced in the response
Select the preferred reshop offer and call OrderChange, supplying the order ID, the chosen new offer reference, and any additional payment required for upsell
Parse the OrderChangeRS for updated order details, new segment information, and reissued or new ticket numbers
Confirm the change is reflected in the order record by retrieving the order via OrderRetrieve and verify seat and ancillary associations carry over correctly
Known gotchas
Not all NDC carriers support OrderReshop/OrderChange; many require a void-and-rebook pattern for changes, so check capability flags in the AirShoppingRS or carrier capability document
Reshop offers may expire quickly — do not present them to a user for extended consideration without refreshing before OrderChange
If the change involves a fare downgrade, the carrier may require a refund of the difference rather than a credit; handle both code paths
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