Release Notes



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



TicketingDocumentServicesRQ 3.18.0 on February 26, 2018

Service Action Code: TicketingDocumentServicesRQ
  • Modified response schema to correct specific schema validation errors, and added new fields to facilitate Interline EMD revenue recognition between partner airlines
  • Modified OtherSystem element in Reservation.Details type from PNR_Locater to Identifier.Reservation.
  • Added optional Reservation element under TicketingDocument.Details.Update
  • Modified type of GetTicketingDocumentRS/Details/Agent/CompanyName to ProperName.150Character
  • Change TicketDesignator to complexType and add attribute ServiceCoupon/TicketDesignator/@appCommission
  • Renamed @appCommission to @appendCommission
Read more

Update Itinerary 1.18.0 on February 21, 2018

Service Action Code: UpdateReservationRQ
  • Support for new FOP type: AccountCode
  • Support for Corporate ID with New Payment Card (WS)
  • FCMI functionality - price validation on SellCancel
Read more

Corporate Travel Services 1.18.01 on February 21, 2018

Method/Endpoint: *
  • The 18.01 update to the Corporate Travel APIs expands the Cart and FareRules services to provide support for all Air Connect (Budget Airline) carriers. Viewing and purchasing Air Extras is also now supported – specifically bags and meals on Travelfusion airlines and seats on GDS airlines (in conjunction with a new SeatMap service). Plus, there is a new Site Announcement service to retrieve static page messages, we've made numerous small improvements in various areas, and several bugs have been eliminated.
  • The `details` section of error responses have been updated to return the attribute related to the error, rather than the full `.json` path. In addition, the information returned in the Corporate Travel APIs now provides more informative error responses in various scenarios:
  • * Duplicate booking requests
  • * Missing `travelerId` during flight shopping
  • * Missing traveler profile during booking
  • * Flight is no longer available during booking
  • * Missing travel policy information for purpose of travel in booking request
  • * Incorrect free text information in Air Connect booking request
  • * Missing TSA information in booking request
  • * Invalid temporary card data in booking request
  • * Invalid values in shopping request
  • * Empty list due to a HTTP 500 error
  • * Invalid IATA airport code for departing or arrival airport
  • * Booking request with missing or invalid answer for `supplementaryDataQuestion`
  • Air Connect Content. All Air Connect (Budget Airline) content is now accessible through the flight Shopping service in the `GET /catalogs` response.
  • The `GET /carts` response has been expanded to provide details about payment options and other information needed to book these airlines. This includes identification of the specific credit card types allowed for payment, support for temporary payment cards (cards that are not in the traveler’s profile and are not site cards), a `paymentCardSecurityCodeRequired` boolean to identify when a CVV (Card Verification Value) is required with the credit card information, and `usageFee` data when there is an additional fee related to the type of credit card used.
  • The `GET /fareRules` response has been extended to provide brand attributes and fare rules for Air Connect flights.
  • Warning! The Cart booking service must be used to book Air Connect carriers. These flights cannot be booked directly using the `POST /bookings` request (except for Southwest Airlines – though even here use of the Cart booking service is highly recommended).
  • Shop and Book Air Extras. The `GET /carts` response now identifies which Air Extras (bags and meals) are available on Air Connect flights. Desired Air Extras can be added using `PATCH /carts` and purchased with the `POST /bookings` request.
  • Bags and meals use the same form of payment as the Air Connect flight.
  • Free seats and premium seats on GDS airlines can be shopped using the new SeatMap service, and booked using the `PATCH /carts` and `POST /bookings` requests (more information about the [SeatMap service](#section-seatmap-service) is provided below).
  • Information regarding any reserved Air Extras is included in the `GET /bookings` response.
  • SeatMap Service. The new SeatMap service provides information about all the seats in a cabin for most flights (except Air Connect flights). A `GET /seatMaps` request is sent using the `seatMapId` from a flight shopping `GET /catalogs` response. Seats with fees are identified for supported airlines. Selected seats can be added with a `PATCH /carts` request for subsequent inclusion in a `POST /bookings` request.
  • For sites with the Air Extra feature enabled (only available when Sabre is the GDS), information about premium seats on supported airlines is included in the `GET /seatMaps` response, using the traveler’s frequent flyer information from their traveler profile to determine eligibility and price. These premium seats can be reserved by including an allowable form of Air Extra payment in the `POST /bookings` request. Air Extra payment details are provided in the `GET /carts` response.
  • Temporary Payment Cards. Temporary payment cards are credit cards which are not predefined, as is the case with site cards or credit cards already in the traveler’s profile. These temporary payment cards need to be provided by the traveler during checkout and included in the `POST /bookings` request.
  • Temporary payment cards can be used for payment of flights and Air Extras (bags, meals, and seats) when enabled through Site Administration. When a temporary payment card is allowed, the `acceptableNewPaymentCards` array will be populated in the `GET /catalogs` response.
  • Note: Temporary payment card information is not saved to the traveler’s profile, so it must be entered for each booking.
  • Site Announcement. A new Site Announcement service retrieves static messages for a site using a `GET /sites/announcements` request and response. These messages - often referred to as "Company Announcements" - represent the header and footer messages shown on various pages during flight shopping and booking in the GetThere UI application:
  • * Low Fare Options (used for the Search by Price flight availability page)
  • * Seat Selection
  • * Checkout
  • * Reservation Complete
  • In addition, the carousel messages and footer message for the Traveler View of the Home page are included, as well as the Please Wait Message for Search by Price. All of the configured messages for each page and for each language are returned, using a label to identify the page and message location, along with a `languageCode` to denote the language for which the message is configured. The `id` used to access these announcement messages is a combination of `site` and `subsite` names. To assist with creation of this `id`, a new `siteId` element has been added to the `GET /travelers` response. This element provides the `site` and `subsite` names in a format which can be directly used in a `GET /sites/announcements` request.
  • Note: These messages replace the obsolete mobile messages in the announcements section of the `GET /travelers` response. Because of this the old announcements section has been removed from `GET /travelers`.
  • General Improvements. Other updates improve overall use of the Corporate Travel APIs:
  • * The `GET /fareRules` service now returns fare rules in more situations, such as when fare rules are not available for the full round-trip itinerary and must be retrieved by segment.
  • * Duplicate items in the `Cart` are rejected during `GET /carts`.
  • * The contents of `answer` and `answerId` have been swapped in `supplementaryDataQuestions` (with predefined answers) in the `GET /carts` response. For backwards compatibility, these fields have not been changed in the `GET /travelers` response, where they remain un-swapped.
  • * Quoted and localized fee values have been added to the `GET /carts` response.
  • * An answer to a `supplementaryDataQuestion` with `openResponse` in a `POST /bookings` request is now validated against the minimum and maximum value when the type is numeric or date.
  • * Fixed an issue when repricing Air Connect flights in the `GET /carts` process.
  • * The `POST /bookings` request now supports `paymentOptionId` from `GET /carts`.
  • * Corrected the format of `fareRulesId` in the `GET /carts` response.
  • * Taxes are calculated for Agentware flights in the `GET /catalogs` response based on the difference between total and base fare values.
  • * Fixed `localizedPrice` in the `GET /bookings` response.
  • * TSA-related boolean elements are now set correctly in the `GET /carts` response (`isGenderRequired`, `isDateOfBirthRequired`, and `isTSARedressNumberUsable`).
Read more

Corporate Travel Services 1.17.12.02 on February 8, 2018

Method/Endpoint: *
  • The 17.12.02 update provides a fix for a cache issue with large shopping “payloads” and restores the increase in shopping options. This means more flight options are now available from the Travelport GDS’s – as well as from Sabre Intellisell and Agentware (for Southwest Airlines).
  • The 17.12 release included an improvement to return many more options during shopping, from all sources. Unfortunately, this update had unintended consequences with an intermediary cache mechanism used to hold flight options, due to the larger “payload” size that comes with a larger shopping response. As a result, that portion of the update was disabled shortly after the 17.12 release, reducing the shopping options back to previous levels for requests to any of the Travelport GDS’s. This 17.12.02 update adds compression so the cache can support large shopping “payloads”, and also re-enables the increase in shopping options.
  • There are no API changes with this release.
Read more