Skip to main content

Send Sabre Command

2.0.0
Utility
SOAP API
Travel Agency
Airline Carrier
  • Redesigned request and response schema so that it is in line with STL standard.
  • Added capability to handle multiple host responses.
  • SDS responses do not contain any additional extra characters, which simplifies parsing.

API Information

Response Format
XML
Service Action Code
SabreCommandLLSRQ
Current Version
2.0.0
Target Audience
both
Environment
Production

What's New

  • Redesigned request and response schema so that it is in line with STL standard.
  • Added capability to handle multiple host responses.
  • SDS responses do not contain any additional extra characters, which simplifies parsing.

Functional Updates And Enhancements

In the Request

Optional

Parameter: ReturnHostCommand

Type: boolean

Description: Attribute to request the service to pass the generated sabre host command in the service response at: …/stl:ApplicationResults/stl:Error/stl:SystemSpecificResults/stl:HostCommand

Sample Value:

ReturnHostCommand="true"
Note:

In the Request

Optional

Parameter: NumResponses

Type: integer

Description: The attribute is used to capture any multiple responses if applicable. Upon receiving the first response from host system, the API waits an additional second to check if any subsequent message has been received. If @NumResponses=”n” system will wait 1 second for the subsequent message and repeat the process until the “n” number of responses is exhausted. If the system does not receive a message within the 1 second time frame, it will stop processing as pass all previously collected messages back to the user.

Sample Value:

NumResponses="4"
Note:

In the Response

Required

Parameter: ApplicationResults

Type: N/A

Description: The response schema will contain a new element /SabreCommandLLSRS/stl:ApplicationResults which follows minimal Sabre Type Library (STL) schema. STL defines common structures for Request and Response, Error Handling, etc. Please note that since SabreCommand is a passthrough service as per design a sabre host error is not considered a failed transaction. Therefore, in all situations /SabreCommandLLSRS/stl:ApplicationResults/ will show @status=”Complete” and include …stl:Success/@timeStamp

Sample Value:

 
Note:

Resolved Issues

In the Response

N/A

Sabre host response in SDS format does not contain any additional “” characters and may be parsed as is.

Relase note ID: 15114