Not Signed In.
Looks like you may not have access to all of the resources and documentation for this page.
Please log-in or contact your support desk team if you believe you should have access.
The Validate Session (SessionValidateRQ) service is used to verify security credentials or login information used to create or to refresh a SOAP API connection by resetting the connection's timestamp, thereby preventing the connection in the connection pool from timing out.
In order to use this service, a live connection to Sabre Web Services, along with a valid binary security token, conversation ID are required.
When a client application sends a correctly-formatted SessionValidateRQ message, the Sabre Web Services gateway does the following:
- Returns the following security credentials that were sent in the SessionCreateRQ message to create the connection
- Resets the connection's timestamp
After establishing a connection, SessionValidateRQ can be sent at any time, and as often as needed. It has no effect on session state, business content, or travel workflows. An example of when to send this service would be whenever your connection manager detects that the timestamp of a particular connection in your connection pool is approximately 2 minutes less than the connection's time-out value.
The request message does not have a payload, and so the response message returns an empty payload.
Errors are returned in SOAP fault format, with or without ebXML headers.
<SOAP-ENV:Header>
<eb:MessageHeader SOAP-ENV:mustUnderstand="1" eb:version="1.0">
<eb:From>
<eb:PartyId type="urn:x12.org:IO5:01">999999</eb:PartyId>
</eb:From>
<eb:To>
<eb:PartyId type="urn:x12.org:IO5:01">123123</eb:PartyId>
</eb:To>
<eb:CPAId>FF9A</eb:CPAId>
<eb:ConversationId>webservices.support@sabre.com</eb:ConversationId>
<eb:Service eb:type="OTA">SessionValidateRQ</eb:Service>
<eb:Action>SessionValidateRQ</eb:Action>
<eb:MessageData>
<eb:MessageId>1000</eb:MessageId>
<eb:Timestamp>2014-06-16T00:00:00Z</eb:Timestamp>
</eb:MessageData>
</eb:MessageHeader>
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">
<wsse:BinarySecurityToken>Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/ACPCRTC!ICESMSLB\/CRT.LB!-3629581695191042687!716834!0!1</wsse:BinarySecurityToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SessionValidateRQ>
<POS>
<Source PseudoCityCode="FF9A"/>
</POS>
</SessionValidateRQ>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<soap-env:Header>
<eb:MessageHeader eb:version="1.0" soap-env:mustUnderstand="1" xmlns:eb="http://www.ebxml.org/namespaces/messageHeader">
<eb:From>
<eb:PartyId eb:type="URI">123123</eb:PartyId>
</eb:From>
<eb:To>
<eb:PartyId eb:type="URI">999999</eb:PartyId>
</eb:To>
<eb:CPAId>FF9A</eb:CPAId>
<eb:ConversationId>webservices.support@sabre.com</eb:ConversationId>
<eb:Service eb:type="sabreXML">Session</eb:Service>
<eb:Action>SessionValidateRS</eb:Action>
<eb:MessageData>
<eb:MessageId>fb3a8eb9-89c0-464a-8797-ee736503e2d0@152</eb:MessageId>
<eb:Timestamp>2014-08-19T21:08:29</eb:Timestamp>
<eb:RefToMessageId>1000</eb:RefToMessageId>
</eb:MessageData>
</eb:MessageHeader>
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext">
<wsse:BinarySecurityToken valueType="String" EncodingType="wsse:Base64Binary">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/ACPCRTC!ICESMSLB\/CRT.LB!-3629581695191042687!716834!0!1</wsse:BinarySecurityToken>
<wsse:UsernameToken>
<wsse:Username>54321</wsse:Username>
<Organization>FF9A</Organization>
<Domain>DEFAULT</Domain>
</wsse:UsernameToken>
</wsse:Security>
</soap-env:Header>
<soap-env:Body>
<SessionValidateRS/>
</soap-env:Body>
</soap-env:Envelope>