Booking Management API

Create Booking and Get Booking now support new NDC capabilities, i.e. multi-adult traveler bookings, contact information associated with a name, and additional identity document types (Visa, Known Traveler Number, and Redress Number).
Get Booking logic is enhanced to return additional brand details for NDC bookings.
Additional mappings are added to the Get Booking method to return extra information about identity documents (lap-child indicator, residence country code).
Information on the issuing country for the Known Traveler Number and Redress Number documents as well as the expiration date for VISA documents (DOCO formats) are now required when using the Create Booking method.
Get Booking now returns information about the purchase deadline stored in the Price Quote (PQ).
The default logic for unmapped passenger types returned in Get Booking is now updated – the passenger code is always returned.
Create Booking now supports adding endorsement details as a new pricing qualifier.
Further enhancements to the error handling logic – additional scenarios are now covered across all BM API methods with more descriptive information for the users. Refer to the BM API error lists for further details.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.17

Target Audience

TN

Environment

Production

What's New

Create Booking and Get Booking now support new NDC capabilities, i.e. multi-adult traveler bookings, contact information associated with a name, and additional identity document types (Visa, Known Traveler Number, and Redress Number).
Get Booking logic is enhanced to return additional brand details for NDC bookings.
Additional mappings are added to the Get Booking method to return extra information about identity documents (lap-child indicator, residence country code).
Information on the issuing country for the Known Traveler Number and Redress Number documents as well as the expiration date for VISA documents (DOCO formats) are now required when using the Create Booking method.
Get Booking now returns information about the purchase deadline stored in the Price Quote (PQ).
The default logic for unmapped passenger types returned in Get Booking is now updated – the passenger code is always returned.
Create Booking now supports adding endorsement details as a new pricing qualifier.
Further enhancements to the error handling logic – additional scenarios are now covered across all BM API methods with more descriptive information for the users. Refer to the BM API error lists for further details.

Business Value

New NDC functionalities are added to the Create Booking and Get Booking methods. Customers can now create and display multi-adult traveler NDC bookings. Travelers can have dedicated contact information (phones and emails) assigned to them. Support for new types of identity documents (Visa, Known Traveler Number, Redress Number) is added as well.
Information about additional branded fare (Price Class) attributes is now available in the Get Booking response for NDC bookings.
Mapping for identity documents is expanded to support residence country code and lap child indicator details in the Get Booking method, for multiple DOCS, DOCO, and DOCA documents.
Industry mandate regarding mandatory information (expiration date for visa documents; issuing country details for Redress Number and Known Traveler Number documents) is incorporated in the Create Booking method.
Customers can now verify in the Get Booking response when a stored fare must be ticketed. This is an additional piece of information to plan fulfillment operations accordingly.
Get Booking now allows for identification of traveler code details even if the specific mapping logic is missing. Instead of the ‘SPECIAL’ text, the traveler code always contains a 3-letter code (https://central.sabre.com/s/article/passenger-type-codes-index).
Endorsement information is now supported in the Create Booking method. Customers can specify desired details as one of the pricing qualifiers.

"identityDocuments": [
{
"documentNumber": "67676767",
"documentType": "KNOWN_TRAVELER_NUMBER",
"issuingCountryCode": "US"
}
]

Note: The `issuingCountryCode` property is now mandatory for the Known Traveler Number and Redress Number documents.

Resolved Issues

In the Request

Optional

Create Booking issue fixed. The `travelerIndex` property is no longer required for the OSI special services.

Relase note ID: 18307

Get Booking now supports unmasking of payment card details for customers with a specific EPR keyword (CCVIEW).
Get Booking now returns two additional passenger type codes: LBR and LNN.
BM API methods contain timestamp information about when a specific request was processed by the Sabre systems.
Check Flight Tickets logic is enhanced to properly identify tickets eligible for the void operation in case of bookings containing surface segments (ARNK).
Error handling improvements – additional scenarios are now covered across all BM API methods with more descriptive information for the users. Refer to BM API error lists for further details.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.16

Target Audience

TN

Environment

Production

What's New

Get Booking now supports unmasking of payment card details for customers with a specific EPR keyword (CCVIEW).
Get Booking now returns two additional passenger type codes: LBR and LNN.
BM API methods contain timestamp information about when a specific request was processed by the Sabre systems.
Check Flight Tickets logic is enhanced to properly identify tickets eligible for the void operation in case of bookings containing surface segments (ARNK).
Error handling improvements – additional scenarios are now covered across all BM API methods with more descriptive information for the users. Refer to BM API error lists for further details.

Business Value

The Get Booking method allows returning of unmasked payment card information for the customers that have EPRs with the CCVIEW keyword.
Customers can now obtain information regarding LBR and LNN passenger types, which are used by Air New Zealand for their SEAT ONLY fares.
Additional logic is added to the Check Flight Tickets method, allowing customers to properly validate by means of `isVoidable` property whether tickets issued for an itinerary with ARNK segments are eligible for the void operation.
Timestamp details added to BM API responses improve troubleshooting of potential customer issues by helping locate the API call within internal logging applications.

New Features

Note: The two newly supported codes are LBR and LNN.

In the Response

Optional

Parameter: CheckTicketsResponse.tickets.isVoidable

Type: Boolean

Description: If true, the electronic document meets void procedure requirements.

Sample Value:

"tickets": [{
"number": "1606721193277",
"isVoidable": true,
"isRefundable": true,
"refundTotals": {
"subtotal": "3848.00",
"taxes": "555.55",
"total": "4403.55",
"currencyCode": "PLN"
}
}
]

Note: This enhancement makes it possible to properly identify tickets eligible for the void operation within bookings that contain surface segments (ARNK).

Resolved Issues

In the Request

Optional

DE253517: Cancel Booking issue fixed, in which a simultaneous changes error affected the void flow. New retry logic has been implemented to recover from those scenarios.

In the Response

Optional

DE258285: Get Booking issue fixed, in which the leading zero was missing from the payment card expiry date.

Relase note ID: 17964

Get Booking and Create Booking now support additional gender type codes (UI and XI) for identity document special services (DOCO).
Get Booking will now return form of payment information for an expanded list of cash and check entries.
Group booking logic was enhanced in the Get Booking method. The traveler’s association is now determined by the means of an additional `isGrouped` boolean value.
Model improvements – property patterns were updated to reflect additional customer requirements and/or system limitations.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.15

Target Audience

TN

Environment

Production

What's New

Get Booking and Create Booking now support additional gender type codes (UI and XI) for identity document special services (DOCO).
Get Booking will now return form of payment information for an expanded list of cash and check entries.
Group booking logic was enhanced in the Get Booking method. The traveler’s association is now determined by the means of an additional `isGrouped` boolean value.
Model improvements – property patterns were updated to reflect additional customer requirements and/or system limitations.

Business Value

You can now obtain (Get Booking) and pass (Create Booking) identity document details intended for infant travelers. An enhancement for the new codes UI (Undisclosed Infant) and XI (Unspecified Infant) was implemented with additional logic to automatically determine proper code usage based on the traveler’s age and type.
Additional logic was added in Get Booking, which allows you to obtain the form of payment information stored in the booking when using FOP entries with `CA`, `CK`, and `CHEQUE` values.
Get Booking will now return additional information regarding group bookings. You can now verify a traveler’s assignation to a group by checking the `isGrouped` property value.

Note:

Functional Updates And Enhancements

In the Response

Optional

Parameter: GetBoookingResponse.payments.formsOfPayment.type

Type: String

Description: Identifies the type of payment method. The MISCELLANEOUS payment method must be activated on the agency level and requires a specific payment credit code. INSTALLMENTS is used for BSP Brazil customers only and refers to a payment by means of card installments commonly referred to as "parcelado". VIRTUAL_CARD, AGENCY_NAME, AGENCY_IATA, CORPORATE, and COMPANY_NAME are used for hotel bookings. `VOUCHER` is used for vehicle bookings.

Sample Value:

"formsOfPayment": [
{
"type": "CASH"
}
]

Note: Additional mapping was added for the CASH and CHECK forms of payments. The application now supports the form of payment information created by using `CA`, `CK`, and `CHEQUE` values in the FOP entries.

In the Request

Optional

Parameter: CreateBookingResponse.agency.agencyCustomerNumber

Type: String

Description: Contains the agency's customer DK number. Can be a six, seven, or ten character string.

Sample Value:

"agency": {
"address": {
"name": "John Smith",
"street": "1230 Ellen Ave, apt 10",
"city": "Dallas",
"stateProvince": "TX",
"postalCode": "75063",
"countryCode": "US",
"freeText": "John Smith\n1230 Ellen Ave, apt 10\nDallas, TX 75063\nUS"
},
"agencyCustomerNumber": "ABC123467",
"ticketingPolicy": "TODAY"
}

Note: The pattern for the `agencyCustomerNumber` property was updated to: '^[0-9A-Z]{6}([1-9A-Z*]{1}|[0-9A-Z]{4})?$'. The same change was implemented for the `GetBookingResponse.agencyCustomerNumber` property.

Resolved Issues

In the Request

Optional

DE245121: Improved sorting logic in Get Booking to mitigate an issue with duplicated special service items caused by the presence of empty space characters in text information associated with the SSR.

Relase note ID: 17544

Get Booking now returns additional seat information, like status and IATA-defined characteristic codes, for both ATPCO and NDC flight bookings.
Create Booking now supports passing flight-related information for CSL hotel bookings.
Get Booking now returns additional information regarding baggage allowance for NDC bookings. Customers can now easily identify baggage allowance information regardless of the booking type (APTCO or NDC).
Get Booking now supports group bookings.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.14

Target Audience

TN

Environment

Production

What's New

Get Booking now returns additional seat information, like status and IATA-defined characteristic codes, for both ATPCO and NDC flight bookings.
Create Booking now supports passing flight-related information for CSL hotel bookings.
Get Booking now returns additional information regarding baggage allowance for NDC bookings. Customers can now easily identify baggage allowance information regardless of the booking type (APTCO or NDC).
Get Booking now supports group bookings.

Business Value

Seat logic has been expanded in the Get Booking method. For both ATPCO and NDC bookings, you can now retrieve status details (seat code and a meaningful description), as well as characteristic codes associated with the seat.
Additional logic has been added to the Create Booking method, allowing you to send flight-related information to hotel vendors when booking CSL content.
You can now obtain information about baggage allowance details not only for ATPCO flight bookings, but also NDC orders in the normalized response structure.
Get Booking will now return information regarding group bookings. You can verify group name, ID, number of travelers already added within a group, as well as the number of remaining names that are missing.

Note:

Functional Updates And Enhancements

In the Request

Optional

Parameter: GetBookingRequest.returnOnly

Type: Array

Description: Lists the response sections returned by the service. If this list is empty or not provided, then the full structure is returned. By using this option, the application may exclude or simplify calls of downline APIs, which usually results in a significant performance boost.

Sample Value:

{
"confirmationId": "BFGBFG",
"returnOnly":[
"FORMS_OF_PAYMENT"
]
}

Note: FORMS_OF_PAYMENT value has been added to the existing list of options.

In the Response

Optional

Parameter: GetBookingResponse.fareOffers

Type: Array

Description: Lists ancillary offers for selected flights identified by itemId flight references.

Sample Value:

"fareOffers": [
{
"travelerIndices": [
1
],
"flights": [
{
"itemId": "8"
}
],
"cabinBaggageAllowance": {
"baggagePieces": [
{
"numberOfPieces": 1
}
]
},
"checkedBaggageAllowance": {
"baggagePieces": [
{
"maximumWeightInKilograms": 30
}
]
}
}
]

Note: Baggage allowance details will now be returned for NDC bookings.

Resolved Issues

In the Request

Optional

US1413541: Adding new error handling (UNABLE_TO_BOOK_HOTEL_LATE_PAYMENT_NOT_SUPPORTED) in the CreateBooking method for a scenario where guarantee type LATE is not supported by the hotel vendor.

In the Response

Optional

US1435135: Adding a more descriptive warning message regarding missing fareRules details for a scenario where manual PQ was stored in the booking.

In the Request

Optional

DE235018: Removing requirement regarding passenger code details in the profile path for the hotel bookings, to support customers without the “store passenger type in PNR” function activated in the agency TJR settings.

In the Request

Optional

DE235364: Adding new error handling (NO_PROFILE_DATA_MOVED_WRONG_PROFILE_TYPE) in the CreateBooking method for a scenario where an unsupported profile type has been identified.

In the Response

Optional

DE237243: Fixing bug in the GetBooking method with flight details mapping to the downline PO_PNRPricingRQ (flight numbers with leading “0”).

Relase note ID: 17346

A new method Modify Booking (BETA) has been released. Visit the dedicated Modify Booking method page to find out more about it.
GetBooking will start returning the form of payment information, which is stored in the booking.
GetBooking will start supporting payment policy details used for CSL hotel bookings.
GetBooking will start returning additional information regarding hotel content. Customers can now easily identify the type of hotel booking.
CreateBooking will start considering name associated phone numbers with higher priority rather than general contact information for hotel bookings.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.13

Target Audience

TN

Environment

Production

What's New

A new method Modify Booking (BETA) has been released. Visit the dedicated Modify Booking method page to find out more about it.
GetBooking will start returning the form of payment information, which is stored in the booking.
GetBooking will start supporting payment policy details used for CSL hotel bookings.
GetBooking will start returning additional information regarding hotel content. Customers can now easily identify the type of hotel booking.
CreateBooking will start considering name associated phone numbers with higher priority rather than general contact information for hotel bookings.

Business Value

Customers can now perform modifications of the existing booking by using Modify Booking method. The initial release allows for CSL hotel content changes. The capabilities of of this new method are described under the URL: https://developer.sabre.com/docs/rest_apis/trip/orders/booking_management_beta
Get Booking has been successfully moved to the PCI cluster. This change allowed adding functionality to return Form of Payment (FOP) information stored in the bookings.
Additional logic has been implemented in Get Booking method, to return details regarding payment policy and type of the hotel content. Customers can now obtain additional information about selected payment policy and distinguish between legacy and CSL (Sabre or aggregators) booking source.
Name associated phone numbers will now take precedence over general contact information during the hotel booking creation process.

Note: The default value of the `sourceTypeName` property is `Unknown`. This way `HotelSourceEnum` can be expanded in the future with a new source value, without breaking backward compatibility.

Resolved Issues

In the Response

Optional

DE231525: Fixing bug in Get Booking method with flight association logic for scenarios that contain an open ticket.

Relase note ID: 17220

GetBooking will start returning additional information regarding traveler association with flights and cars.
GetBooking will start supporting additional information associated with hotel bookings: corporate id and arrival/departure flight details.
GetBooking will start returning booking signature used to verify the state of the booking during modification (more information soon!).
GetBooking will start expanding traveler information based on the guest details stored in the hotel booking.
GetBooking will start returning agency IATA number if booking contains CSL (Content Services for Lodging) content.
CancelBooking schema will be slightly improved by removing unused, duplicated properties related to queue placement.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.12

Target Audience

TN

Environment

Production

What's New

GetBooking will start returning additional information regarding traveler association with flights and cars.
GetBooking will start supporting additional information associated with hotel bookings: corporate id and arrival/departure flight details.
GetBooking will start returning booking signature used to verify the state of the booking during modification (more information soon!).
GetBooking will start expanding traveler information based on the guest details stored in the hotel booking.
GetBooking will start returning agency IATA number if booking contains CSL (Content Services for Lodging) content.
CancelBooking schema will be slightly improved by removing unused, duplicated properties related to queue placement.

Business Value

Customers can now retrieve additional details associated with the existing hotel booking. Information like corporate id, guest’s email and phone numbers, as well as arrival and departure flight data, will be now, if applicable, present in the GetBooking response.
Introducing a booking signature will allow verifying the state of the booking and prevent from doing unexpected modifications.
Additional logic has been implemented to verify and retrieve guest information. This ensures more cohesive data in reference to traveler information returned by GetBooking.
Presence of the IATA number in the GetBooking response is a supplementary source of agency identification by the customers.
The removal of unused elements from the schema lets us maintain a high quality and complete API product.

"flights": [
{
"itemId": "22",
"confirmationId": "UEFTKF",
"sourceType": "ATPCO",
"flightNumber": 524,
"airlineCode": "AA",
"operatingFlightNumber": 524,
"operatingAirlineCode": "AA",
"fromAirportCode": "DFW",
"toAirportCode": "LAX",
"departureDate": "2022-09-20",
"departureTime": "07:00:00",
"arrivalDate": "2022-09-20",
"arrivalTime": "08:00:00",
"seats": [
{
},
{
},
{
"number": "22A"
}
],
"numberOfSeats": 3,
"cabinTypeName": "ECONOMY",
"cabinTypeCode": "Y",
"aircraftTypeCode": "321",
"aircraftTypeName": "AIRBUS",
"bookingClass": "Y",
"meals": [
{
"code": "R",
"description": "Refreshment"
}
],
"flightStatusCode": "HK",
"flightStatusName": "Confirmed",
"durationInMinutes": 180,
"distanceInMiles": 1235,
"travelerIndices": [
1,
2,
3
]
}
]

Note: Description update to include meaningful information regarding empty Seat objects.

Resolved Issues

In the Request

Optional

US1335214: Adding support for the infant tickets containing “INF” string prefix in the CancelBooking and VoidFlightTIckets methods.

Relase note ID: 17035

CreateBooking will start supporting the optional issuing country information for Known Traveler Number documents (DOCO formats).
CreateBooking will start supporting information about the place and date of issue for VISA identity documents (DOCO formats) as optional fields.
GetBooking will start supporting the expiration date for Visa documents (DOCO formats).
Void/Refund/Check Flight Tickets methods will start processing conjunctive ticket numbers.
GetBooking will start returning additional flight-related information: hidden stops and the number of seats occupied by the travelers.
GetBooking will allow obtaining additional information stored for hotel bookings like the guest association to a room and loyalty numbers.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.11

Target Audience

TN

Environment

Production

What's New

CreateBooking will start supporting the optional issuing country information for Known Traveler Number documents (DOCO formats).
CreateBooking will start supporting information about the place and date of issue for VISA identity documents (DOCO formats) as optional fields.
GetBooking will start supporting the expiration date for Visa documents (DOCO formats).
Void/Refund/Check Flight Tickets methods will start processing conjunctive ticket numbers.
GetBooking will start returning additional flight-related information: hidden stops and the number of seats occupied by the travelers.
GetBooking will allow obtaining additional information stored for hotel bookings like the guest association to a room and loyalty numbers.

Business Value

Customers can now specify issuing country details for Known Traveler Number documents, by passing required information in CreateBooking request.
Customers can now provide information regarding the place and date of issue for VISA identity documents in CreateBooking request. These details are considered optional.
The expiration date for Visa documents was included in the identity documents information in GetBooking. Information is consistent with the same functionality introduced in CreateBooking.
Customers can now use conjunctive ticket numbers (e.g.: 0167662548958/59) in their Void/Refund/Check Flight Tickets requests.
By adding hidden stop and number of seats information customers can obtain additional details associated with the existing air booking.
By supporting guest to room association and loyalty numbers customers can obtain additional details associated with the existing hotel booking.

Note:

Resolved Issues

Relase note ID: 16795

CreateBooking will start supporting the expiration date for Visa documents (DOCO formats).
GetBooking will start returning information about delivery and collection site/address present in the car bookings in a cohesive form.
GetBooking will allow obtaining information about the past date indicator for the flown flights.
GetBooking will start returning additional traveler information regarding name-associated phone numbers.
GetBooking will allow obtaining additional information stored in manual PQs. Now it is possible to check fare construction details, flight association and much more.
GetBooking has now improved roundtrip journeys logic – it can verify whether selected trip contains a multi-airport city.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.10

Target Audience

TN

Environment

Production

What's New

CreateBooking will start supporting the expiration date for Visa documents (DOCO formats).
GetBooking will start returning information about delivery and collection site/address present in the car bookings in a cohesive form.
GetBooking will allow obtaining information about the past date indicator for the flown flights.
GetBooking will start returning additional traveler information regarding name-associated phone numbers.
GetBooking will allow obtaining additional information stored in manual PQs. Now it is possible to check fare construction details, flight association and much more.
GetBooking has now improved roundtrip journeys logic – it can verify whether selected trip contains a multi-airport city.

Business Value

Customers can now follow the new industry mandate introduced by the IATA regarding the expiration date for Visa documents, by passing required information in CreateBooking request.
By adding delivery and collection site/address information customers can obtain the custom details specified for car bookings.
Name associated phone numbers were added to travel information in GetBooking. Information is consistent with the same functionality introduced in CreateBooking.
Added past date indicator allows to quickly identify a flown flight.
Additional details returned for manual PQs were added to further support pricing data analysis.
Added internal multi-airport city database, which improves journeys functionality. It allows identifying roundtrips with departure and arrival at the same city.

Note: Name associated phones will be removed from GetBookingResponse.contactInfo.phones array in the future major release of the BM API.

Functional Updates And Enhancements

In the Response

Optional

Parameter: GetBookingResponse.fares.fareConstruction

Type: Array

Description: Lists the components used to construct the fare.

Sample Value:

"fareConstruction": [
{
"flights": [
{
"itemId": "50"
}
],
"flightIndices": [
1
],
"fareBasisCode": "KL40MALP",
"isCurrentItinerary": true,
"checkedBaggageAllowance": {
"totalWeightInKilograms": 10
}
},

Note: Additional information is now returned for manual PQs.

In the Request

Optional

Parameter: CreateBookingRequest.travelers.identityDocuments.expiryDate

Type: string

Description: The expiration date of the identity document.

Sample Value:

"identityDocuments": [
{
"documentNumber": "0123456789",
"expiryDate": "2022-07-09",
"hostCountryCode": "US",
"documentType": "VISA",
"givenName": "John",
"middleName": "Jack",
"surname": "Smith",
"placeOfIssue": "FR",
"issueDate": "2021-05-21"
}
]

Note: The expiration date is now supported when sending Visa DOCO.

Resolved Issues

In the Response

Optional

DE216212: Fixing bug in GetBooking response with incorrect flight association in fare component information for hybrid bookings (NDC + ATPCO).

In the Response

Optional

DE218361: Fixing bug in GetBooking response to return missing ancillary offers when returnOnly option was specified in the request.

In the Response

Optional

DE218514: Fixing bug in GetBooking response to return missing DOCS SSRs.

In the Response

Optional

DE217175: Fixing bug in GetBooking response with an incorrect value for flightTotals, when multiple passengers are assigned to a single PQ.

In the Response

Optional

DE217199: Fixing bug in GetBooking response with missing mapping for extended location codes applied to the car booking.

Relase note ID: 16673

CreateBooking will support booking cars. Implementation covers adding car content into the reservation by means of a booking key.
CreateBooking will support Payment Service Directive 2 (PSD2) compliant Strong Customer Authentication (SCA) for payment cards when booking hotel content.
CreateBooking will now allow creating name-associated phone numbers.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.9

Target Audience

TN

Environment

Production

What's New

CreateBooking will support booking cars. Implementation covers adding car content into the reservation by means of a booking key.
CreateBooking will support Payment Service Directive 2 (PSD2) compliant Strong Customer Authentication (SCA) for payment cards when booking hotel content.
CreateBooking will now allow creating name-associated phone numbers.

Business Value

Car booking is now integrated into CreateBooking. New capabilities will allow booking cars exclusively and alongside flights and/or hotel content in a single request.
PSD2 is a new set of rules changing how consumers confirm their identity when making purchases online. The rules apply in full for card payments and CreateBooking will now support Strong Customer Authentication (SCA) for hotel bookings.
Name-associated phone numbers were added to provide additional flexibility in terms of contact information stored in the booking.

New Features

In the Request

Optional

Parameter: CreateBookingRequest.car

Optional

DE211540: Fixing bug in CreateBooking logic - incorrect segment numeration when ARNK segments are included in the booking.

In the Response

Optional

DE212274: Fixing bug in GetBooking response to return proper details about passenger type code (age information instead of generic code, e.g.: C04 instead of CNN), under GetBookingResponse.travelers.passengerCode.

In the Response

Optional

DE213068: Fixing bug in GetBooking response to return missing fare rules under GetBookingResponse.fareRules for INF passenger, once the booking is ticketed.

Relase note ID: 16637

CreateBooking will start supporting booking ancillaries. Initial implementation covers the air extras booking process for ATPCO flights. You can now assign selected ancillaries to a particular traveler, in a single request.
CreateBooking will support sending special service requests (SSR). This is another functionality further improving the trip experience – you can notify the airline about traveler’s preferences/additional information in an easy way.
GetBooking will start returning additional fare data obtained from Price Quote (PQ) details. Now it is possible to check the status of the fare, flight association, brand details and much more.
GetBooking will allow obtaining information about booked ancillaries. More to come with the next releases.
GetBooking will start returning information about SSRs present in the booking in a cohesive form.
CancelBooking/VoidFlightTickets/RefundFlightTickets will run corresponding ticket related operations for the customers with AUTO-END functionality activated on the PCC level.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.8

Target Audience

TN

Environment

Production

What's New

CreateBooking will start supporting booking ancillaries. Initial implementation covers the air extras booking process for ATPCO flights. You can now assign selected ancillaries to a particular traveler, in a single request.
CreateBooking will support sending special service requests (SSR). This is another functionality further improving the trip experience – you can notify the airline about traveler’s preferences/additional information in an easy way.
GetBooking will start returning additional fare data obtained from Price Quote (PQ) details. Now it is possible to check the status of the fare, flight association, brand details and much more.
GetBooking will allow obtaining information about booked ancillaries. More to come with the next releases.
GetBooking will start returning information about SSRs present in the booking in a cohesive form.
CancelBooking/VoidFlightTickets/RefundFlightTickets will run corresponding ticket related operations for the customers with AUTO-END functionality activated on the PCC level.

Business Value

Ancillaries and SSRs were integrated into CreateBooking and GetBooking. New capabilities will allow communicating with the airlines and pass/receive information about trip details, requirements, or enhancements.
Additional details for air fares were added to further support pricing data analysis.
Implemented AUTO-END functionality verification helps execute void/refund operations in a predictable manner.

New Features

Note:

Resolved Issues

In the Request

Optional

DE200410: Pattern correction for ticketing printers to allow using 1R and 1T codes (settlement methods for Russia).

In the Response

Optional

DE207661: Adding additional information in GetBooking response under GetBookingResponse.payments.flightCurrentTotals property, which contains a sum of charges only for issued tickets – voided, refunded/exchanged items are not taken into consideration.

In the Request

Optional

DE200951: VoidFlightTickets request validation, preventing from specifying multiple printer types under single printer address object.

In the Response

Optional

DE206825: Fixing bug in GetBooking response to return information about identity document status, under GetBookingResponse.flights.identityDocuments.status.

Relase note ID: 16445

CreateBooking will start support for hotels. By adding a hotel object to your createBookingRequest you will be able to add a hotel to your booking with just one API call. The object is normalized and supports all content types, including Sabre's Content Services for Lodging.
For all those who asked for more details on fares - We have you covered now! GetBooking will return details for fares based on price quotes for ATPCO bookings or based on the NDC orders. More to come with the next releases.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.7

Target Audience

TN

Environment

Production

What's New

CreateBooking will start support for hotels. By adding a hotel object to your createBookingRequest you will be able to add a hotel to your booking with just one API call. The object is normalized and supports all content types, including Sabre's Content Services for Lodging.
For all those who asked for more details on fares - We have you covered now! GetBooking will return details for fares based on price quotes for ATPCO bookings or based on the NDC orders. More to come with the next releases.

Business Value

Hotels were integrated into the seamless workflow for createBooking. It was never easier to book a hotel using an API.
Details for air fares were added to support you with analyzing the pricing data or optimizing you back-office workflows.

New Features

In the Request

Optional

Parameter: CreateBookingRequest.hotel

Type: object

Description: The object allows to add a hotel to your createBooking-request. This works across the different content types for hotels in Sabre.

Sample Value:

"hotel": {
"useCsl": true,
"bookingKey": "d9e73f0d-5f90-4b43-9c86-2d88a732604f",
"corporateDiscountCode": 6878700,
"rooms": [
{
"isSmoking": false,
"bedTypeCode": 3,
"physicalDisabilityCode": 3,
"roomExtras": [
{
"roomExtraType": 26,
"quantity": 1,
"amount": "100.00"
}
],
"travelerIndices": [
1
]
}
],
"specialInstruction": "Need a wi-fi in the room.",
"paymentPolicy": "DEPOSIT",
"formOfPayment": 1
}

Note:

In the Response

Optional

Parameter: getBookingResponse.fares

Optional

DE196845: Wrong travelerIndices in fareOffers section for split PNR's [getBooking]

Relase note ID: 16267

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.
CreateBooking will now automatically send infant traveler SSRs to the airline.
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

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.6

Target Audience

TN

Environment

Production

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.
CreateBooking will now automatically send infant traveler SSRs to the airline.
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.

"confirmationId": "GLEBNY"

Note: Not supported for NDC Orders.

Resolved Issues

Relase note ID: 15802

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

Response Format

JSON

Method/Endpoint

/v1/trip/orders/

Current Version

1.5

Target Audience

TN

Environment

Production

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

DE183115: no message Context Created for cancelBooking & void Ticket

Relase note ID: 15543

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

Response Format

JSON

Method/Endpoint

/v1/trip/orders/getBooking | /v1/trip/orders/cancelFlightTickets | /v1/trip/orders/cancelBooking

Current Version

1.4

Target Audience

TN

Environment

Production

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.

Relase note ID: 15125

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

Response Format

JSON

Method/Endpoint

/v1/trip/orders/getBooking /v1/trip/orders/cancelFlightTickets /v1/trip/orders/cancelBooking

Current Version

1.3

Target Audience

TN

Environment

Production

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.

Note:

Resolved Issues

In the Response

Required

DE178964: Missing Seat info for TravelerIndex 1 doesn't return empty array.

Relase note ID: 14780

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

Response Format

JSON

Method/Endpoint

/v1/trip/orders/getBooking /v1/trip/orders/cancelFlightTickets /v1/trip/orders/cancelBooking

Current Version

1.2

Target Audience

TN

Environment

Production

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

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

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

Response Format

JSON

Method/Endpoint

/v1/trip/orders

Current Version

1.1

Target Audience

TN

Environment

Production

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

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

DE171600: GetBooking - Not latest TicketDetails used for ticketStatus

Relase note ID: 14354

This initial release of the Booking Management API introduces two methods: GetBooking and CancelBooking.

API Information

Response Format

JSON

Method/Endpoint

/v1/trip/orders

Current Version

1

Target Audience

TN

Environment

Production

What's New

This initial release of the Booking Management API introduces two methods: GetBooking and CancelBooking.

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.

Relase note ID: 14294

v1.17 | April 5, 2023

API Information

What's New

Business Value

New Features

In the Request

Optional

In the Request

Optional

In the Response

Optional

In the Response

Optional

In the Response

Optional

Functional Updates And Enhancements

In the Request

Required

In the Request

Optional

In the Request

Optional

In the Response

Optional

In the Request

Required

In the Request

Required

Resolved Issues

In the Request

Optional

In the Request

Optional

In the Request

Optional

In the Request

Optional

In the Request

Optional

In the Response

Optional

In the Request

Optional

v1.16 | February 21, 2023

API Information

What's New

Business Value

New Features

In the Request

Optional

In the Response

Optional

Functional Updates And Enhancements

In the Response

Optional

In the Response

Optional

Resolved Issues

In the Request

Optional

In the Response

Optional

v1.15 | September 30, 2022

API Information

What's New

Business Value

New Features

In the Request

Optional

In the Response

Optional

In the Response

Optional

Functional Updates And Enhancements

In the Response

Optional

In the Request

Optional

Resolved Issues

In the Request