Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Method/Endpoint: / Digital Connect - Self Service
- Features
- Performance improvements and workflow changes in MTO and Edit passenger Exchange
- 3DS 2.0 - defined iframe size
- Supplier Transaction ID in VCR and EMD
- Multiple exchanges
- EMD as Form of Payment
- Defect fixes
- Incorrect installment interest format
- Query Ancillaries connectivity issue - passenger type
- Query Ancillaries connectivity issue - currency data
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.
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.
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.