Ancillary Cancel API Reference

POST

book/airoffer/reservationworkbench/{workbenchID}/offers/canceloffer

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

Base path:

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

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

Related Content:Seats Guide, Ancillary Guide

The Ancillary Cancel API supports canceling baggage and/or seats for both GDS and NDC, and canceling non-baggage paid ancillaries for NDC. Canceling non-baggage paid ancillaries for GDS is not supported.

Ancillary Cancel must be sent in a workbench session: Create a workbench, send Ancillary Cancel, and commit the workbench. You can cancel ancillaries booked in the same or a previous session.

Seat and ancillary cancel support may vary for specific carriers and in the booking workflow. See the Seats Guide and Ancillary Guide for support details.
Only one ancillary or seat per workbench session can be canceled. If you need to cancel multiple ancillaries or seats, send one cancel request, commit the workbench, and start a new workbench session to cancel the next ancillary or seat, and so on.
You cannot cancel ancillaries or seats from a ticketed itinerary.

Request

Query Parameters

None.

Request Body

Response

GDS responses return the ReferenceList object with flight details while NDC responses do not return ReferenceList.

Object

Description

OfferListResponse

Top level object for response.

Includes OfferID object. GDS responses also return the ReferenceList object.

OfferID

Top level object for seat offer details.

Includes Identifier, Product, Price, and TermsAndConditionsFull.

Identifier

Identifier for seat offer. Key value pairs:

authority: Returns the value Travelport for GDS or the carrier name for NDC.

value: Internal system-generated identifier for the offer.

Product

Top level object for product (product is the flight or connecting flights for one leg of the itinerary). Multiple instances returned for flights with multiple legs.

Key value pairs:

  • id: Custom identifier for product.

  • productRef: Reference for product.

Includes Identifier and Ancillary objects. May return Quantity.

Product/Identifier

Identifier for the product. Key value pairs:

authority: Returns the value Travelport for GDS or the carrier name for NDC.

value: Internal system-generated identifier for the product.

Quantity

Returned when multiple travelers are on the itinerary; number of seats in this product.

Ancillary

Includes SeatAssignment.

SeatAssignment

Includes Seat object.

Seat

Row and seat number of assigned seat that was canceled.

Price

Top level object for price details; amounts are 0 for free seats.

Includes CurrencyCode, Base, TotalTaxes, and TotalPrice objects. May include PriceBreakdown

CurrencyCode

The currency in which the price is returned. Currency is the default associated with your provisioned PCC from Travelport.

Key value pairs:

decimalPlace: Number of decimal places in the currency.

value: Currency code value.

Base

Base price before taxes and fees.

TotalPrice

Total price for a paid seat; 0 for free seats.

TermsAndConditionsFull

Any terms and conditions applicable to the seat.

Includes ApplicationLimit.

ApplicationLimit

Any restrictions on the number of this seat product that can be purchased.

Key value pairs:

start: Minimum quantity that can be purchased.

end: Maximum quantity that can be purchased.

value: The unit represented by this quantity. Possible values are:

  • PassengerSegment: Ancillary limit applies to each passenger at the segment level. E.g, Itinerary is LON-SIN-LON and the ancillary limit is “n” per segment per passenger.

  • Segment: Ancillary limit applies to all passengers at the segment level (one flight, or flights under the same number).

  • Itinerary: Ancillary limit applies to all passengers for the full itinerary.

  • Passenger: Ancillary limit applies per passenger for the full itinerary.

  • PassengerOD: Ancillary limit applies per passenger for the origin destination. E.g., Itinerary is LON X/SIN SYD X/SIN LON and the ancillary limit is “n” per origin destination (LON XSIN SYD)

  • Other

ReferenceList

Top level object for flight details. Includes Flight object.

Not returned for NDC seat cancel responses.

Flight

One instance per flight.

Key value pairs:

duration: Time of the flight in hours (H) and minutes (M).

carrier: Airline carrier.

number: Flight number.

operatingCarrier: When the carrier has filed a codeshare operating carrier for the flight, the IATA code for that codeshare carrier.

operatingCarrierName: Name of the marketing operating carrier.

equipment: Equipment model. Note that TRN, TRS, and BUS equipment codes indicate ground transportation.

id: id for internal flight reference number, also used in products and offers. For GDS, the Flight id is formatted as the letter ‘s’+ unique numeric value, as in s1.

Includes Identifier, Departure, and Arrival objects.

Flight/Identifier

Internal identifier for the flight. Key value pairs:

authority: Returns the value Travelport.

value: Internal system-generated identifier for the flight.

Departure

Departure details. Key value pairs are the location, date, time, and terminal of departure.

Arrival

Arrival details. Key value pairs are the location, date, time, and terminal of arrival.

Example Request

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

Example Response

The seat cancel response for both NDC and GDS returns an identifier and details of the canceled seat offer per the examples below.

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

GDS responses return the ReferenceList object with flight details while NDC responses do not return ReferenceList.

The NDC seat cancel response below does not return the ReferenceList object.