Release Notes



Looking for the latest features and enhancements to Sabre APIs? You're in the right place.



Flight Schedules 2.2.0 on April 26, 2018

Service Action Code: OTA_AirScheduleLLSRQ
  • Added a new attribute to the response message which is used to pass time zone difference between the origin location and the destination location
Read more

Access Queue 2.0.9 on April 26, 2018

Service Action Code: QueueAccessLLSRQ
  • Corrected an intermittent issue where specific PNRs were not being correctly parsed within the response payload.
Read more

Corporate Travel Services 1.18.04 on April 18, 2018

Method/Endpoint: *
  • The 18.04 update to the Corporate Travel Services introduces a change to the way error information is organized in API responses and adds two new services used to cancel bookings made with the `POST /bookings` API.
  • Shopping performance has been improved, an issue with travel policy information in the Cart has been resolved, and 24-hour shopping is now available with Amadeus. And as always, we’ve included numerous small improvements and eliminated several bugs.
  • Improved Error Handling. A revision to the error message section of our responses is being rolled out in this release, starting with the `POST /catalogs`, `GET /catalogs`, and `GET /travelers` services:
  • * Added a new `errors` section encapsulating all error information
  • * Introduced a new `category` element to better classify the error
  • * Removed the `details` container since items within this section were reorganized
  • * Revised the content in the `type` and `description` elements to provide clearer information
  • The other services also use this new error structure in their response for most errors related to a bad request (missing required field, min/max or format constraints, etc.). And the `PATCH /carts` response uses this error structure when validating seats added to a Cart. This format change will be added to other responses for all error situations in upcoming releases.
  • Other updates include new elements added to all API responses to identify the source of an error: `fieldName`, `fieldPath`, and `fieldValue`. And the Corporate Travel Services now provide better handling of errors and more informative error responses in some specific scenarios:
  • * Validation of the itinerary and seat when booking a Cart
  • * Changed the error when attempting to book without creating a Cart from `INVALID_DATA` to `ONLY_ONE_BOOKING_PER_SESSION_ALLOWED`
  • Note: The `fieldPath` and `fieldValue` elements have been added to all services; not only those associated with catalogs and travelers.
  • Cancel A Booking. A new `PATCH /bookings` service provides the ability to cancel a booking made through the Corporate Travel Services. This new service can be invoked with a `bookingId` and body of `"removeAll": "true"` to completely cancel all components in the booking – if the booking is cancellable.
  • A new `GET /bookingRules` service provides a way to obtain cancel-related details about the booking before it is cancelled. For example, can the booking be cancelled (`isCancellable`)? Can it be voided (`isVoidable`)? Is the booking refundable (`isRefundable`) and if so, how much will be returned (`refund`)? If there is a cancel penalty how much is it (`cancellationPenalty`)? The amount of information returned by the `GET /bookingRules` service varies depending on whether or not GetThere Ticket Manager is enabled for the site, or if the booking is for Southwest Airlines via Air Connect.
  • The `GET /bookingRules` service requires a `bookingRulesId` resource identifier, which has been newly added to the `GET /bookings` response. In addition, the `GET /bookings` service has been updated to return booking information from the GetThere database when that data is no longer available in the internal temporary cache. This removes the previous constraint that `GET /bookings` could only be utilized within one hour of making the initial booking, relying on data from that cache before it expired.
  • Example responses for `GET /bookingRules` (`id` in the response refers to `bookingRulesId` in the request):
  • Note: The `bookingId` value is returned by the `POST /bookings` service and should be saved by the client. This `bookingId` will be needed to cancel a booking (and in the future to modify a booking).
  • Warning! These new services should only be used with flight bookings created using the Corporate Travel Services `POST /bookings` service. The `GET /bookings` service has not yet been updated to provide itinerary information for non-flight items, and `GET /bookingRules` does not return information for every type of non-flight item. Those updates are coming in future releases.
  • Several enhancements to existing services are also included in this release:
  • * Shopping performance using `POST /catalogs` has been improved by optimizing the way data is written to the internal temporary cache.
  • * Shopping for 24-hours is now available with Amadeus when using the `POST /catalogs` request. To return flights across a 24-hour **period **the request should include `"hoursTolerance": 12`, `"departureTime": "12:00"`, and `"returnTime": "12:00"` (or `"Time": "12:00"` when shopping one-way).
  • * Elements that are `null` have been removed from API responses. For example, the previous `GET /travelers` response `"firstName": "Vernon", "middleName": null, "lastName": "Bear"` will now return as `"firstName": "Vernon", "lastName": "Bear"`.
  • * As mentioned under [Cancel a booking](#section-cancel-a-booking) above, the `GET /bookings` service now returns booking information from the GetThere database when that data is no longer available in the internal temporary cache. This removes the previous constraint where `GET /bookings` could only be used just after making a booking, before data expired from the cache.
  • * A new `customNotes` section in the `GET /carts` response provides informational links provided by Air Connect carriers. For example, Air Asia provides links for items such as FAQs, checked baggage information, terms and conditions, and requirements for contact information with home phone and Mobile Rules.
  • * Active Residual Travel Fund (RTF) vouchers on Southwest Airlines have been added to the `GET /travelers` response. When available, details such as `voucherCode`, `expirationDate`, and `initialValue`are included for each voucher in a `vouchers` section. A future update will allow these vouchers to be used as a payment option in the `POST /bookings` request. This will only be supported when Southwest Airlines is booked via Air Connect, not when booked through the GDS.
  • Other updates improve the use of specific Corporate Travel Services:
  • `GET /carts` Policy violations are now specified for all items in the Cart.
  • `GET /carts` Now only those payment options allowed by the Air Connect carriers in the itinerary are listed in `acceptableNewPaymentCards`.
  • `GET /carts` Fixed a issue with “reprice” where a price was not returned for some Air Connect carriers.
  • `GET /carts` Corrected a problem where a second request on some Air Connect carriers resulted in an error. Now requests can be submitted any number of times.
  • `GET /carts` The unused `onTimePercentage` element has been removed.
  • `POST /bookings` Frequent flyer numbers used with Air Connect airlines now get passed correctly into the booking.
  • `POST /bookings` Made sure a non-selectable seat cannot be booked.
  • `POST /bookings` Made sure a paid seat cannot be booked without a payment option.
Read more