The Send Sabre Command (SabreCommandLLSRQ) API is used to send specific Sabre® system commands that are not available as structured Sabre Web Services.
Important! To support Sabre technology modernization efforts, we are changing the Sabre agency reservation logic and workflows for American Airlines (AA), which will result in AA and Sabre agencies no longer sharing a single reservation (PNR). Click here to view the documentation on potential impacts to existing workflows.
Note: Please refrain from using this service for commands that are available as a structured Sabre Web Service. Improper use for purposes other than those intended may result in unexpected or undesirable responses, which are not supported.
SabreCommandLLSRQ offers client applications several different options for formatting the response data via the @Output attribute. Clients have the ability to specify "SCREEN," "SDS," or "SDSXML" via @Output.
If "SCREEN" is specified via @Output, the response will be returned in screen format.
If "SDS" or "SDSXML" is specified via @Output, the response will be returned in Sabre Data Source (SDS) response format. Please note that the SDSXML option simply converts the SDS-delimiter character set into XML. For additional SDS-related details please visit sds.sabre.com. Please note that if clients opt to utilize SDS-based functionality via the SabreCommandLLSRQ service they need to be plugged into the SDS change notification process to ensure no negative impact to their applications when the various content teams make changes to their SDS responses. Clients can sign up for SDS-related notifications, which are delivered via the Sabre Advance Notification (SAN) process, by submitting a request to their account executive.
When commands in the Sabre system include special characters, it is recommended that clients define character variables using hexadecimal codes . To insert the special characters, the character variable is included with other characters. Doing it this way avoids problems associated with different font/character sets.
Example of character variables:
- char CROSS_OF_LORRAINE_CHAR = (char) 0xA5;
- char CHANGE_KEY_CHAR = (char) 0xA4;
- char END_ITEM_CHAR = (char) 0xA7;
Example of a .NET client calling a special character:
- req.Value="1"+ CROSS_OF_LORRAINE_CHAR + "2"; where the value sent with the SabreCommandLLSRQ element is “1‡2”.
Please note that several host shopping-based commands, i.e. JR and WPNI-type commands, utilize underlying Tripsearch/Bargain Finder(sm) Plus-based functionality, which are categorized as "Worldfare" scans. These commands are charged at a higher price point. For additional information please refer to the Format Finder Help System reference: homtp001.
<SabreCommandLLSRQ ReturnHostCommand="true" Version="2.0.0">
17MAR WED JFK/EDT SFO/PDT-3 1UA 1978 J9 C9 D9 Z9 P7*EWRSFO N 200P 534P 752 L/N 0 DCA /E Y9 B9 M9 E9 U9 H9 Q9 V9 W9 2UA 2264 J9 C9 D9 Z9 P9*EWRSFO N 1200N 338P 757 L/N 0 DCA /E Y9 B9 M9 E9 U9 H9 Q9 V9 W9 3UA 583 J9 C9 D9 Z9 P9*EWRSFO 9 300P 627P 757 L/N 0 DCA /E Y9 B9 M9 E9 U9 H9 Q9 V9 W9 4UA 739 J9 C9 D9 Z9 P9*EWRSFO N 400P 708P 781 D/N 0 DCA /E O9 A9 R9 Y9 B9 M9 E9 U9 H9 5UA 2080 J9 C9 D9 Z9 P7*EWRSFO N 1100A 238P 752 L/N 0 DCA /E Y9 B9 M9 E9 U9 H9 Q9 V9 W9 6UA 1991 J9 C9 D9 Z9 P9*EWRSFO 8 1000A 138P 757 L/N 0 DCA /E Y9 B9 M9 E9 U9 H9 Q9 V9 W9 * - FOR ADDITIONAL CLASSES ENTER 1*C.