Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: FareLLSRQ
- Added a dedicated response element to pass the full cabin name on top of already existing cabin code
Service Action Code: OTA_AirFlifoLLSRQ
- Corrected an intermittent issue where incorrect information was passed at .../FlightInfo/ActualInfo/FlightLeg/ArrivalDateTime
Service Action Code: OTA_VehLocDetailLLSRQ
- Added .../VehAvailRQCore/VendorPrefs/CarExtras/@Code to the request message to be able to specify a car extras code to validate with vendor.
- Added.../VehAvailRSCore/VehVendorAvails/VehVendorAvail/LocationDetails/OperationSchedule/AdditionalOperationTimes to the response message to pass additional custom information from vendor.
Service Action Code: OTA_VehResLLSRQ
- Added ability to pass customer e-mail address or supplier fax number in the request message.
- Corrected method of generating vehicle delivery address. The method used in previous versions resulted in errors.
Service Action Code: VehResModifyLLSRQ
- Added ability to pass customer e-mail address or supplier fax number in the request message.
- Added ability to delete corporate Ids, ID numbers, Promotion Codes, Tour Codes and Special Equipment Preferences.
Service Action Code: VehRateRulesLLSRQ
- Added a new attribute to pass the special equipment name provided by the supplier.
Method/Endpoint: POST /v2.0.0/GetHotelRateInfoRQ
- Will return rate details from multiple sources, including GDS, EAN, HotelBeds, GTA and Booking.com
- Search criteria includes check in/check out dates; number of guests; hotel property ID; rate range; pre-paid and/or post-paid rates; specific rate codes.
Method/Endpoint: POST /v2.0.0/GetHotelLeadRateRQ
- This will allow customers to shop for the lowest available rate from GDS and multiple aggregator sources, including EAN, Hotel Beds, Booking.com and GTA.
- Included in the product response are elements specific to the individual products including: Product Name; Product Description; Room Type Code; Nightly Rate Breakdown; Applicable taxes and fees; Cancellation penalties associated to the product
Method/Endpoint: *
- ## The 19.01 update to the Corporate Travel Services is focused on improved error handling, squashing bugs, and delivering a few enhancements.
- Note: This release is officially known as 19.01-01 since it is a patch release to 19.01. The 19.01 update was briefly put into production on 30 January 2019, but was quickly removed after an issue was found with a new system used to authorize API access. The 19.01-01 release on 7 February provides the exact same client-facing updates that were noted for 19.01, but does not use the new authorization system (instead it uses the same authorization in previously releases).
- Improved error handling. Better categorization and additional information has been added for the following situations: * `E_NEED_TICKETING` (`error_code: 175`). Now returns error `type` = "INVALID_TICKETING_DATA" under `category` "BAD_CONFIGURATION" with `description` = "Invalid or missing ticketing time limit.".
- * `E_NEED ADDRESS` (`error_code: 108`). Now returns **error **`type` = "INVALID_PROFILE_ON_SUPPLIER_SIDE" under `category` "BAD_CONFIGURATION".
- * `E_BILLING_NAME_ERROR` (`error_code: 69`). Now returns an error under `category` "BAD_CONFIGURATION" with `description` = "Unable to complete booking.".
- * `PAYMENT_CARD_NOT_FOUND` (`error_code: 23`). Three specific types of payment errors have been broken down to provide more information. These cases now return a different error `type` and `description` under `category` "INVALID_DATA", depending on the issue:
- * `type` = "PAYMENT_CARD_EXPIRED" with `description` = "Booking cannot be made. Payment card has expired."
- * `type` = "INVALID_PAYMENT_CARD_NUMBER" with `description` = "Booking cannot be made. Invalid card number."
- * `type` = "INVALID_PAYMENT_CARD_SECURITY_CODE" with `description` = "Booking cannot be made. Invalid security code."
- ## * `[[CREDIT_CARD_EXPIRED](from Air **Connect **(*TravelFusion*). Previously this returned `INTERNAL_SERVER_ERROR` (500) but now returns error `type` = "PAYMENT_CARD_EXPIRED" under `category` "INVALID_DATA" with `description` "Booking cannot be made. Payment card has expired.".
- * Missing or duplicate shopping parameters. If neither `shopByPrice` or `shopByTime` are included in the `POST /catalogs` request (or if they are both included) a new error is returned with `type` = "EXACTLY_ONE_FIELD_REQUIRED" under the `category` "BAD_REQUEST" with `description` = "Exactly one of shopByPrice or shopByTime fields must be provided".
- Enhancements and General Improvements. Other updates have been made to improve various Corporate Travel Services: * Retired the ability to book without a Cart. This means `POST /bookings` can no longer be used. All bookings must be made using `POST /carts/{id}/bookings`.
- * Preferred airlines sometimes showed `corporatePreference` = "true" in the Catalog, but the same setting was "false" in the Cart. This has been fixed so preferred airlines are always identified as `corporatePreference` = "true" in both the Catalog and the Cart.
- * The traveler's `assignedSiteId` has been added to the `GET /travelers` response. This identifies the site and subsite to which the traveler's login is assigned within the system. The `siteId` element is still present and denotes the "working" site and subsite for the traveler to be used during their session. This will be different from `assignedSiteId` if API Subsite Redirection is enabled.
- * Fixed the issue noted in the [18.11 Release Notes](http://corporatetravel.developer.sabre.com/blog/1811-release-notes#section-booking-details) where the `localizedPrice` in `GET /bookings` used the same currency and value as `quotedPrice`. The proper currencies are now listed, with the converted amounts for that currency. This same update was also made to the `GET /catalogs` and `GET /carts` responses when using the Search by Time path.
- * Added a `specialRequests` array to the `GET /bookings` response within `carItineraries` identifying any special equipment requests associated with the vehicle included in the booking.
- * The list of `suppliers` from `GET /sites` included data from the SuperPNR setting for secondary suppliers even when SuperPNR was disabled in Site Administration. Now that information is only included in `GET /sites` when SuperPNR is enabled.
- * Summary details have been added to the `GET /travelers/bookings` and `GET /bookings` responses. Specifically the trip `startDate`, `endDate`, and `destinationName` (city).
- * Corrected a problem where `GET /carts` returned a 422 error when going down the Search by Time path and an `itemType` = "FLIGHT_SEAT" was in the Cart. Now the Cart is priced correctly when a seat is included.
- * Added support for hidden and read-only custom fields (CFEs) - referred to as `supplementaryDataQuestions` in the webservices. Now hidden (`toBeConcealed`) and read-only (`readOnly`) fields are included in `GET /carts` and are validated in `POST /carts/bookings`. More information is available in the updated documentation on `supplementaryDataGroups` and `supplementaryDataQuestions`. ***<<-- Need to add link to location when documentation is updated.***
- * Converted `numberOfConnectionsAllowed` from a value to an enum in the `GET /sites` response in order to accommodate a couple of special options that use non-standard values. This setting identifies the type of connecting flight options to be included in the air shopping response. When a site was configured in Site Administration with one of the special options it caused `GET /sites` to return an error. That no longer happens. The enums for this element can be:
- ALL_RESULTS: all available journeys. NON_STOP_AND_DIRECT_FLIGHTS_ONLY: journeys without any connections. MAXIMUM_ONE: journeys with a maximum of one connection. MAXIMUM_TWO: journeys with a maximum of two connections. MAXIMUM_THREE: Journeys with a maximum of three connections