Release Notes
Looking for the latest features and enhancements to Sabre APIs? You're in the right place.
Method/Endpoint: GET v1/cur/currency/all
- MDM Currency All provides the full list of all current and active currency codes managed and recognized by ISO.
- The currency will have information on the code, name, HTML codes, numeric code, symbol and decimal placement.
Method/Endpoint: GET v1/cur/countrycurrency/all
- MDM Country Currency All provides the full list of all current and active country to currency mapping managed and recognized by ISO.
- The country to currency mapping will have information on the code, name and default currency indicator.
Method/Endpoint: GET v1/eqp/equipmentcode/all
- MDM Equipment Code All provides the full list of all current and active equipment codes managed and recognized by Cirium/Innovata.
- The equipment code service will have information on the equipment group code, equipment group name, equipment type code, equipment type name, number of engines, equipment category, body width and commuter indicator.
Method/Endpoint: GET v1/ms/airmealservice/all
- MDM Meal Service All provides the full list of all current and active meal service codes managed and recognized by IATA and Sabre.
- The air meal service will have information on the air meal service code and the meal service name.
Method/Endpoint: GET v1/sp/serviceprovider/all
- MDM Service Provider is a reference domain that provides service provider-specific information such as airline codes, GDS codes and railway codes.
- Air and Rail Service Provider data are sourced primarily from Innovata/Cirium, and augmented with data from IATA, whereas the GDS Service Provider data is sourced primarily from IATA.
- The MDM Service Provider API belongs to the Master Data Management (MDM) suite of APIs.
Method/Endpoint: *
- The 1.19.09 update to the Corporate Travel Services adds hotel payment information to the GET /travelers response, addresses an issue with the new Booking Connectivity Service (BCS), and includes additional error handling when using Strong Customer Authentication (SCA).
- The GET /travelers response now identifies the preferred payment card for hotels (under preferences), and includes hotel card summary information (under paymentCards). This information can be used to distinguish between user-assigned profile card preferences vs. default preference assignments, in situations where the profile synchronization process creates default assignments.
- New error messages have been added for the following error situations associated with Strong Customer Authentication (SCA):
- The paymentAuthenticationReturnUrl is missing in the POST /carts/{id}/booking request, when this element is required by the mayRequirePaymentAuthentication indicator in the GET /carts response. The new error is type = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under category "MISSING_DATA" with a description of "Booking cannot be made. In order to make a booking, payment authentication return url is required.".
- When payment authentication fails because an error is returned by TravelFusion, or when an attempt is made to resume a booking with PATCH /bookings for a booking that was not pending authentication or has failed authentication. These situations return error type = "PAYMENT_AUTHENTICATION_FAILED" under category "INVALID_DATA" with a description of "Booking cannot be made. Payment hasn't been successfully authenticated.".
- Note: More information about Strong Customer Authentication (SCA) can be found in the Release Notes for 1.19.07 and 1.19.08.
- An issue with the new Booking Connectivity Service (BCS) has been corrected. This problem was around handling the ticketing time limit for bookings made from the Corporate Travel Services (CTS), specifically with the POST /carts/{id}/bookings endpoint. Now bookings made with BCS are handled properly, clearing the way for clients to switch ticketing to BCS.
Service Action Code: GetHotelAvailRQ
- The response now shows both the Sabre Hotel Code and the Global ID
- Product codes now returned in the response for GDS products in 'ProductCode'
- Breakdown of tax and fee information by date range is now returned in 'Taxes' and 'Fees' elements
- Updated structure of element 'Guarantee'
- Added ability to view Security Features mapped to a property
- Amenities can now have a text description associated to them
- Added 'RateDetailsInd' attribute to request to control whether only hotels with rates are shown in the response
- Schema changes to support ability to AAA into a different PCC to retrieve negotiated / contractual rates in the future
Service Action Code: HotelPriceCheckRQ
- Added 'HotelInfo' element to response so API returns basic descriptive hotel information
- Breakdown of tax and fee information by date range is now returned in 'Taxes' and 'Fees' elements
- Updated structure of element 'Guarantee'
- Product codes now returned in the response for GDS products in 'ProductCode'
- Schema changes to support ability to AAA into a different PCC to retrieve negotiated / contractual rates in the future
Service Action Code: GetHotelContentRQ
- The response now shows both the Sabre Hotel Code and the Global ID
- Added ability to view Security Features mapped to a property
- Amenities can now have a text description assosciated to them
- Schema changes to support ability to AAA into a different PCC in the future
- Renamed 'PointOfInterests' element to 'PointsOfInterest'
Service Action Code: GetHotelDetailsRQ
- The response now shows both the Sabre Hotel Code and the Global ID
- Product codes now returned in the response for GDS products in 'ProductCode'
- Breakdown of tax and fee information by date range is now returned in 'Taxes' and 'Fees' elements
- Updated structure of element 'Guarantee'
- Added ability to view Security Features mapped to a property
- Amenities can now have a text description assosciated to them
- Schema changes to support ability to AAA into a different PCC to retrieve negotiated / contractual rates in the future
- Renamed 'PointOfInterests' element to 'PointsOfInterest'