Cancel or modify an existing Travelport JSON API booking using the Workbench servicing flow
domain: developer.travelport.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve the reservation and open a workbench session for it so you have the workbenchID needed for servicing.
For a GDS booking, send a Cancel Workbench Items request specifying the offers, products, or segments to remove within that workbench session.
For an NDC-booked itinerary, use the separate NDC Modify API instead of Cancel Workbench Items, since NDC exchanges are finalized via Modify rather than Workbench Commit.
Send a Workbench Commit request (POST book/reservation/reservations/{workbenchID}) to finalize the cancellation or change and process payment for any residual charges.
Inspect the commit response for the updated reservation status and any refund, EMD, or MCO (miscellaneous change order) detail returned.
Known gotchas
Workbench Commit is the step that actually finalizes any cancel or modify action — items removed via Cancel Workbench Items are not applied until the commit call succeeds.
GDS and NDC content are serviced through different flows: GDS uses Cancel Workbench Items + Workbench Commit, while NDC order changes are completed via the separate Modify API — using the wrong flow for the content type will fail.
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?