Retrieve Workbench API Reference

Get

book/session/reservationworkbench/{workbenchID}

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

Use this base path if you have not yet received or not migrated to the new credentials from Travelport:

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

Use this base path after you have migrated to the new credentials from Travelport (.net instead of .com):

Pre-production https://api.pp.travelport.net/11/air/ | Production https://api.travelport.net/11/air/

Related Content:Booking Guide, Booking Session Workflow

At any point in the booking session, you can retrieve the workbench. The response returns all details added to the workbench at that point.

AirReservation 25.11.69 and later: When retrieving a workbench prior to the first workbench commit; if the Add Offer reference payload has been sent in that workbench session, the response returns price details. GDS only; not supported for NDC. Not supported if the Add Offer full payload has been sent, as price details are retrieved from a cached Search or Price response referenced in the Add Offer reference payload.
If a split ticketing offer has been added without a pricing request prior to the workbench session, a pre-commit workbench retrieve returns price details only for offers that share a combinability code (for example, both outbound and inbound are j0, j1, etc.). If differing segments have been added (for example, j1 outbound and j7 inbound), the response does not return price details, and may return an error such as No Valid Fare for Input Criteria.

Request

As part of the request requirements, also see Authentication and Common Air Headers.

Query Parameters

None.

Request Body

None.

Response

The request returns all information that has been added to the reservation workbench at this point. For example, if you have added an offer but not travelers, the request returns offer details but no traveler information.

The response uses the same format as the Reservation Retrieve but does not necessarily include all data outlined for that response.

Example Request

This request has no message payload.

Example Response

See Reservation Retrieve for examples.