Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: CreditVerificationLLSRQ
Service Action Code: TravelItineraryAddInfoLLSRQ
Service Action Code: InventoryManageRulesRQ
- Added new rule conditions: PhysicalPointOfSale, SeatMapAvailability, SeatMapCapacity, SeatMapLoadFactor, STGAvailabilityCabin, STGAvailabilityFareClass, STGCapacity, STGLoadFactor, STGBookingCount, AuFactor
- Added new rule actions: STGIncrease, STGDecrease, STGSuppressToZero, STGUnsuppress, STGInhibit, STGUninhibit, DoNotSendDpAdjustments, DoNotSendFloorPrice, DoNotSendCeilingPrice, IncreaseFloorPrice, DecreaseFloorPrice, IncreaseCeilingPrice, DecreaseCeilingPrice, AdjustDpFare, AdjustFloorPrice
Method/Endpoint: / All API for Digital Connect Check-In
- New Features
- Mandate – UAE Secure Boarding
- Support 3DS 2.0 in Payment Process – New Requirements
- Support for Mutli-Segment Boarding Passes
- Store Baggage Weight and send it in UpdateReservation
- Support Infant Added as an Edit Code
- Enhance Segment Selection Process
- Defect Fixes
- G3 G2S Cutover DW Unable to Change Seat – “Error Occurred While Loading Seat Map”
- G3D0 DCCI ERR.DCCI.APP.INTERNAL_EROOR | pnrlookup Group Booking
- DXCI 2.6 PROD
Service Action Code: PassengerDetailsRQ
- Modified .../RemarkInfo/Remark to unbounded. - This allows for more than 98 remarks in a single PassengerDetailsRQ call. This is an update to existing service version 3.4.0.
- Added an additional TravelItineraryAddInfoLLSRQ call for Corporate ID - From now on /PassengerDetailsRQ/TravelItineraryAddInfoRQ/CustomerInfo/Corporate can be combined with other qualifiers, because the ID will be sent in the initial TravelItineraryAddInfoLLSRQ call, before adding other information to the session state. This is an update to existing service version 3.4.0.
- Modified the limit for splitting Add Remark requests - Abacus remark limit is 779 characters, INFINI is 799 so we lowered the limit to 750 characters. The logic is still approximate but this functionality will now serve a broader base of customers. This is an update to existing service version 3.4.0.
- (10/18/2021) Integrated the latest version of TravelItineraryAddInfoLLSRQv2.2.1 - With this change the response for addition of Address lines on airline Partitions will be interpreted as successful.
- (10/28/2021) The API will return Strong Customer Authentication information saved in sessions and reservations when re-displaying the reservation at /PassengerDetailsRS/TravelItineraryReadRS/TravelItinerary/OpenReservationElements/OpenReservationElement/FormOfPayment/PaymentCard/StrongCustomerAuthentication
- (12/09/2021) Added capability to pass Visa special service document expiration date at .../SpecialReqDetails/SpecialServiceRQ/SpecialServiceInfo/AdvancePassenger/Document/Visa/@ExpirationDate
Method/Endpoint: /v1.2.1/air/ticket
- Extended sleep/delay logic for future ticketing lines. When API receives the "F LINE PROCESSING STARTED" warning message from AirTicketLLSRS, it will will wait 2000 ms for each future ticketing line that is sent in the AirTicketRQ in order to successfully complete the ticketing transaction.
- Added a delay before 2nd call to TKT_DocumentServicesRQ - This is done to mitigate cases where multiple tickets were issued but only some of them are visible in the ticketing database, the extra delay of 500 ms aims to mitigate the problem.
- Added AirTicketRQ.PostProcessing.actionOnBackDatePrice - The API was enhanced to handle `UNABLE TO TICKET STORED FARE - PQ CONTAINS BACK DATE PRICE` ticketing mask. By default, the API will attempt to "R" - Reprice the stored fare, however the user can specify to "O" - Override or "Q" - Quit as well.
- Extend future line logic with Ticketing Mask detection. - As of now, when future ticketing line processing starts, the API will also react to known ticketing mask messages via SabreCommandLLSRQ.
- (03/08/2022) Enabled user controlled delays between multiple ticketing transactions as a way to limit 'SIMULTANEOUS CHANGES' error occurrences. Added AirTicketRQ.PostProcessing.TicketingInterval.waitInterval to allow the user to tell the API to wait between subsequent .Ticketing transactions.
- (03/08/2022) The API will now handle a very specific corner case related to multiple Future Line issuance. If you decide to quit upon encountering so-called 'ticketing masks' (acceptNegotiatedFare, acceptPriceChanges, actionOnBackDatePrice and actionOnPQExpired), system will now take into account already issued Future Ticketing lines commit them to the reservation.
Service Action Code: AirTicketRQ
- Extended sleep/delay logic for future ticketing lines. When API receives the "F LINE PROCESSING STARTED" warning message from AirTicketLLSRS, it will will wait 2000 ms for each future ticketing line that is sent in the AirTicketRQ in order to successfully complete the ticketing transaction.
- Added a delay before 2nd call to TKT_DocumentServicesRQ - This is done to mitigate cases where multiple tickets were issued but only some of them are visible in the ticketing database, the extra delay of 500 ms aims to mitigate the problem.
- Added /AirTicketRQ/PostProcessing/@actionOnBackDatePrice - The API was enhanced to handle `UNABLE TO TICKET STORED FARE - PQ CONTAINS BACK DATE PRICE` ticketing mask. By default, the API will attempt to "R" - Reprice the stored fare, however the user can specify to "O" - Override or "Q" - Quit as well.
- Extended Future Ticketing Lines logic with Ticketing Mask detection in Text fields - As of now, when Future ticketing line processing starts, the API will react to known ticketing mask messages.
- (03/08/2022) Enabled user controlled delays between multiple ticketing transactions as a way to limit 'SIMULTANEOUS CHANGES' error occurrences. Added AirTicketRQ/PostProcessing/TicketingInterval@waitInterval to allow the user to tell the API to wait between subsequent <Ticketing> transactions.
- (03/08/2022) The API will now handle a very specific corner case related to multiple Future Line issuance. If you decide to quit upon encountering so-called 'ticketing masks' (acceptNegotiatedFare, acceptPriceChanges, actionOnBackDatePrice and actionOnPQExpired), system will now take into account already issued Future Ticketing lines commit them to the reservation.
Service Action Code: CreatePassengerNameRecordRQ
- Added capability to make passive PNR bookings. This is particularly useful when the user wishes to create Sabre PNR for bookings made outside of Sabre GDS.
- Modified .../AddRemark/RemarkInfo/Remark to unbounded. - From now on our users can send more than 98 remarks in a single CreatePNR request.
- Added support for combining .../TravelItineraryAddInfo/CustomerInfo/Corporate/ID with other ../TravelItineraryAddInfoelements/attributes. Previously such combination was not allowed.
- Introduced PostProcessing/ARUNK/@keepSegments which , when combined with ARUNK/@priorPricing="true" and segment selection pricing, will accurately apply flight segment numbering. (ASTSP-416)
- (10/28/2021) Added capability to pass or reference Strong Customer Authentication (SCA) data during a hotel booking payment card transaction. A new element 'PaymentInformation/FormOfPayment/PaymentCard/StrongCustomerAuthentication' has been added to the request schema for that purpose.
- (12/09/2021) Added capability to pass Visa special service document expiration date at .../SpecialReqDetails/SpecialServiceRQ/SpecialServiceInfo/AdvancePassenger/Document/Visa/@ExpirationDate
Method/Endpoint: /v2.4.0/passenger/records
- Added capability to make passive PNR bookings. This is particularly useful when the user wishes to create Sabre PNR for bookings made outside of Sabre GDS.
- Modified .AddRemark.RemarkInfo.Remark to unbounded. - From now on our users can send more than 98 remarks in a single CreatePNR request.
- Introduced PostProcessing.ARUNK.keepSegments which , when combined with ARUNK.priorPricing="true" and segment selection pricing, will accurately apply flight segment numbering. (ASTSP-416)
- (10/28/2021) Added capability to pass or reference Strong Customer Authentication (SCA) data during a hotel booking payment card transaction. A new object 'PaymentInformation.FormOfPayment.PaymentCard.StrongCustomerAuthentication' has been added to the model for that purpose.
- (12/09/2021) Added capability to pass Visa special service document expiration date at .SpecialReqDetails.SpecialServiceRQ.SpecialServiceInfo.AdvancePassenger.Document.Visa.ExpirationDate