Cancel Workbench Items API Reference

POST

book/reservationworkbench/{workbenchID}/reservations/cancelitems

For {workbenchID} send the workbench identifier returned in ReservationResponse/Identifer/value in the workbench create response.

Base path:

Note the following base path does not include air and varies from other JSON APIs.

Pre-production https://api.pp.travelport.com/11/

Production https://api.travelport.com/11/

Related Content:Booking Guide, Booking Session Workflow

The Cancel Workbench Items API offers several payload optoins that support canceling the following.

In the initial booking workbench only:

Cancel Workbench Items supports only GDS in the post-commit workbench (in other words, for a held booking, aka an existing reservation). To modify an NDC held booking, use the NDC Modify API instead of Cancel Workbench Items. Cancel Workbench Items supports the following options for a GDS held booking:

When only offers are canceled, any data in the workbench and/or in the booking persist, and another offer can be added with Add Offer. If the workbench is committed without adding another offer, a shell booking with only traveler data is created.

A workbench retrieve before Cancel Workbench is recommended to sync all data.

Request

Query Parameters

None.

Request Body

The following payload provides options to cancel the entire reservation, all offers, or only selected offers, products, or segments.

See the introductory section above for which options are supported for NDC/GDS and in the initial and post-commit workbench. Note that this payload does not support any NDC post-commit options; instead, to modify an NDC held booking, create a post-commit workbench and use the NDC Cancel API.

Response

All of the request payloads above return a transaction identifier in the same format in the response.

Example Request

See the Request Body section above for details on when the following payloads are supported.

The following payload cancels the entire booking.

The following payload cancels all offers (air, hotel, and car as applicable) on a GDS held booking. Supported only for GDS in the post-commit workbench.

The following payload cancels a specific offer. This example sends sendPassiveNotificationInd because the offer includes a passive segmentClosed An air segment booked in a system outside the Travleport GDS. Adding a passive air segment to a booking maintains all travel details as part of the complete itinerary..

The following payload cancels multiple offers; the following example cancels two offers.

The following payload cancels a product within an offer.

The following payload cancels a segment within a product.

The following payload cancels multiple product and segment combinations.

Example Response

All of the request payloads above return a transaction identifier in the response per the example below.