v1.6 | April 7, 2021
- GetBooking will return additional data for the creation of the booking. This will include the sine of the user who created it, creation date & time, the PCC the booking was created in, the PCC the creating user is coming from, and the prime host ID.
- GetBooking will start returning structured data about Other Service Information (OSI). The information provided will include the airline, chain (hotels) or vendor (cars, trains, cruises) codes, and the service message. Optionally, the traveler index can also be returned.
- CreateBooking will support sending other service information (OSI).
- CreateBooking will allow filtering the profiles by ID.
- CheckFlightTickets will start supporting requests by confirmationId. This allows you to check all ATPCO-Tickets of a reservation and check the refund or void option of a NDC Order.
- CancelBooking will support voids or refunds for NDC orders. Simply provide the offerItemId to the request and we take care of the rest.
API Information
What's New
- GetBooking will return additional data for the creation of the booking. This will include the sine of the user who created it, creation date & time, the PCC the booking was created in, the PCC the creating user is coming from, and the prime host ID.
- GetBooking will start returning structured data about Other Service Information (OSI). The information provided will include the airline, chain (hotels) or vendor (cars, trains, cruises) codes, and the service message. Optionally, the traveler index can also be returned.
- CreateBooking will support sending other service information (OSI).
- CreateBooking will allow filtering the profiles by ID.
- CheckFlightTickets will start supporting requests by confirmationId. This allows you to check all ATPCO-Tickets of a reservation and check the refund or void option of a NDC Order.
- CancelBooking will support voids or refunds for NDC orders. Simply provide the offerItemId to the request and we take care of the rest.
Business Value
- Full integration of void and refund in cancelBooking across ATCPO and NDC content.
- Support for other service information in createBooking and getBooking.
- CreateBooking will now automatically send infant traveler SSRs to the airline.
New Features
In the Request
Optional
- Parameter: CreateBookingRequest.profiles.filterId
-
Type: string
Description: Profile Filters
Sample Value:
"filterId": "112676753"Note:
In the Request
Optional
- Parameter: CreateBookingRequest.travelers.emails
-
Type: Array
Description: Associate a list of email addresses to a traveler.
Sample Value:
"emails": [
"john@smith.family.priv"
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.otherServices
-
Type: Array
Description: Contains Other Service Information (OSI) sent to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Response
Optional
- Parameter: GetBookingResponse.creationDetails
-
Type: Object
Description: Contains details about the creation of a booking.
Sample Value:
"creationDetails": {
"creationUserSine": "A12",
"creationDate": "2021-01-09",
"creationTime": "15:00",
"userWorkPcc": "AB12",
"userHomePcc": "CD34",
"primeHostId": "1S"
},Note:
In the Response
Optional
- Parameter: GetBookingResponse.otherServices
-
Type: Array
Description: Contains Other Service Information (OSI) sent to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Request
Optional
- Parameter: CancelBookingRequest.offerItemId
-
Type: String
Description: Offer ID referencing the cancel option for a NDC order. This ID must be applied when cancelling an order to receive a refund or void.
Sample Value:
"offerItemId": "cb7778589bcbklg7tkkp8sdo50"Note:
In the Request
Optional
- Parameter: CheckFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: VoidFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: RefundFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
Functional Updates And Enhancements
In the Request
Optional
- Parameter: CreateBookingRequest.profiles
-
Type: Object
Description: Additional filtering options for profile selection.
Sample Value:
"profiles": [
{
"profileName": "TESTPROFILE",
"profileTypeCode": "TVL",
"uniqueId": "ABC123",
"domainId": "G7HE",
"filterId": "112676753"
}
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.otherServices
-
Type: Array
Description: Possibility to send other service information (OSI) to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.travelers.emails
-
Type: Array
Description: Lists emails associated to a traveler.
Sample Value:
"emails": [
"john@smith.family.priv"
]Note:
In the Request
Optional
- Parameter: getBookingRequest.returnOnly
-
Type: Array
Description: Additional returnOnly option "OTHER_SERVICES" to return only other service information (OSI)
Sample Value:
{
"confirmationId": "ABCDEF",
"returnOnly": ["OTHER_SERVICES"]
}Note:
In the Response
Optional
- Parameter: GetBookingResponse.otherServices
-
Type: Array
Description: Lists other service information (OSI)
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"travelerIndex": 1,
"serviceMessage": "TEST OSI MESSAGE"
},
{
"chainCode": "BY",
"serviceMessage": "/CX-J674A0957C0"
},
{
"vendorCode": "ZE",
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Response
Optional
- Parameter: GetBookingResponse.creationDetails
-
Type: Object
Description: Provides information about the creation of the booking.
Sample Value:
"creationDetails": {
"creationUserSine": "A12",
"creationDate": "2021-01-09",
"creationTime": "15:00",
"userWorkPcc": "AB12",
"userHomePcc": "CD34",
"primeHostId": "1S"
}Note:
In the Response
Optional
- Parameter: GetBookingResponse.futureTicketingPolicy
-
Type: Object
Description: Contains ticketing instructions for a booking.
Sample Value:
"futureTicketingPolicy": {
"ticketingPcc": "AB12",
"queueNumber": "55",
"ticketingDate": "2019-07-09",
"ticketingTime": "11:00",
"comment": "TICKET BEFORE TUES"
}Note:
In the Request
Optional
- Parameter: CancelBookingRequest.flightTicketOperation
-
Type: String
Description: New option "REFUND" to cancel the booking and refund all tickets.
Sample Value:
"flightTicketOperation": "REFUND"Note:
In the Request
Optional
- Parameter: CancelBookingRequest.designatePrinters.
-
Type: Array
Description: Additional printer designation options were added: hard copy printer, ticket printer and invoice&itinerary printer
Sample Value:
"designatePrinters": [
{
"hardcopy": {
"address": "EF34GH",
"spacing": "1"
},
"invoiceItinerary": "AB12CD",
"ticket": {
"address": "EF34GH",
"countryCode": "RU"
}
}
]Note:
In the Request
Optional
- Parameter: CancelBookingRequest.offerItemId
-
Type: String
Description: The offerItemId allows to define action on NDC tickets. Use checkFlightTickets to obtain the possible refund or void offers, including the offerItemId.
Sample Value:
"offerItemId": "cb7778589bcbklg7tkkp8sdo50"Note:
In the Request
Optional
- Parameter: CheckFlightTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to verify refund and void options for the entire booking. This will check the entire list ATPCO tickets in a PNR or the NDC Order.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: RefundFlighTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to refund the entire list ATPCO tickets in a PNR.
Sample Value:
"confirmationId": "GLEBNY"Note: Not supported for NDC Orders.
In the Request
Optional
- Parameter: VoidFlightTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to void the entire list ATPCO tickets in a PNR.
Sample Value:
"confirmationId": "GLEBNY"Note: Not supported for NDC Orders.
Resolved Issues
In the Request
Optional
DE191705: voidFlightTickets with confirmationId returns tickets array in request
In the Request
Optional
DE193728: cancelBooking with Sabre Order Id fails
In the Response
Optional
DE193144: Baggage allowance showing in itinerary when there is no PQ in reservation
In the Request
Optional
DE193727: cancelBooking with offerItemId fails [NDC]
In the Request
Optional
DE192788: cancelBooking Cannot deserialize value of type `ReturnOnlyEnum` from String
In the Response
Optional
DE190631: CONTEXT_CHANGE_PROBLEM when using targetPcc
Relase note ID: 15802
v1.5 | February 25, 2021
- createBooking - New method for booking various content.
- checkFlightTickets - New method to verify voidability and refundability for flight tickets.
- refundFlightTickets - New method to refund flight tickets incl. the option to apply refund qualifiers.
- Post Processing Options - Send and email or place the booking on one or more queues after transaction finished.
- Printer Designation - Apply a printer profile for a void or refund transaction.
API Information
What's New
- createBooking - New method for booking various content.
- checkFlightTickets - New method to verify voidability and refundability for flight tickets.
- refundFlightTickets - New method to refund flight tickets incl. the option to apply refund qualifiers.
- Post Processing Options - Send and email or place the booking on one or more queues after transaction finished.
- Printer Designation - Apply a printer profile for a void or refund transaction.
Business Value
- Create Booking is used to book various Sabre content within a single API call. It creates either a Sabre order or a Sabre PNR.
- Check and Refund Flight Tickets are used to refund tickets with a two-step process. These methods return options to refund or void a ticket (including refundable amounts).
- Added post-processing options are used to place a PNR on one or more queues, or to send an email after the transaction finished.
- Support for printer profiles allows the designation of a printer using a printer profile number.
New Features
In the Response
Optional
- Parameter: getBooking returns seat array for NDC flights
-
Type: array
Description: Row and column for a seat location
Sample Value:
"seats": [
{
"number": "13A"
}
],Note:
Functional Updates And Enhancements
In the Request
Optional
- Parameter: Printer Designation
-
Type: array
Description: Providing the applicable printer profile number will designate the associated printer(s) during the transaction. Printer(s) will be undesignated at the end of the flow.
Sample Value:
"designatePrinters": [
{
"printerProfileNumber": 1
}
]Note:
In the Request
Optional
- Parameter: Queue Placement
-
Type: array
Description: Place the PNR on up to three (3) queues after the transaction finishes. Additionally, PCC, PIC, and queue place date can be specified.
Sample Value:
"queuePlacement": [
{
"queueNumber": 400,
"queueName": "HENRY",
"pcc": "G7RE",
"prefatoryInstructionCode": 11,
"futureQueuePlacementDate": "2019-07-09"
}
]Note: This cannot be combined with notifications.email.
In the Request
Optional
- Parameter: Email
-
Type: string
Description: Send an email with a predefined template to the email address(es) in the PNR.
Sample Value:
"email": "INVOICE",Note: This cannot be combined with notifications.queuePlacement.
In the Response
Required
- Parameter: Support for ARUNK-Segments
-
Type: string
Description: Get Booking will return a special type, "ARNK", for ARUNK segments under allSegments.
Sample Value:
"allSegments": [
{
"id": "8",
"type": "FLIGHT",
"text": "2",
"vendorCode": "EY",
"startDate": "2021-05-10",
"startTime": "11:20:00",
"startLocationCode": "FRA",
"endDate": "2021-05-10",
"endTime": "19:40:00",
"endLocationCode": "AUH"
},
{
"id": "9",
"type": "ARNK"
}
],Note:
Resolved Issues
In the Response
Required
DE188896: ticketStatus doesn't match couponStatus
In the Response
Required
DE188764: cancelBooking unable to finish due to EET Error
In the Response
Optional
DE188524: Duplicate fareRules Warning returned when ticket is voided/refunded/exchanged
In the Response
Required
DE188440: getBooking with "returnOnly": ["TICKETS"] does not return flightCoupons and returns warning for fareRules
In the Response
Optional
DE187807: getBooking returns flightCoupons without itemId for PNR without flights (cancelled)
In the Response
Optional
DE187800: getBooking returns warnings regarding fareRules for PNR without flights (cancelled)
In the Response
Optional
DE187795: Incorrect Price Quote filtering leads to fareRules error
In the Response
Required
DE187129: incorrect validating carrier applied to structuredFareRulesRQ
In the Response
Optional
DE186806: incorrect passenger type count sent to structured fare rules
In the Response
Required
DE186902: getBooking with "returnOnly": ["TICKETS"] does not return tickets
In the Request
Required
DE186774: Missing validation for too long ticket number in VoidTicketRQ
In the Response
Optional
DE186747: Post Processing: Send queuePlaceRQ with multiple queues
In the Response
Required
DE185951: flighTotals.total not returned for unticketed NDC Order
In the Request/Response
Optional
DE185847: messageContext not populated for Ticketing service
In the Request
Required
DE185629: cancelBooking: Invalid entry for flightTicketOperation doesn't stop the flow
In the Response
Optional
DE185327: missing FareRules warning created incorrectly
In the Response
Required
DE185017: missing fareRules warning lacks in singular/plural consistency
In the Request/Response
Required
DE185014: Cancel of ATPCO segment in mixed NDC/ATPCO Order fails due to EnhancedEndTransaction Warning
In the Response
Required
DE184773: flightTotals for not ticketed NDC order missing
In the Response
Optional
DE184566: Inconsistent Error for Partial Cancel of NDC content
In the Response
Optional
DE183115: no message Context Created for cancelBooking & void Ticket
Relase note ID: 15543
v1.4 | December 3, 2020
- Additional details were added for hotels, cars and trains. Payment details per segment are returned now.
- hotelTotals returns information about fees included in the payment now.
- With this version the service starts returning information about identity documents based on Special Service Requests (SSR) for flights.
- Application will now return loyalty program information per traveler.
- CancelBooking and cancelFlightTickets supports AUTO-E setup now.
- CancelBooking and cancelFlightTickets allow now a custom value for the "receive from" field.
API Information
What's New
- Additional details were added for hotels, cars and trains. Payment details per segment are returned now.
- hotelTotals returns information about fees included in the payment now.
- With this version the service starts returning information about identity documents based on Special Service Requests (SSR) for flights.
- Application will now return loyalty program information per traveler.
- CancelBooking and cancelFlightTickets supports AUTO-E setup now.
- CancelBooking and cancelFlightTickets allow now a custom value for the "receive from" field.
Business Value
- The addition of loyalty programs and identity documents in getBooking mark the first step in supporting special service requests for flights.
New Features
In the Response
Optional
- Parameter: identityDocuments
-
Type: array
Description: This feature will list all identity documents for a given traveler providing detailed information about each document.
Sample Value:
"identityDocuments": [
{
"documentNumber": "1122334455AAZZ",
"documentType": "PASSPORT",
"expiryDate": "2022-09-30",
"issuingCountryCode": "EN",
"givenName": "GEORGE",
"surname": "ORWELL",
"birthDate": "1986-04-26",
"gender": "MALE",
"isPrimaryDocumentHolder": false
}
]Note: Depending on the document type different fields will be returned.
In the Response
Optional
- Parameter: loyaltyPrograms
-
Type: array
Description: The feature will list loyalty programs such a frequent flyer numbers for each traveler.
Sample Value:
"loyaltyPrograms": [
{
"supplierCode": "BA",
"programNumber": "11223344",
"tierLevel": 3,
"receiverCode": "AA"
}
]Note: Currently only frequent flyer programs are supported.
In the Request
Optional
- Parameter: receivedFrom
-
Type: string
Description: CancelBooking and cancelFlightTickets will allow you to customize the value for the receivedFrom field.
Sample Value:
{
"confirmationId": "UOZEUN",
"retrieveBooking": true,
"receivedFrom": "MY RECEIVER NAME",
"cancelAll": false,
"errorHandlingPolicy": "HALT_ON_ERROR",
"flights": [
{
"itemId": 12
}
]
}Note:
Functional Updates And Enhancements
In the Request
Optional
- Parameter: cancelBookingRQ.receivedFrom
-
Type: string
Description: Used to identify the entity that authorized the changes in a passenger name record.
Sample Value:
"receivedFrom": "Booking Management API Test"Note: If the field is not part of the request the default value will be applied.
In the Response
Optional
- Parameter: getBookingRS.hotels.payment.taxes
-
Type: string
Description: Returns the sum of taxes for a given hotel payment.
Sample Value:
"taxes": "8.00"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.payment.subtotal
-
Type: string
Description: Returns the amount before taxes for a given hotel payment.
Sample Value:
"subtotal": "120.00"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.payment.fees
-
Type: string
Description: Returns the sum of fees for a given hotel payment.
Sample Value:
"fees": "12.50"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.payment.total
-
Type: string
Description: Returns the total amount for a given hotel payment.
Sample Value:
"total": "125.63"Note:
In the Response
Optional
- Parameter: getBookingRS.payments.hoteltotals.fees
-
Type: string
Description: Returns the sum of fees for all hotel payment.
Sample Value:
"fees": "36.30"Note:
In the Response
Optional
- Parameter: getBookingRS.trains.payment.currencyCode
-
Type: string
Description: Returns the three letters ISO 4217 Currency Code for a given train payment.
Sample Value:
"currencyCode": "USD"Note:
In the Response
Optional
- Parameter: getBookingRS.trains.payment.total
-
Type: string
Description: Returns the total amount for a given train payment.
Sample Value:
"total": "43.00"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.payment.currencyCode
-
Type: string
Description: Returns the three letters ISO 4217 Currency Code for a given hotel payment.
Sample Value:
"currencyCode": "USD"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.payment.subtotal
-
Type: string
Description: Returns the amount before taxes of a given car payment.
Sample Value:
"subtotal": "150.00"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.payment.total
-
Type: string
Description: Returns the total amount for a given car payment.
Sample Value:
"total": 185.30"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.payment.currencyCode
-
Type: string
Description: Returns the three letters ISO 4217 Currency Code for a given car payment.
Sample Value:
"currencyCode": "USD"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.payment.taxes
-
Type: string
Description: Returns the sum of taxes for a given car payment.
Sample Value:
"taxes": "15.99"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.documentNumber
-
Type: string
Description: Returns the unique identifier for a document.
Sample Value:
"documentNumber": "CC90IBE2020"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.documentType
-
Type: string
Description: Returns the type of document.
Sample Value:
"documentType": "VISA"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.expiryDate
-
Type: string
Description: The expiration date of the identity document.
Sample Value:
"expiryDate": "2024-07-09"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.issuingCountryCode
-
Type: string
Description: The ISO code of the country issuing the passenger document.
Sample Value:
"issuingCountryCode": "FR"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.residenceCountryCode
-
Type: string
Description: The ISO code of the residing country or nationality country.
Sample Value:
"residenceCountryCode": "DE"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.placeOfIssue
-
Type: string
Description: The name of the place where the document was issued.
Sample Value:
"placeOfIssue": "ROME"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.placeOfBirth
-
Type: string
Description: The place of birth.
Sample Value:
"placeOfBirth": "MINSK"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.hostCountryCode
-
Type: string
Description: The ISO country code where the document is valid.
Sample Value:
"hostCountryCode": "US"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.issueDate
-
Type: string
Description: The issue date of the identity document.
Sample Value:
"issueDate": "2019-07-09"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.givenName
-
Type: string
Description: The traveler's first name.
Sample Value:
"givenName": "John"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.middleName
-
Type: string
Description: The traveler's middle name.
Sample Value:
"middleName": "Jack"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.surname
-
Type: string
Description: The traveler's last name.
Sample Value:
"surname": "Orwell"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.birthDate
-
Type: string
Description:
Sample Value:
"birthDate": "1980-12-02"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.gender
-
Type: string
Description: The gender of the individual.
Sample Value:
"gender": "MALE"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.isPrimaryDocumentHolder
-
Type: boolean
Description: If 'true' it indicates the primary passport holder when the document is issued for multiple travelers.
Sample Value:
"isPrimaryDocumentHolder": trueNote:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.residenceDestinationAddress.street
-
Type: string
Description: The street name and house number accompanied with the number of apartments/unit/suite, if applicable.
Sample Value:
"street": "1230 Ellen Ave, apt 10"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.residenceDestinationAddress.city
-
Type: string
Description: The name of the city.
Sample Value:
"city": "Dallas"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.residenceDestinationAddress.stateProvince
-
Type: string
Description: The name or code of the state or province.
Sample Value:
"stateProvince": "TX"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.identityDocuments.residenceDestinationAddress.postalCode
-
Type: string
Description: The zip or postal code.
Sample Value:
"postalCode": "75063"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.loyaltyProgram.supplierCode
-
Type: string
Description: The two-letter code that issued the number such as IATA airline code.
Sample Value:
"supplierCode": "BA"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.loyaltyProgram.programNumber
-
Type: string
Description: Traveler membership number for loyalty program such as frequent flyer number.
Sample Value:
"programNumber": "987654321"Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.loyaltyProgram.tierLevel
-
Type: integer
Description: The level that the traveler reached within the loyalty program.
Sample Value:
"tierLevel": 3Note:
In the Response
Optional
- Parameter: getBookingRS.travelers.loyaltyProgram.receiverCode
-
Type: string
Description: The two-letter receiver code, such as IATA airline code.
Sample Value:
"receiverCode": "UA"Note:
Resolved Issues
In the Response
Optional
[GetBooking] DE179517: fareRules: Incorrect Passenger Code Filtering
In the Request
Optional
[CancelFlightTickets] DE181034: TKT_GetElectronicDocument fails when document number exceeds 13 digits
In the Response
Optional
[GetBooking] DE181137: missing fareRules/No fareRules Error
In the Response
Optional
[GetBooking] DE181922: Exception while processing --> Text '11FEB08' could not be parsed at index
In the Response
Optional
[GetBooking] DE182391: fareRules not populated for Multi-Passenger-One-Way Itinerary
In the Response
Optional
[GetBooking] DE182381: fareRules can not be populated for Multiple-One-Ways Itinerary
In the Response
Optional
[GetBooking] DE182400: For not-ticketed PNR flightTotals should not be returned if there is no flight present
In the Response
Optional
[GetBooking] DE182282: fareRules can not be populated for Open-Jaw Itinerary
In the Response
Optional
[GetBooking] DE182875: travelers section sometimes does not contain passengerCode
In the Response
Optional
[GetBooking] DE182876: payments total incorrect when 2 PQs have the same price
In the Response
Optional
[GetBooking] DE183250: flightTotals.subtotal missing if no EquivalentFare present
In the Response
Optional
[GetBooking] DE183382: fareRules for ticketed PNR duplicated for same passengerType & Origin-Destination-Option
Relase note ID: 15125
v1.3 | October 15, 2020
- Additional information was added to the GetBooking endpoint for the car element; it now provides more details about the rate code, vehicle type, and vendor contact information.
API Information
What's New
- Additional information was added to the GetBooking endpoint for the car element; it now provides more details about the rate code, vehicle type, and vendor contact information.
Business Value
- Extensions in GetBooking now provide more information for car bookings.
Functional Updates And Enhancements
In the Response
Optional
- Parameter: getBookingRS.cars.pickUpContactInfo
-
Type: list
Description: Contains contact information for the pickup location.
Sample Value:
{
"phones": [
"866-434-1111"
]
}Note:
In the Response
Optional
- Parameter: getBookingRS.cars.dropOffContactInfo
-
Type: reference
Description: Contains contact information for the drop-off location.
Sample Value:
{
"phones": [
"866-434-1111"
]
}Note:
In the Response
Optional
- Parameter: getBookingRS.cars.vehicleTypeCode
-
Type: string
Description: The 4 character [ACRISS](https://www.acriss.org/car-codes/) code of the car.
Sample Value:
"vehicleTypeCode": "C"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.vehicleTypeName
-
Type: string
Description: The name of the car type based on the second character of the [ACRISS](https://www.acriss.org/car-codes/) code.
Sample Value:
"vehicleTypeName": "Two/Four Door"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.rateCode
-
Type: string
Description: The unique ID for an offer at a given vendor.
Sample Value:
"rateCode": "RCUD1"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.distanceAllowance
-
Type: string
Description: The included distance in the car rental booking.
Sample Value:
"distanceAllowance": "UNL"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.guaranteePaymentNote
-
Type: string
Description: The payment information provided to the vendor to guarantee the booking. Returned when structured data is not available.
Sample Value:
"guaranteePaymentNote": "GVI4XXXXXXXXXXX1111EXP 12 24-MONSTER"Note:
In the Response
Optional
- Parameter: getBookingRS.cars.specialInstructions
-
Type: string
Description: The special information provided to the vendor.
Sample Value:
"specialInstructions": "NON-SMOKING CAR PLEASE"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.refundPenaltyPolicyCode
-
Type: string
Description: The penalty code of a cancellation in the context of legacy GDS hotel content.
Sample Value:
"refundPenaltyPolicyCode": "01D"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.guaranteePaymentNote
-
Type: string
Description: Provides information regarding the guarantee provided for the legacy GDS hotel content.
Sample Value:
"guaranteePaymentNote": "GVI4XXXXXXXXXXX1111EXP 01 25-HOTEL"Note:
Resolved Issues
In the Response
Optional
DE177488: Empty travelers.address.freeText should not be returned.
In the Response
Optional
DE176306: No warning returned for missing fareRules/fareOffers.
In the Response
Optional
DE177573: travelerIindex not populated for flightTickets.
In the Response
Optional
DE178133: getBooking should not return empty arrays for flightOffers.
In the Response
Optional
DE178178: cars.pickUpContactInfo should not return null values for faxes and emergencyPhones.
In the Response
Required
DE178964: Missing Seat info for TravelerIndex 1 doesn't return empty array.
In the Response
Required
DE178964: Missing Seat info for TravelerIndex 1 doesn't return empty array.
Relase note ID: 14780
v1.2 | September 2, 2020
- A new method CancelFlightTickets has been introduced to the Booking Management API.
- For GetBooking additional information was added to the hotel element providing more details about vendor, room and fulfillment details.
- The construction of fareRules for GetBooking has been enhanced. This was done for both scenarios: Saved price quotes and issued tickets. Logic for different passenger type as well as more complex origin-destination-options has also been enhanced.
API Information
What's New
- A new method CancelFlightTickets has been introduced to the Booking Management API.
- For GetBooking additional information was added to the hotel element providing more details about vendor, room and fulfillment details.
- The construction of fareRules for GetBooking has been enhanced. This was done for both scenarios: Saved price quotes and issued tickets. Logic for different passenger type as well as more complex origin-destination-options has also been enhanced.
Business Value
- The introduction of Cancel Flight Tickets simplifies the voiding of electronic documents for ATPCO content. Instead of handling a complex sequence of API calls this service orchestrates multiple services in one call. This includes a recovery strategy in case of failure, handling of multiple documents, performing the action in a different PCC than the home PCC and update of the reservation.
New Features
In the Request
Required
- Parameter: cancelFlightTicketsRQ.tickets
-
Type: array
Description: Lists 13-digit electronic document numbers for tickets or EMDs which should be voided.
Sample Value:
{
"tickets": [
"0011234567890",
"0011234567891
]
}Note: Currently we support up to 12 documents in one call.
Functional Updates And Enhancements
In the Response
Optional
- Parameter: getBookingRS.cruises.cruiseStatusCode
-
Type: string
Description: We're returning status code and name for cruises now.
Sample Value:
"cruises": [
{
"itemId": "7",
"vendorCode": "VI",
"fromPortCode": "MIA",
"toPortCode": "SJU",
"departureDate": "2020-09-30",
"departureTime": "16:00:00",
"numberOfGuests": 2,
"cruiseStatusCode": "GK",
"cruiseStatusName": "Confirmed"
}
],Note: CruiseStatusName is returned based on the cruiseStatusCode.
In the Response
Optional
- Parameter: getBookingRS.agencyCustomerNumber
-
Type: string
Description: The new field agencyCustomerNumber contains the DK Number.
Sample Value:
{
"agencyCustomerNumber": "SABRE1",
"flightTickets": [
{
"number": "0721237616987",
"date": "2020-08-07",
"travelerIndex": 1,
"flightCoupons": [
{
"itemId": "9",
"couponStatus": "Not Flown",
"couponStatusCode": "I"
}
],
"payment": {
"subtotal": "444.00",
"taxes": "74.50",
"total": "518.50",
"currencyCode": "USD"
},
"ticketStatusName": "Issued",
"ticketStatusCode": "TE"
}
],
"request": {
"confirmationId": "XYZABC",
"returnOnly": [
"TICKETS"
]
}
}Note: The agencyCustomerNumber will be returned for all returnOnly options.
In the Response
Optional
- Parameter: getBookingRS.hotels.propertyId
-
Type: string
Description: The field will provide you with the unique property Id of each hotel.
Sample Value:
"propertyId": "52007"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.chainCode
-
Type: string
Description: The field returns the hotel chain code.
Sample Value:
"chainCode": "KC"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.chainName
-
Type: string
Description: This field provides the hotel chain name.
Sample Value:
"chainName": "KIMPTON HOTELS"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.guaranteeTypeCode
-
Type: int
Description: The field returns the code of the form of payment used to guarantee the booking.
Sample Value:
"guaranteeTypeCode": 5Note: The form of payment codes follow OTA standard.
In the Response
Optional
- Parameter: getBookingRS.hotels.guaranteeTypeName
-
Type: string
Description: The field returns the name of the form of payment used to guarantee of the booking.
Sample Value:
"guaranteeTypeName": "CREDIT CARD"Note: The form of payment names follow OTA standard.
In the Response
Optional
- Parameter: getBookingRS.hotels.specialInstructions
-
Type: string
Description: This field returns additional information provided to the property when booking, e.g. special preferences.
Sample Value:
"specialInstructions": "Upper floor please"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.room.roomTypeCode
-
Type: string
Description: The field returns the room type code applied by the vendor.
Sample Value:
"roomTypeCode": "1DN"Note:
In the Response
Optional
- Parameter: getBookingRS.hotels.room.roomRate
-
Type: Object
Description: This object will return amount and currency code of the applied rate per night before taxes.
Sample Value:
"amount": "46.60",
"currencyCode": "USD"Note:
Resolved Issues
In the Response
Optional
Incorrect ticketStatusCode and ticketStatusName when timestamps are overlapping.
In the Request
Optional
GraphQL: Invalid input for Enum 'FlightStatusNameEnum'
In the Response
Optional
Hotel refundPenalties Incorrectly display in Get Booking Response
Relase note ID: 14363
v1.1 | July 21, 2020
- A new feature is introduced for CancelBooking, which allows you to cancel a booking and void the corresponding tickets or EMD's in one call by specifying the flightTicketOperation "VOID" in the request.
- GetBooking contains information regarding the baggage policy per flight and traveler. Now in addition, enhancements for hotel and ticket status is introduced.
API Information
What's New
- A new feature is introduced for CancelBooking, which allows you to cancel a booking and void the corresponding tickets or EMD's in one call by specifying the flightTicketOperation "VOID" in the request.
- GetBooking contains information regarding the baggage policy per flight and traveler. Now in addition, enhancements for hotel and ticket status is introduced.
Business Value
- Version 1.1 brings additional value to the Booking Management API by combining segment and ticket handling for CancelBooking, where customers had to perform multiple steps to void tickets or EMD's and then cancel the segments. It's just one call for everything now.
- User will have full details about baggage allowance and related charges with the introduction of fareOffers section.
New Features
In the Request
Optional
- Parameter: flightTicketOperation
-
Type: string
Description: Defines the operation applied to the electronic documents in the booking. If not used, only segments will be cancelled and the electronic documents remain untouched. Currently there is no support for the NDC Orders.
Sample Value:
{
"confirmationId": "ABCDEF",
"retrieveBooking": false,
"cancelAll": true,
"flightTicketOperation": "VOID",
"errorHandlingPolicy": "ALLOW_PARTIAL_CANCEL"
}Note: Currently, only the flightTicketOperation "VOID" is supported. Support for refunds is on our roadmap.
In the Response
Optional
- Parameter: fareOffers
-
Type: list
Description: Lists ancillary offers for selected flights identified by itemId flight references.
Sample Value:
{
"fareOffers": [
{
"travelerIndices": [
1
],
"flights": [
{
"itemId": "7"
}
],
"cabinBaggageAllowance": {
"maximumPieces": 1,
"totalWeightInKilograms": 7
},
"checkedBaggageAllowance": {
"totalWeightInKilograms": 30
},
"checkedBaggageCharges": [
{
"maximumWeightInPounds": 33,
"maximumWeightInKilograms": 15,
"numberOfPieces": 1,
"fee": {
"amount": "399.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 44,
"maximumWeightInKilograms": 20,
"numberOfPieces": 1,
"fee": {
"amount": "528.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 55,
"maximumWeightInKilograms": 25,
"numberOfPieces": 1,
"fee": {
"amount": "656.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 66,
"maximumWeightInKilograms": 30,
"numberOfPieces": 1,
"fee": {
"amount": "785.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 77,
"maximumWeightInKilograms": 35,
"numberOfPieces": 1,
"fee": {
"amount": "912.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 11,
"maximumWeightInKilograms": 5,
"numberOfPieces": 1,
"fee": {
"amount": "143.00",
"currencyCode": "USD"
}
},
{
"maximumWeightInPounds": 22,
"maximumWeightInKilograms": 10,
"numberOfPieces": 1,
"fee": {
"amount": "272.00",
"currencyCode": "USD"
}
},
{
"numberOfPieces": 1,
"specialItemDescription": "WEIGHT SYSTEM CHARGE",
"fee": {
"amount": "30.00",
"currencyCode": "USD"
}
},
{
"numberOfPieces": 1,
"specialItemDescription": "ASSISTIVE DEVICES 2",
"fee": {
"amount": "42.00",
"currencyCode": "AUD"
}
}
]
}
],
"request": {
"confirmationId": "RIGDDB",
"returnOnly": [
"BAGGAGE_POLICY"
]
}
}Note: The source of this information is Get Ancillary Offers API.
Functional Updates And Enhancements
In the Response
Optional
- Parameter: US917209: Add Status Info to Hotel
-
Type: string
Description: For hotels, the hotelStatusCode and hotelStatusName are supported now.
Sample Value:
{
"startDate": "2020-11-03",
"endDate": "2020-11-04",
"hotels": [
{
"itemId": "15",
"confirmationId": "ABC123",
"hotelName": "WINDSOR GUEST HOUSE",
"address": {
"street": "325 WEST 11TH AVENUE",
"city": "VANCOUVER",
"postalCode": "V5Y1T3",
"countryCode": "CA"
},
"checkInDate": "2020-11-03",
"checkInTime": "00:00",
"checkOutDate": "2020-11-04",
"checkOutTime": "00:00",
"room": {
"roomType": "Basic Double Room with Shared Bathroom - Breakfast included in the price - Genius Business - Booking.com rate",
"quantity": 1,
"description": "Basic Double Room with Shared Bathroom - Breakfast included in the price - Genius Business - Booking.com rate"
},
"isRefundable": false,
"hotelStatusCode": "HK",
"hotelStatusName": "Confirmed"
}
],
"request": {
"confirmationId": "JMRIPG",
"returnOnly": [
"HOTELS"
]
}
}Note: Only the current status will be reflected.
In the Response
Optional
- Parameter: US933173: Add Ticket Status to flightTickets
-
Type: string
Description: For each flightTicket the ticketStatusName and ticketStatusCode will be returned. Currently, three ticketStatusNames are supported: Issued, Voided, Exchanged/Refunded. The coupons status is not taken into consideration for definition of ticket status.
Sample Value:
{
"flightTickets": [
{
"number": "6071234567890",
"date": "2020-07-03",
"travelerIndex": 1,
"flightCoupons": [
{
"itemId": "7",
"couponStatus": "Not Flown",
"couponStatusCode": "I"
}
],
"payment": {
"subtotal": "1347.00",
"taxes": "238.70",
"total": "1585.70",
"currencyCode": "USD"
},
"ticketStatusName": "Issued",
"ticketStatusCode": "TE"
}
],
"request": {
"confirmationId": "ABCDEF",
"returnOnly": [
"TICKETS"
]
}
}Note: Only the current status will be reflected.
Resolved Issues
In the Response
Required
In the Response
Required
DE168797: GetBooking - Missing Travel Index for Infant Ticket
In the Response
Required
DE168912: CancelBooking - Missing EndTransaction when calling with ATK Token
In the Response
Required
DE169025: GetBooking - Inconsistency in the response regarding Flights
In the Response
Required
DE169026: GetBooking - Duplicate Flight Ticket Numbers
In the Response
Required
DE169553: CancelBooking - null value in CSL_CANCEL_PROBLEM error description
In the Response
Required
DE170028: GetBooking - returnOnly "TICKETS" not returning flightTickets
In the Response
Required
DE170031: GetBooking - Invalid returnOnly option returns INTERNAL_SERVER_ERROR
In the Response
Required
DE170222: GetBooking - returnOnly "PAYMENTS" doesn't return Payments
In the Response
Required
DE171600: GetBooking - Not latest TicketDetails used for ticketStatus
Relase note ID: 14354
v1 | April 17, 2020
API Information
What's New
Business Value
- The Booking Management API is a part of Sabre's Business Services, that allows users to manage their Sabre reservations/bookings in a better way. This API provides a normalized set of services to manage both Sabre Passenger Name Records (PNRs) and Sabre Orders, by simplifying these implementations and ensuring that both expert and novice users can integrate and adopt Sabre APIs in the most seamless way possible.
New Features
In the Request/Response
N/A
- Parameter:
-
Type:
Description:
Sample Value:
Note:
Relase note ID: 14213
v1.6 | April 7, 2021
- GetBooking will return additional data for the creation of the booking. This will include the sine of the user who created it, creation date & time, the PCC the booking was created in, the PCC the creating user is coming from, and the prime host ID.
- GetBooking will start returning structured data about Other Service Information (OSI). The information provided will include the airline, chain (hotels) or vendor (cars, trains, cruises) codes, and the service message. Optionally, the traveler index can also be returned.
- CreateBooking will support sending other service information (OSI).
- CreateBooking will allow filtering the profiles by ID.
- CheckFlightTickets will start supporting requests by confirmationId. This allows you to check all ATPCO-Tickets of a reservation and check the refund or void option of a NDC Order.
- CancelBooking will support voids or refunds for NDC orders. Simply provide the offerItemId to the request and we take care of the rest.
API Information
What's New
- GetBooking will return additional data for the creation of the booking. This will include the sine of the user who created it, creation date & time, the PCC the booking was created in, the PCC the creating user is coming from, and the prime host ID.
- GetBooking will start returning structured data about Other Service Information (OSI). The information provided will include the airline, chain (hotels) or vendor (cars, trains, cruises) codes, and the service message. Optionally, the traveler index can also be returned.
- CreateBooking will support sending other service information (OSI).
- CreateBooking will allow filtering the profiles by ID.
- CheckFlightTickets will start supporting requests by confirmationId. This allows you to check all ATPCO-Tickets of a reservation and check the refund or void option of a NDC Order.
- CancelBooking will support voids or refunds for NDC orders. Simply provide the offerItemId to the request and we take care of the rest.
Business Value
- Full integration of void and refund in cancelBooking across ATCPO and NDC content.
- Support for other service information in createBooking and getBooking.
- CreateBooking will now automatically send infant traveler SSRs to the airline.
New Features
In the Request
Optional
- Parameter: CreateBookingRequest.profiles.filterId
-
Type: string
Description: Profile Filters
Sample Value:
"filterId": "112676753"Note:
In the Request
Optional
- Parameter: CreateBookingRequest.travelers.emails
-
Type: Array
Description: Associate a list of email addresses to a traveler.
Sample Value:
"emails": [
"john@smith.family.priv"
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.otherServices
-
Type: Array
Description: Contains Other Service Information (OSI) sent to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Response
Optional
- Parameter: GetBookingResponse.creationDetails
-
Type: Object
Description: Contains details about the creation of a booking.
Sample Value:
"creationDetails": {
"creationUserSine": "A12",
"creationDate": "2021-01-09",
"creationTime": "15:00",
"userWorkPcc": "AB12",
"userHomePcc": "CD34",
"primeHostId": "1S"
},Note:
In the Response
Optional
- Parameter: GetBookingResponse.otherServices
-
Type: Array
Description: Contains Other Service Information (OSI) sent to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Request
Optional
- Parameter: CancelBookingRequest.offerItemId
-
Type: String
Description: Offer ID referencing the cancel option for a NDC order. This ID must be applied when cancelling an order to receive a refund or void.
Sample Value:
"offerItemId": "cb7778589bcbklg7tkkp8sdo50"Note:
In the Request
Optional
- Parameter: CheckFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: VoidFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: RefundFlightTicketsRequest.confirmationId
-
Type: String
Description: The booking reference ID as shown in the source supplier/vendor system. For `SABRE`, this is the PNR Locator value.
Sample Value:
"confirmationId": "GLEBNY"Note:
Functional Updates And Enhancements
In the Request
Optional
- Parameter: CreateBookingRequest.profiles
-
Type: Object
Description: Additional filtering options for profile selection.
Sample Value:
"profiles": [
{
"profileName": "TESTPROFILE",
"profileTypeCode": "TVL",
"uniqueId": "ABC123",
"domainId": "G7HE",
"filterId": "112676753"
}
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.otherServices
-
Type: Array
Description: Possibility to send other service information (OSI) to an airline.
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"chainCode": "BY",
"vendorCode": "ZE",
"travelerIndex": 1,
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Request
Optional
- Parameter: CreateBookingRequest.travelers.emails
-
Type: Array
Description: Lists emails associated to a traveler.
Sample Value:
"emails": [
"john@smith.family.priv"
]Note:
In the Request
Optional
- Parameter: getBookingRequest.returnOnly
-
Type: Array
Description: Additional returnOnly option "OTHER_SERVICES" to return only other service information (OSI)
Sample Value:
{
"confirmationId": "ABCDEF",
"returnOnly": ["OTHER_SERVICES"]
}Note:
In the Response
Optional
- Parameter: GetBookingResponse.otherServices
-
Type: Array
Description: Lists other service information (OSI)
Sample Value:
"otherServices": [
{
"airlineCode": "AA",
"travelerIndex": 1,
"serviceMessage": "TEST OSI MESSAGE"
},
{
"chainCode": "BY",
"serviceMessage": "/CX-J674A0957C0"
},
{
"vendorCode": "ZE",
"serviceMessage": "/CX-J674A0957C0"
}
]Note:
In the Response
Optional
- Parameter: GetBookingResponse.creationDetails
-
Type: Object
Description: Provides information about the creation of the booking.
Sample Value:
"creationDetails": {
"creationUserSine": "A12",
"creationDate": "2021-01-09",
"creationTime": "15:00",
"userWorkPcc": "AB12",
"userHomePcc": "CD34",
"primeHostId": "1S"
}Note:
In the Response
Optional
- Parameter: GetBookingResponse.futureTicketingPolicy
-
Type: Object
Description: Contains ticketing instructions for a booking.
Sample Value:
"futureTicketingPolicy": {
"ticketingPcc": "AB12",
"queueNumber": "55",
"ticketingDate": "2019-07-09",
"ticketingTime": "11:00",
"comment": "TICKET BEFORE TUES"
}Note:
In the Request
Optional
- Parameter: CancelBookingRequest.flightTicketOperation
-
Type: String
Description: New option "REFUND" to cancel the booking and refund all tickets.
Sample Value:
"flightTicketOperation": "REFUND"Note:
In the Request
Optional
- Parameter: CancelBookingRequest.designatePrinters.
-
Type: Array
Description: Additional printer designation options were added: hard copy printer, ticket printer and invoice&itinerary printer
Sample Value:
"designatePrinters": [
{
"hardcopy": {
"address": "EF34GH",
"spacing": "1"
},
"invoiceItinerary": "AB12CD",
"ticket": {
"address": "EF34GH",
"countryCode": "RU"
}
}
]Note:
In the Request
Optional
- Parameter: CancelBookingRequest.offerItemId
-
Type: String
Description: The offerItemId allows to define action on NDC tickets. Use checkFlightTickets to obtain the possible refund or void offers, including the offerItemId.
Sample Value:
"offerItemId": "cb7778589bcbklg7tkkp8sdo50"Note:
In the Request
Optional
- Parameter: CheckFlightTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to verify refund and void options for the entire booking. This will check the entire list ATPCO tickets in a PNR or the NDC Order.
Sample Value:
"confirmationId": "GLEBNY"Note:
In the Request
Optional
- Parameter: RefundFlighTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to refund the entire list ATPCO tickets in a PNR.
Sample Value:
"confirmationId": "GLEBNY"Note: Not supported for NDC Orders.
In the Request
Optional
- Parameter: VoidFlightTicketsRequest.confirmationId
-
Type: String
Description: Use the confirmationId to void the entire list ATPCO tickets in a PNR.
Sample Value:
"confirmationId": "GLEBNY"Note: Not supported for NDC Orders.
Resolved Issues
In the Request
Optional
DE191705: voidFlightTickets with confirmationId returns tickets array in request
In the Request
Optional
DE193728: cancelBooking with Sabre Order Id fails
In the Response
Optional
DE193144: Baggage allowance showing in itinerary when there is no PQ in reservation
In the Request
Optional
DE193727: cancelBooking with offerItemId fails [NDC]
In the Request
Optional
DE192788: cancelBooking Cannot deserialize value of type `ReturnOnlyEnum` from String
In the Response
Optional
DE190631: CONTEXT_CHANGE_PROBLEM when using targetPcc
Relase note ID: 15802