Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: ManualPriceQuoteAddInfoLLSRQ
- Multiple bugfixes for the current version of the API
Service Action Code: MISCServicesRQ
- Added optional attribute to DocumentNumber complex type, to return issue date if issued document number
- Add orchestrationID attribute to header
- Added these data elements to pass additional data for internal use
Service Action Code: AirSeatLLSRQ
- Corrected an intermittent issue where details of the second booked seats were not correctly reflected in the XML response payload.
Service Action Code: AirTicketLLSRQ
- Added support for Form of payment reference for single and multiple forms of payment.
- Added capability to issue a paperless service fee request.
Service Action Code: OTA_AirFlifoLLSRQ
- Corrected an intermittent issue where incorrect date was passed within response payload at .../FlightInfo/ScheduledInfo/FlightLeg/DepartureDateTime
Method/Endpoint: *
- The 1.19.08 update to the Corporate Travel Services corrects some issues when using Bargain Finder Max (BFM) - an upgrade to the Sabre flight shopping service. It also eliminates some confusion around baggage information in the Catalog and Cart content; and it adds support for the Strong Customer Authentication (SCA) initiative in Europe.
- 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 expected to come into force starting 14 September 2019.
- The two new fields added to support SCA in the 1.19.07 release are now functional: the boolean indicator `mayRequirePaymentAuthentication` in the `GET /carts` response and the `paymentAuthenticationReturnUrl` element in the `POST /carts/{id}/bookings` request. (See the 1.19.07 Release Notes for more details.)
- After the traveler returns from authentication a `PATCH /bookings` request needs to be submitted with `finalizeBooking` = "true". This tells the system to resume polling to check for a response to the original booking request; testing to see if the booking is complete. The service will respond by returning `status` = "204".
- Also, the following error messages have been added to support SCA:
- > Traveler tries to resume a booking without completing payment authentication. The error is `type` = "PAYMENT_AUTHENTICATION_FAILED" under `category` "INVALID_DATA" with the `description` "Payment hasn't been successfully authenticated."
- > If `paymentAuthenticationUrl` is not included in the `POST /carts/{id}/bookings` request when required (i.e., when `mayRequirePaymentAuthentication` is `true` in the `GET /carts` response). This error is `type` = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under `category` "MISSING_DATA" with a `description` of "In order to make a booking, payment authentication return url is required."