v2.3.0 | January 7, 2021
- Added capability to include time in historical rule display request.
API Information
Format
XML
Current Version
2.3.0
Environment
Production
What's New
- Added capability to include time in historical rule display request.
Business Value
- The new optional time will allow the user to display the rule in effect on a specific day and exact time in the past. This is very helpful when one or more fare or fare-related changes has been made to the same fare class during the day requested.
Functional Updates And Enhancements
In the Request
Optional
- Parameter: TicketingDate
-
Type: dateOrTime
Description: Specifies ticketing date or date and time.
Sample Value:
<OTA_AirRulesRQ ReturnHostCommand="true" Version="2.3.0" xmlns="http://webservices.sabre.com/sabreXML/2011/10" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OptionalQualifiers>
<TravelDateOptions>
<Historical>
<TicketingDate>2020-04-15T15:25</TicketingDate>
<TravelDate>2020-04-22</TravelDate>
</Historical>
</TravelDateOptions>
</OptionalQualifiers>
<OriginDestinationInformation>
<FlightSegment>
<DestinationLocation LocationCode="LAS"/>
<MarketingCarrier Code="AA"/>
<OriginLocation LocationCode="DFW"/>
</FlightSegment>
</OriginDestinationInformation>
<RuleReqInfo>
<FareBasis Code="Y"/>
</RuleReqInfo>
</OTA_AirRulesRQ>Note: Previously the type was fulldate.
v2.2.1 | March 23, 2017
- Corrected an intermittent issue where system message containing "CONSTRUCTED ROUTING" was incorrectly parsed into response payload.
API Information
Format
XML
Current Version
2.2.1
Environment
Production
What's New
- Corrected an intermittent issue where system message containing "CONSTRUCTED ROUTING" was incorrectly parsed into response payload.
Resolved Issues
In the Response
Optional
Description: Corrected an intermittent issue where system message containing "CONSTRUCTED ROUTING" was incorrectly parsed into response payload.