GDS PNR Cancel API Reference

A PNR can be canceled prior to ticketing. For a GDS itinerary, send a POST request with the record locator. For an NDC itinerary, you must create a workbench session and then send the cancel request.

The segment or segments are then canceled; however, the PNR can still be retrieved. The PNR retrieve response in this case returns the traveler or travelers but no offer details.

In this topic:

PNR Cancel - GDS

Query Parameters

None.

POST Request

Send the POST request to the following resource:

POST receipt/reservations/{PNR}/receipts

Base path:

Pre-production https://api.pp.travelport.com/9/air/

Production https://api.travelport.com/9/air/

Payload

None.

Response

The PNR Cancel response returns a confirmation and status. The table below details the objects returned in the PNR Cancel response and notes differences between models v6 and v9.

Object Description

ReceiptListResponse

Top level object for response.

Includes ReceiptID object.

ReceiptID

Top level object for cancellation details.

Contains the following attribute:

  • id: Internal identifier.

Identifier

Contains the following attributes:

  • authority: Returns the value Travelport.
  • value: Internal transaction identifier for the cancellation.

Cancellation

Returns cancellation details. Includes the Locator object with the following attributes:

  • source: Provider on which the PNR was created.
  • sourceContext: Returns the value Travelport.
  • value: The locator code of the cancelled PNR.

PNR Cancel - NDC

Query Parameters

None.

POST Request

Send the POST request to the following resource:

POST receipt/reservations/{workbenchID}/receipts?OfferIdentifer/{offerID}/

Base path:

Pre-production https://api.pp.travelport.com/9/air/

Production https://api.travelport.com/9/air/

Payload

None.

Response

Both the Commit workbench transaction and a PNR retrieve request retrieve full PNR details.

The table below details the objects that may be returned in the PNR Retrieve response. Specific objects vary depending on what information was sent for the booking, and if an itinerary has already been ticketed.