Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: EnhancedEndTransactionRQ
- Simplifies the End Transaction booking step described under the Format Finder Help System reference: pnrfo005.
- If finalizing or completing the PNR is the only action you want, please include only the EndTransaction node in the request.
- If receiving the PNR is the only action you want, please send the Source/@ReceivedFrom attribute in the request and set EndTransaction/@Ind="false".
Service Action Code: FaresContractLoadRQ
- New fare base attributes can be defined and processed when using creating FaresContractLoadRQ for a Category 25 rule
- New Passenger Application selection will be added to Category 12 Surcharges
- Removed Obsolete Routing Restriction Options not supported by ATPCO
Method/Endpoint: *
- The 1.19.07 update to the Corporate Travel Services address a couple of issues, updates error handling, and prepares the APIs for upcoming changes related to Strong Customer Authentication (SCA).
- Improved Error Handling. Better categorization and additional information has been added for the following error situations:
- > Traveler age is too young on Agentware. The new error is `type` = "TRAVELER_TOO_YOUNG" under `category` "INVALID_DATA" with `description` of "Booking cannot be made. Traveler must be 12 years of age or older.".
- > Connection time between flights is too short. This is error `type` = "INSUFFICIENT_CONNECTING_TIME" under `category` "INVALID_DATA" with `description` of "Insufficient connecting time between journeys".
- Strong Customer Authentication (SCA). SCA is a requirement of the EU Revised Directive on Payment Services (PSD2) affecting payment service providers within the European Economic Area. The SCA requirement is planned to come into force starting 14 September 2019. In preparation for SCA new fields have been added to the CTS APIs. These new items are present in the 1.19.07 release, but are not active (functional) and will not be required until 1.19.08:
- > A boolean indicator `mayRequirePaymentAuthentication` has been added to the `GET /carts` response. When this is true it means the Cart includes a Travelfusion itinerary and SCA may be in effect.
- > The element `paymentAuthenticationReturnUrl` has been added to the `POST /carts/{id}/bookings` request. This is the URL to which the traveler will be redirected after they have completed the authentication process. This new element is at the same level as `components` and `travelers` in the request. Starting in 1.19.08 a value needs to be provided for this element whenever `mayRequirePaymentAuthentication=true` in the Cart.
Service Action Code: TKT_ExchangeRQ
- The Schedule Change API has been enhanced with a new optional XML element to include an exchange waiver code. This element is only supported for subscribers reporting ticket sales to ARC.
Service Action Code: PaymentQueryRQ
- ValidatingCarrierCode : new attribute added to QueryRQ002
- OrderType : new attribute added to QueryRQ002
- QueryRQ006 : new service added
- QueryRS006 : new service added
- FopFeeAmount : new attribute added to QueryRS002
- FopFeeTaxCode : new attribute added to QueryRS002
- PromotionalInd : new attribute added to QueryRS002
- FopFeeAmount : new attribute added to FullfilmentItemType
Service Action Code: FraudCheckRQ
- Title : new optional attribute Title added to PersonNameGroup
- MiddleName : new optional attribute Title added to PersonNameGroup
- ContactInfoType : new complex element added with EmailAddress (String) and PhoneNumber (PhoneType) elements added
- LoyaltyMemberDetail : new element added to PassengerDetailType
- ContactInfo : new element added to PassengerDetailType
- NdcInd : new optional attribute added to POS_Type
- NameNumberInPNR : new attribute added to PassengerDetailType
- Address : new complex element of type AddressType added to LoyaltyMembershipDetailType
- ContactInfo : new complex element of type ContactInfoType added to LoyaltyMembershipDetailType
- PersonNameGroup : new attribute group added to LoyaltyMembershipDetailType
- MemberLoggedInInd : new attribute added to LoyaltyMembershipDetailType
- ID : new complex attribute added to LoyaltyMembershipDetailType
- Status : new attribute added to LoyaltyMembershipDetailType
- Level : new attribute added to LoyaltyMembershipDetailType
- IssueDate : new attribute added to LoyaltyMembershipDetailType
- LoyaltyOalCode : new attribute added LoyaltyMembershipDetailType
- CurrentBalance : new attribute added LoyaltyMembershipDetailType
- LoyaltyMemberDetail : new element of type LoyaltyMembershipDetailType added to PaymentCardType
- OrderOfferType : new attribute added to OrderDetail
- OrderCreateDate : new attribute added to OrderDetail
- LoyaltyMemberDetail : new element of type LoyaltyMembershipDetailType added to CustomerDetail
- PersonNameGroup : new attribute group added CustomerDetail
- Name : Attribute deleted from CustomerDetail
Service Action Code: PaymentRQ
- OrderCreateDate : new attribute added to OrderDetail
- LoyaltyMemberDetail : new element of type LoyaltyMembershipDetailType added to CustomerDetail
- ErrorCode : new attribute added in PaymentRS/Result
- PA_ResponseCode : new attribute added in T3DS_Result
- VE_ResponseCode : new attribute added in T3DS_Result
- LoyaltyMemberDetail : new element of type LoyaltyMembershipDetailType added to PassengerDetailType
- ContactInfo : new element added to PassengerDetailType
- LoyaltyMemberDetail : new element of type LoyaltyMembershipDetailType added to PaymentCardType
- FopFeeAmount : new attribute added to AmountDetail
- PromotionalInd : new attribute added to InstallmentDetail
- Title : new attribute added to PersonNameGroup
- MiddleName : new attribute added to PersonNameGroup
- new complex type LoyaltyMembershipDetailType added
Service Action Code: AirSchedulesAndAvailabilityRQ
- The request now contains a new element providing calendar search for the same market for 1 to 40 consecutive days.
- The request now contains additional element providing the option to search for specific flights (pairs of carrier code and flight number).
- The response now includes the base date of each response block.
- The interpretation of format date has changed from only the same day (as per current UTC time at time of receiving the request) to allowing up to three last days to be interpreted as current year.