v1.19.21 | September 28, 2023
- This new release offers the ability to retrieve additional information from the reservation.
API Information
What's New
- This new release offers the ability to retrieve additional information from the reservation.
New Features
In the Response
Optional
- Parameter: CheckInInfo
-
Type: String
Description: The new response element is dedicated to returning information regarding Passenger Checkin Information. The new element will be returned under the following response node: Reservation/PassengerReservation/Segments/Air/CheckInInfo
Sample Value:
<CheckInInfo>CHECK-IN ONLINE AT RAIL-CHECKIN.CO</CheckInInfo>Note: Examples of request and response are available in the Resources tab.
In the Response
Optional
- Parameter: CheckInAirlineCode
-
Type: String
Description: The new response element is dedicated to returning information regarding Check-in Carrier Code. The new element will be returned under the following response node: Reservation/PassengerReservation/Segments/Air/CheckInAirlineCode This element is always returned together with CheckInInfo response parameter.
Sample Value:
<CheckInInfo>CHECK-IN WITH AMERICAN AIRLINES</CheckInInfo>
<CheckInAirlineCode>AA</CheckInAirlineCode>Note: Examples of request and response are available in the Resources tab.
In the Response
Optional
- Parameter: GroupManagementInformation
-
Type: Complex
Description: The new response element is dedicated to returning information regarding Group Manager Information that can be returned for Group Bookings. The new element will be returned under the following response node: Reservation/PassengerReservation/Segments/Air/GroupManagementInformation
Sample Value:
<stl19:GroupManagementInformation>
<stl19:GmrLocator>VYMIXW</stl19:GmrLocator>
<stl19:OaDealId>
<stl19:AirlineCode>AA</stl19:AirlineCode>
<stl19:AirlineLocator>LNJDMO</stl19:AirlineLocator>
</stl19:OaDealId>
</stl19:GroupManagementInformation>Note: The information returned under GroupManagementInformation is equivalent to the one that can be returned using host entry: T/XBAS*28« EXTENDED BAS INFORMATION DISPLAY SEGMENT NUMBER: 01 *TYPE 28 - GROUP MANAGER INFORMATION GMR LOCATOR - VYMIXW OA DEAL ID - AA*LNJDMO Examples of request and response are available in the Resources tab.
v1.19.20 | August 3, 2023
- This new release offers the ability to retrieve additional information from the reservation.
API Information
What's New
- This new release offers the ability to retrieve additional information from the reservation.
New Features
In the Response
Optional
- Parameter: MembershipPrograms
-
Type: Complex
Description: The new response element is dedicated to return detailed information regarding all loyalty programs for a particular Frequent Traveler. This is an optional element and can be returned only in certain cases when Carrier supports multiple loyalty programs. New element will be returned under the following response node: Reservation/OpenReservationElements/OpenReservationElements/Loyalty/FrequentFlyer/MembershipPrograms
Sample Value:
<or114:FrequentFlyer>
<or114:ActionCode>HK</or114:ActionCode>
<or114:PreviousActionCode>NN</or114:PreviousActionCode>
<or114:Vendor>XX</or114:Vendor>
<or114:ReceivingCarrierCode>XX</or114:ReceivingCarrierCode>
<or114:VitType>97</or114:VitType>
<or114:FrequentFlyerNumber>Y94W899</or114:FrequentFlyerNumber>
<or114:ATPCOTierLevel>1</or114:ATPCOTierLevel>
<or114:Banner>EXECUTIVE PLATINUM * EMERALD</or114:Banner>
<or114:Tag>EXP/EMD/AAP/PCC</or114:Tag>
<or114:MembershipPrograms domainId="XX" supplierCode="XX">
<or114:MembershipProgram>
<or114:ProgramType>FT</or114:ProgramType>
<or114:TierValue>04</or114:TierValue>
<or114:PnrTier>96</or114:PnrTier>
<or114:AtpcoTier>1</or114:AtpcoTier>
<or114:DisplayPriority>2</or114:DisplayPriority>
<or114:Banner>EXECUTIVE PLATINUM * EMERALD</or114:Banner>
<or114:PrimaryTag>EXP</or114:PrimaryTag>
<or114:DisplayTag>EXP/EMD</or114:DisplayTag>
</or114:MembershipProgram>
<or114:MembershipProgram>
<or114:ProgramType>AP</or114:ProgramType>
<or114:TierValue>13</or114:TierValue>
<or114:PnrTier>1</or114:PnrTier>
<or114:DisplayPriority>20</or114:DisplayPriority>
<or114:Banner>AIRPASS - NO COMPANION BENEFITS</or114:Banner>
<or114:PrimaryTag>AAP</or114:PrimaryTag>
<or114:DisplayTag>AAP</or114:DisplayTag>
</or114:MembershipProgram>
<or114:MembershipProgram>
<or114:ProgramType>PC</or114:ProgramType>
<or114:TierValue>10</or114:TierValue>
<or114:PnrTier>4096</or114:PnrTier>
<or114:AtpcoTier>8</or114:AtpcoTier>
<or114:DisplayPriority>30</or114:DisplayPriority>
<or114:Banner>PREMIUM CREDIT CARD</or114:Banner>
<or114:PrimaryTag>PCC</or114:PrimaryTag>
<or114:DisplayTag>PCC</or114:DisplayTag>
</or114:MembershipProgram>
</or114:MembershipPrograms>
</or114:FrequentFlyer>Note: Example of request and response in the Resources section.
v1.19.19 | June 15, 2023
- This new release offers ability to retrieve additional information from the reservation
API Information
What's New
- This new release offers ability to retrieve additional information from the reservation
New Features
In the Response
Optional
- Parameter: SubscriptionCard
-
Type: Complex
Description: New response element is dedicated to return Air France Subscription Card which allows all Sabre-connected agents to connect to the Air France Subscription Card holder's server and use the specially discounted Subscription Card holder's fares. Subscription Card information will be returned under following response element: Reservation/SubscriptionCards/ SubscriptionCard
Sample Value:
<stl19:SubscriptionCard id="17">
<stl19:NameAssociation>
<stl19:AssociatedName>1</stl19:AssociatedName>
</stl19:NameAssociation>
<stl19:SubscriptionCardNumber>999426244</stl19:SubscriptionCardNumber>
<stl19:SubscriptionCardAirline>AF</stl19:SubscriptionCardAirline>
<stl19:FrequentFlyerNumber/>
<stl19:RejectedCard>false</stl19:RejectedCard>
<stl19:DateValidFrom>2021-10-19</stl19:DateValidFrom>
<stl19:DateValidTo>2023-10-18</stl19:DateValidTo>
<stl19:SubscriptionCardSegments>
<stl19:SubscriptionCardSegment>
<stl19:ValidSegmentAssociation>true</stl19:ValidSegmentAssociation>
<stl19:Segment>
<stl19:CarrierCode>AF</stl19:CarrierCode>
<stl19:FlightNumber>1105</stl19:FlightNumber>
<stl19:DepartureDate>2023-09-27</stl19:DepartureDate>
<stl19:BoardPoint>FCO</stl19:BoardPoint>
<stl19:OffPoint>CDG</stl19:OffPoint>
<stl19:ClassOfService>Y</stl19:ClassOfService>
</stl19:Segment>
<stl19:AssociatedItinerarySegment>2</stl19:AssociatedItinerarySegment>
<stl19:SubscriptionOrDiscountCode>RPFM</stl19:SubscriptionOrDiscountCode>
<stl19:PassengerTypeCode>CFM</stl19:PassengerTypeCode>
</stl19:SubscriptionCardSegment>
</stl19:SubscriptionCardSegments>
</stl19:SubscriptionCard>Note: Example of request and response in the Resources section.
v1.19.18 | April 27, 2023
- This new release offers the ability to retrieve additional payment data from the reservation.
API Information
What's New
- This new release offers the ability to retrieve additional payment data from the reservation.
New Features
In the Response
Optional
- Parameter: InterfaceUserRecord
-
Type: Complex
Description: New response parameters stored for payment cards with the IR Use Type can now be returned for Back Office (UIR) System purposes. If registered, Amount and Notes information can be returned as sub-elements under the following response elements: For an active form of payment: Reservation/OpenReservationElements/OpenReservationElements/FormOfPayment/PaymentCard/InterfaceUserRecord For historical transactions: Reservation/History/HistoryTransaction/ItineraryHistoryOrRemarkHistoryOrFactHistory/FormOfPayment/PaymentCard/InterfaceUserRecord
Sample Value:
<or114:FormOfPayment migrated="false">
<or114:PaymentCard reconcileAsCash="false" virtual="false">
<or114:PaymentType>CC</or114:PaymentType>
<or114:CardCode>AX</or114:CardCode>
<or114:CardNumber tokenized="true" masked="true">3XXXXXXXXXX2009</or114:CardNumber>
<or114:ExpiryMonth>--12</or114:ExpiryMonth>
<or114:ExpiryYear>2023</or114:ExpiryYear>
<or114:DefaultExtendPayment>false</or114:DefaultExtendPayment>
<or114:SuppressFromInvoice>false</or114:SuppressFromInvoice>
<or114:GenerateApprovalAtTicketing>false</or114:GenerateApprovalAtTicketing>
<or114:InterfaceUserRecord>
<or114:Amount currencyCode="USD">300.95</or114:Amount>
<or114:Notes>Notes for Back Office </or114:Notes>
</or114:InterfaceUserRecord>
</or114:PaymentCard>
</or114:FormOfPayment>Note: Full request and response examples containing these new parameters are available in the Resources section.
v1.19.17 | February 16, 2023
- In this version new functionality was introduced.
API Information
What's New
- In this version new functionality was introduced.
Business Value
- Ability to retrieve additional data from the reservation.
New Features
In the Response
Optional
- Parameter: PreferredCustomer
-
Type: boolean
Description: A new parameter stored in the cardholder's information now indicates whether the cardholder is a preferred customer: *CC« CREDIT CARD DATA PREFERRED CUSTOMER STATUS - AUTO AVS NOT REQUESTED PreferredCustomer will be returned as an attribute within the following response element: Reservation/PassengerReservation/FormsOfPayment/CreditCardPayment/CardHolderInfo/@PreferredCustomer
Sample Value:
<stl19:CardHolderInfo Name="TEST PAX" PreferredCustomer="true">
<stl19:AddressLines>
<stl19:AddressLine>
<stl19:Text>LONG</stl19:Text>
</stl19:AddressLine>
<stl19:AddressLine>
<stl19:Text>STREET</stl19:Text>
</stl19:AddressLine>
<stl19:AddressLine>
<stl19:Text>12323-2323</stl19:Text>
</stl19:AddressLine>
</stl19:AddressLines>
</stl19:CardHolderInfo>Note: Full request and response examples containing this new element are available in the Resource section.
In the Response
Optional
- Parameter: nameId
-
Type: string
Description: A new response parameter called nameId has been added to TicketDetails and AccountingLines. This parameter identifies the Name field the PNR, ticket, and accounting line are associated with. The PNAPNR TJR setting determines whether nameId will be returned in the response. The parameters below will only be returned if PNAPNR is set to ON in the pcc TJR: Reservation/PassengerReservation/Passengers/Passenger/TicketingInfo/TicketDetails/PassengerName/@nameId Reservation/PassengerReservation/Passengers/Passenger/AccountingLines/accountingLine/passengerName/@nameId Reservation/PassengerReservation/TicketingInfo/TicketDetails/PassengerName/@nameId The parameter below will be returned regardless of what the PNAPNR setting is: Reservation/AccountingLines/AccountingLine/PassengerName/@nameId
Sample Value:
AccountingLine information:
<stl19:AccountingLine id="18" index="1" elementId="pnr-18">
<stl19:FareApplication>ONE</stl19:FareApplication>
<stl19:FormOfPaymentCode>CA</stl19:FormOfPaymentCode>
<stl19:AirlineDesignator>AF</stl19:AirlineDesignator>
<stl19:DocumentNumber>7959016930</stl19:DocumentNumber>
<stl19:CommissionAmount>0.00</stl19:CommissionAmount>
<stl19:Fare>1010.00</stl19:Fare>
<stl19:BaseFare>1010.00</stl19:BaseFare>
<stl19:TaxAmount>50.80</stl19:TaxAmount>
<stl19:PassengerName nameId="1.1">MOSIO PAT</stl19:PassengerName>
<stl19:NumberOfConjunctedDocuments>1</stl19:NumberOfConjunctedDocuments>
<stl19:TarriffBasis>F</stl19:TarriffBasis>
<stl19:TransactionInd>E</stl19:TransactionInd>
<stl19:AccountingLineText> AF$7959016930/ 0.00/ 1010.00/ 50.80/ONE/CA 1.1MOSIO PAT/1/F/E</stl19:AccountingLineText>
</stl19:AccountingLine>
TicketDetails information:
<stl19:TicketDetails id="26" index="2" elementId="pnr-26">
<stl19:OriginalTicketDetails>TE 0557959016950-AT MOSIO/P B4T0*-KR 2040/02JUN*</stl19:OriginalTicketDetails>
<stl19:TransactionIndicator>TE</stl19:TransactionIndicator>
<stl19:TicketNumber>0557959016950</stl19:TicketNumber>
<stl19:PassengerName nameId="01.01">MOSIO/P</stl19:PassengerName>
<stl19:AgencyLocation>B4T0</stl19:AgencyLocation>
<stl19:DutyCode>*</stl19:DutyCode>
<stl19:AgentSine>-KR</stl19:AgentSine>
<stl19:Timestamp>2023-06-02T20:40:00</stl19:Timestamp>
<stl19:PaymentType>*</stl19:PaymentType>
<stl19:Status>ACTIVE</stl19:Status>
</stl19:TicketDetails>Note: Full request and response examples containing this new element are available in the Resource section.
v1.19.16 | June 1, 2022
- In this version new functionality was introduced.
API Information
What's New
- In this version new functionality was introduced.
New Features
In the Response
Optional
- Parameter: LegacyCompatible
-
Type: boolean
Description: The new IUR attribute "LegacyCompatible" is valid for GDS bookings only. This parameter is stored within the segment details, with a default value of "False". The data will be available in active segment details and also in historical details under the following elements: Reservation/PassengerReservation/Segments/Product/or:ProductDetails/or:Lodging/@LegacyCompatible Reservation/History/HistoryTransaction/ProductDetailsHistory/or:Lodging/@LegacyCompatible
Sample Value:
Example:
<or114:Lodging LegacyCompatible="true">
<or114:ResGlobalInfo>
<or114:BookingInfo Status="39" RequestorID="SG000000" InfoSource="100" TransactionId="IHFVIK0101653055002563" Email="Orville.Wright@sabre.com">
<or114:BookingKey>6fcba3a0-d52a-4d3a-a10c-2fe11bca63de</or114:BookingKey>
<or114:HotelReservationIds>
<or114:HotelReservation Id="IHFVIK" Type="24"/>
<or114:HotelReservation Id="99999999" Type="5"/>
<or114:HotelReservation Id="5603WIC502" Type="40"/>
</or114:HotelReservationIds>
</or114:BookingInfo>
...
<stl19:ProductDetailsHistory ProductId="3" productCategory="AGTLCSSEGMENT" productType="HHL" vendorCode="RT" statusCode="HK" startPoint="SYD" startDateTime="2022-09-13T00:00:00" endPoint="SYD" endDateTime="2022-09-15T00:00:00">
<or114:ProductName type="HHL">Lodging</or114:ProductName>
<or114:Lodging LegacyCompatible="true">
<or114:ResGlobalInfo>
...
v1.19.14 | December 10, 2021
- In this version new functionality was introduced.
API Information
What's New
- In this version new functionality was introduced.
Business Value
- Ability to retrieve additional data from the PNR
New Features
In the Response
Optional
- Parameter: New response schema element for PreReservedSeat, returned in case of seats that are unavailable following an equipment change
-
Type: boolean
Description: New element will be visible under: reservation/passengerReservation/segments/segment/air/seats/preReservedSeats/preReservedSeat/seatErrorDuringReaccommodation and reservation/passengerReservation/passengers/passenger/seats/preReservedSeats/preReservedSeat/seatErrorDuringReaccommodation
Sample Value:
Host Level:
*B«
SEATS/BOARDING PASS
1 1212Y 20DEC DFWORD HK¤ 18A NW BLP 1.1 SMITH/ALICE MRS
The same information in GetReservationRQ response:
<stl19:PreReservedSeat id="8">
<stl19:SeatNumber>18A</stl19:SeatNumber>
<stl19:SmokingPrefOfferedIndicator>false</stl19:SmokingPrefOfferedIndicator>
<stl19:SeatTypeCode>WLMOIQG</stl19:SeatTypeCode>
<stl19:SeatStatusCode>HK</stl19:SeatStatusCode>
<stl19:PreviousSeatStatusCode>SS</stl19:PreviousSeatStatusCode>
<stl19:SeatErrorDuringReaccommodation>true</stl19:SeatErrorDuringReaccommodation>
<stl19:BoardPoint>DFW</stl19:BoardPoint>
<stl19:OffPoint>ORD</stl19:OffPoint>
<stl19:Changed>Y</stl19:Changed>
<stl19:NameNumber>01.01</stl19:NameNumber>
</stl19:PreReservedSeat>
v1.19.14 | December 10, 2021
- In this version new functionality was introduced.
API Information
What's New
- In this version new functionality was introduced.
Business Value
- Ability to retrieve additional data from the PNR
New Features
In the Response
Optional
- Parameter: New response schema element for PreReservedSeat, returned in case of seats that are unavailable following an equipment change
-
Type: boolean
Description: New element will be visible under: reservation/passengerReservation/segments/segment/air/seats/preReservedSeats/preReservedSeat/seatErrorDuringReaccommodation and reservation/passengerReservation/passengers/passenger/seats/preReservedSeats/preReservedSeat/seatErrorDuringReaccommodation
Sample Value:
Host Level:
*B«
SEATS/BOARDING PASS
1 1212Y 20DEC DFWORD HK¤ 18A NW BLP 1.1 SMITH/ALICE MRS
The same information in GetReservationRQ response:
<stl19:PreReservedSeat id="8">
<stl19:SeatNumber>18A</stl19:SeatNumber>
<stl19:SmokingPrefOfferedIndicator>false</stl19:SmokingPrefOfferedIndicator>
<stl19:SeatTypeCode>WLMOIQG</stl19:SeatTypeCode>
<stl19:SeatStatusCode>HK</stl19:SeatStatusCode>
<stl19:PreviousSeatStatusCode>SS</stl19:PreviousSeatStatusCode>
<stl19:SeatErrorDuringReaccommodation>true</stl19:SeatErrorDuringReaccommodation>
<stl19:BoardPoint>DFW</stl19:BoardPoint>
<stl19:OffPoint>ORD</stl19:OffPoint>
<stl19:Changed>Y</stl19:Changed>
<stl19:NameNumber>01.01</stl19:NameNumber>
</stl19:PreReservedSeat>