Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Service Action Code: BargainFinderMaxRQ
- Bargain Finder Max has been enhanced with the following new optional search parameters:
- Shop by Fare Basis Code – project introduces enhancements to our Bargain Finder Max and Revalidate Itinerary API to support the capability for shopping to exclude a fare option based on Fare Basis Code.
- Shop by – Class of Service – project introduces enhancements to our Bargain Finder Max and Revalidate Itinerary API to support the capability for shopping to exclude a fare option based on Class of Service (RBD).
- Shop with parity mode – the project introduces enhancements to our Multiple Branded Fare shopping capabilities that allows to control the parity mode also for the lowest fare returned.
- Enhanced Multi-Ticket – the new parameter allows to specify the requested number of One-Way solutions in Multi-Ticket processing.
- Ancillary, Fare type descriptors - new Fare type descriptors in Bargain Finder Max. Exposure of new elements in the response to describe the fare type, the fare rule and fare tariff. The most relevant is return Fare type code descriptor in the response that indicates Basic Economy fares from the response.
Service Action Code: RevalidateItinRQ
- Revalidate Itinerary has been enhanced with the following new optional search parameters:
- Shop by Fare Basis Code – project introduces enhancements to our Bargain Finder Max and Revalidate Itinerary API to support the capability for shopping to exclude a fare option based on Fare Basis Code.
- Shop by – Class of Service – project introduces enhancements to our Bargain Finder Max and Revalidate Itinerary API to support the capability for shopping to exclude a fare option based on Class of Service (RBD).
- Shop with parity mode – the project introduces enhancements to our Multiple Branded Fare shopping capabilities that allows to control the parity mode also for the lowest fare returned.
- Enhanced Multi-Ticket – the new parameter allows to specify the requested number of One-Way solutions in Multi-Ticket processing.
- Ancillary elements GAO - new Fare type descriptors in Bargain Finder Max. Exposure of new elements in the response to describe the fare type, the fare rule and fare tariff. The most relevant is return Fare type code descriptor in the response that indicates Basic Economy fares from the response.
Method/Endpoint: /v1/offers/shop
- Bargain Finder Max has been enhanced with the following new optional search parameters:
- Shop by Fare Basis Code – project introduces enhancements to our Bargain Finder Max API to support the capability for shopping to exclude a fare option based on Fare Basis Code.
- Shop by – Class of Service – project introduces enhancements to our Bargain Finder Max API to support the capability for shopping to exclude a fare option based on Class of Service (RBD).
- Shop with parity mode – the project introduces enhancements to our Multiple Branded Fare shopping capabilities that allows to control the parity mode also for the lowest fare returned.
- Enhanced Multi-Ticket – the new parameter allows to specify the requested number of One-Way solutions in Multi-Ticket processing.
- Ancillary, Fare type descriptors - new Fare type descriptors in Bargain Finder Max. Exposure of new elements in the response to describe the fare type, the fare rule and fare tariff. The most relevant is return Fare type code descriptor in the response that indicates Basic Economy fares from the response.
Service Action Code: BargainFinderMax_ADRQ
- No changes for this functionality in this Release. Only schema version upgrade to 5.2.0.
Service Action Code: BargainFinderMax_ASRQ
- No changes for this functionality in this Release. Only schema version upgrade to 5.2.0.
Method/Endpoint: /v5.2.0/shop/altdates/flights?mode=live
- No changes for this functionality in this Release. Only schema and endpoint version upgrade to 5.2.0.
Method/Endpoint: /v5.2.0/shop/altairports/flights?mode=live
- No changes for this functionality in this Release. Only schema and endpoint version upgrade to 5.2.0.
Method/Endpoint: *
- The 19.06 update to the Corporate Travel Services improves the way Travel Policy is applied during 24-hour shopping, significantly improves the response time of `GET /travelers` requests, adds a small enhancement for branded fares, and updates error handling for a specific scenario.
- Improved Error Handling. Better categorization and additional information has been added for the following error situations: * Departure time is too close to current time (when using Search by Time). Following the 19.05 release this situation was returning `500 INTERNAL SERVER ERROR` . Now the error is as it was before 19.05, with `type` = "DEPARTURE_TIME_TOO_CLOSE" under `category` "POLICY_VIOLATION" with `description` of "Departure time is too close to the current time based on the policy setup for the site".
- Other updates have been made to improve various Corporate Travel Services: * In the Search by Time path `fareBrandId` has been added to the `GET /catalogs` response (on flights with brands).
- * 24-hour shopping no longer requires that the `time` in the `POST /catalogs` request be set to "12:00", as was previously required (depending on the GDS). Now a 24-hour search is performed simply by including `hoursTolerance` as "12" in the request. This allows the `time` from the `POST /catalogs` request to be used in Travel Policy to calculate *Lowest Logical Fare* and apply that to flights. Specifically, when Travel Policy includes an *Ideal Air Itinerary* rule, that `time` is used to determine the *Ideal Air Itinerary* and the corresponding *Lowest Logical Fare*. That *Lowest Logical Fare* is then used to evaluate the price of each flight in the `GET /catalogs` response and determine which flights are "out of policy".
- Note: For one-way shopping `time` is the element used in Travel Policy evaluation. When doing round-trip shopping the element name is `departTime`.
- * The performance of `GET /travelers` has been greatly improved. A request should now return in about 10%-30% of the time previously seen.
- The *first* `GET /travelers` request sent for a given main site (supersite) will still take extra time. But all subsequent requests - for any traveler on any subsite under that main site - will be returned much more quickly. The improved performance will continue until the cached information expires, 1 hour later. However, any `GET /travelers` request or `POST /catalogs` request send during that time will reset the cache timer, restarting the 1 hour countdown.
Service Action Code: DisplayPriceQuoteLLSRQ
- Added .../PriceQuoteBreakdown/PassengerFare/PassengerType to the response message.
- Added .../PriceQuoteSummary/Indicators/Ticketed/@Ind to the response message.
Service Action Code: OTA_AirBookLLSRQ
- Added .../OriginDestinationInformation/FlightSegment/@RedemptionSell to the request message in order to indicate that the transaction is a redemption booking.