Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: PO_AllBrandsPricingRQ
- Price with Multiple Brands has been enhanced with the following new parameters:
- Exclude Non-Branded Fares - Allows for only branded fares to be returned when requesting single or multiple brands.
- Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes.
- Fare Type Bitmap - A fare pricing component related to ancillaries offer.
Method/Endpoint: /v1/offers/shop
- Bargain Finder Max has been enhanced with following new features:
- REST JSON API response format - Grouped Itinerary Response (GIR). Note: OTA JSON Response type is no longer available with the new version
- Streamed response format - Split the response into multiple packages by setting a limited number of itineraries in each one of them
- Branded Fare Attributes - Parameter to request brand attributes, allows Sabre agencies to return additional brand attributes.
- Exclude Non-Branded Fares - Allows for only branded fares to be returned when requesting single or multiple brands
- Alternate Airport Cross Border Indicator - Added flexibility to determine whether alternate airports can be in other country than main pair when mileage is used
- New Distribution Capability (NDC) - New parameters introduced to the Shopping request and response to support the new functionality
- Credit Card Fee - The credit card amount returned with Low-Cost-Carriers options added at passenger level
- Booking Fee - The booking fee amount returned with Low-Cost-Carriers options added at passenger level
- Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
- Fare Type Bitmap - A fare pricing component related to ancillaries offer
Service Action Code: BargainFinderMaxRQ
- Bargain Finder Max has been enhanced with the following new optional search parameters:
- Branded Fare Attributes - Parameter to request brand attributes, allows Sabre agencies to return additional brand attributes in the response it returns the structured data filed in table 166. Brand attributes is a feature within the Branded fares capabilities and will be returned with single and multiple branded fares request
- Exclude Non-Branded Fares - Allows for only branded fares to be returned when requesting single or multiple brands
- Alternate Airport Cross Border Indicator - Added flexibility to determine whether alternate airports can be in other country than main pair when mileage is used
- Credit Card Fee - The credit card amount returned with Low-Cost-Carriers options added at passenger level
- Booking Fee - The booking fee amount returned with Low-Cost-Carriers options added at passenger level
- Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
- Fare Type Bitmap - A fare pricing component related to ancillaries offer
Service Action Code: RevalidateItinRQ
- Revalidate Itinerary has been enhanced with the following new optional search parameters:
- Branded Fare Attributes - Parameter to request brand attributes, allows Sabre agencies to return additional brand attributes in the response it returns the structured data filed in table 166. Brand attributes is a feature within the Branded fares capabilities and will be returned with single and multiple branded fares request
- Exclude Non-Branded Fares - Allows for only branded fares to be returned when requesting single or multiple brands
- Alternate Airport Cross Border Indicator - Added flexibility to determine whether alternate airports can be in other country than main pair when mileage is used
- Credit Card Fee - The credit card amount returned with Low-Cost-Carriers options added at passenger level
- Booking Fee - The booking fee amount returned with Low-Cost-Carriers options added at passenger level
- Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
- Fare Type Bitmap - A fare pricing component related to ancillaries offer
Service Action Code: PO_PNRPricingRQ
- Price with Itinerary has been enhanced with the following new optional search parameter:
- Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
- Fare Type Bitmap - A fare pricing component related to ancillaries offer
Method/Endpoint: /v5.1.0/shop/altairports/flights?mode=live
- The classic Alternate Airport Shop Request is available now in JSON over the REST path/endpoint.
- AirStreaming - Split the final Intellisell response into multiple packages by setting a limited number of itineraries in each one of them.
Method/Endpoint: /v5.1.0/shop/altdates/flights?mode=live
- The classic Alternate Date API is available now in JSON over the REST path/endpoint.
- AirStreaming - Split the final Intellisell response into multiple packages by setting a limited number of itineraries in each one of them.
Service Action Code: EnhancedSeatMapRQ
- Enhanced Seat Map version 6 supports ATPCO Table 191 requirements. ATPCO Table 191 introduced new standard for airlines that would like to differentiate their commercial names for seats on the seat map. For seats there was one commercial name STANDARD SEAT ASSIGNEMENT. Other then commercial name also seat characteristics were displayed on the seat map. Airlines that will start using ATPCO Table 191 will have ability to define different commercial names depending on seat characteristics.
Method/Endpoint: *
- The 19.02 update to the Corporate Travel Services is focused on improved error handling, squashing bugs, and delivering enhancements.
- This release is officially known as 19.02-01 since it is a patch release to 19.02. The 19.02 update on 5 March introduced a problem related to the setting which allows the traveler's name to be changed at the time of booking. A workaround involving system settings minimized the impact of the issue until it was corrected with an update on 13 March. The changes in the 19.02-01 update were internal and as such did not change or affect any of the client-facing updates listed below for 19.02.
- Improved error handling. Better categorization and additional information has been added for the following situations involving a `POST / bookings` request sent to Agentware (one of the Air Connect aggregators/suppliers). In each of these cases the API previously returned `INTERNAL_SERVER_ERROR` (500):
- * Invalid phone number (for example, when the number includes an alpha character). Now returns error `type` = "INVALID_PHONE_NUMBER" under `category` "INVALID_DATA" with `description` "Booking cannot be made. Phone number is invalid.".
- * Invalid email address. Now returns error `type` = "INVALID_EMAIL" under `category` "INVALID_DATA" with `description` "Booking cannot be made. Invalid email.".
- * Expired payment card. Now returns error `type` = "PAYMENT_CARD_EXPIRED" under `category` "INVALID_DATA" with `description` "Booking cannot be made. **Payment **card has expired.".
- * Declined payment card or general error processing the payment card. Both scenarios now return error `type` = "PAYMENT_DECLINED" under `category` "INVALID_DATA" with `description` "Booking cannot be made. Payment card declined.".
- Enhancements and General Improvements. Other updates have been made to improve various Corporate Travel Services: * Corrected a problem where the PNR Editor Tag `itin.has_air_tempcard` was not set correctly. This Tag now has the correct state and can be used in PNR Editor Strings as part of an expression to create a PNR remark.
- * Added the ability to send replacement (override) traveler contact information (`contactInfo`) with `emailAddress` and/or `telephoneNumber` in a `POST /bookings` request.
- * Removed `fareRulesId` from the `GET /catalogs` response for Air Connect flights. This is a continuation of the plan described in the [18.09 Release Notes](http://corporatetravel.developer.sabre.com/blog/1809-release-notes#section-farebrands-service) to migrate to the `GET /fareBrands` service for brand attribute data, and remove brand information from the `GET /fareRules` response.
- * A payment card `billingAddress` object has been added for each card under `acceptableKnownPaymentOptions` in `GET /carts`. This information is aligned with the `isBillingAddressInProfile` indicator also present for each payment card. Note that every payment billing address has four required elements: `addressLine1`, `city`, `postalCode`, and `countryCode`:
- * If any of the required elements for the payment billing address are empty then the `billingAddress` object will be `null` and `isBillingAddressInProfile` will be `false`.
- * All of the required elements must have a value for the `billingAddress` object to be populated and for `isBillingAddressInProfile` to be `true`.
- * When `isBillingAddressInProfile` is `true` then the optional elements `addressLine2` and `stateProvinceCode` will also be included, whenever either element is not empty.
- * Fixed the issue noted in the [18.11-01 Release Notes](http://corporatetravel.developer.sabre.com/blog/1811-01-release-notes#section-personal-address) where `stateProvinceCode` was a required element for Air Connect bookings, whenever address was included in a `POST /bookings` request. The `stateProvinceCode` is no longer required in `POST /bookings` for countries without such information.
- * Improved the handling of situations where a booking completed successfully but some informational components were not returned from the supplier (e.g. vendor confirmation). This sometimes caused a response of `INTERNAL_SERVER_ERROR` (500) from `POST /bookings`, leaving the traveler unclear if the booking was or was not complete. These situations will now be handled properly, without an error.
- * Updated the `GET bookings` response to return `travelerId` in the correct format (the same as in the `POST /bookings` request). Also replaced some elements under `travelers` and `personalIdentifiableInformation` with names that better describe their contents - matching the booking information as stored in the GDS. Specifically, `firstName` and `middleName` have been replaced by `givenName` with both pieces of data, and `lastName` is now surname.
- * The `supplementaryDataQuestions` array has been removed from the `GET /travelers` response. This information is now only available from the `GET /carts` response. This update implements the vision for `GET /carts` functionality described back in late 2017 in the notes for [Upcoming: Air Connect and Cart Service](http://corporatetravel.developer.sabre.com/blog/upcoming-air-connect-and-cart-service#section-get-cart-functionality).
- * Updated several services so `travelerId` can include a period (.) character, such as when the `travelerId` in an email address.
- * As foretold in the [18.11 Release Notes](http://corporatetravel.developer.sabre.com/blog/1811-release-notes#section-custom-fields-supplementarydatagroups), the contents of `answerId` and `answer` have been swapped. Now `answer` is the "label" shown to the traveler and `answerId` is the "code" or value for the selection.
- Warning! Clients should stop using `newAnswer` and `newAnswerId`, and return to using `answer` and `answerId`. The `newAnswer` and `newAnswerId` elements will be removed from `GET /carts` in a future update.
- * Information about class of service has been added into the `GET /sites` response. This data identifies which classes are configured for use on the site-subsite - such as Coach, Premium Economy, Business, or First. The response includes an array of `shoppableClassesOfService` within `airConfiguration`. Each grouping under `shoppableClassesOfService` describes a `classOfService`, the `label` configured for that `classOfService`, and an `isDefault` boolean indicator to identify which `classOfService` is setup as the default.
- Note: This new `shoppableClassesOfService` array in `GET /sites` works in conjunction with the `shoppableFareTypes` array introduced in release 18.11.
- Special considerations with Amadeus. Sites using the Amadeus GDS have an alternate configuration in Site Administration, such that supported classes of service are setup together with fare types, rather than independently. In addition only the LOWEST_AVAILABLE and UNRESTRICTED fare types are supported, and only for some classes of service. Because of these unique aspects the following needs to be considered when using an Amadeus site:
- `>` Only LOWEST_AVAILABLE and/or UNRESTRICTED will be returned under `shoppableFareTypes` in `GET /sites`.
- `>` The `label` element is not present in the `GET /sites` response for either `shoppableClassesOfService` or `shoppableFareTypes`.
- `>` If LOWEST_AVAILABLE and UNRESTRICTED are listed as `shoppableFareTypes` in `GET /sites` they can be used as `fareType` when flight shopping with `POST /catalogs` - but only with the COACH, PREMIUM_ECONOMY, or BUSINESS `classOfService`. However, it is possible to configure a given `fareType` so it is allowed for one `classOfService` but not for another `classOfService`. For example, UNRESTRICTED can be configured for use when shopping COACH, but not allowed when shopping BUSINESS. Currently these types of special configurations that link just *some* `shoppableFareTypes` to *some* `shoppableClassesOfService` are not described in the `GET /sites` response.
- `>` When shopping for the FIRST `classOfService` with `POST /catalogs` there is no assigned `fareType`. So the `fareType` element must equal `null` or be removed entirely from the `POST /catalogs` request. (*Be sure to see an update to this behavior described in the* [19.03 Release Notes](http://corporatetravel.developer.sabre.com/v1.0/blog/1903-release-notes#section-enhancements-and-general-improvements).)