Create Session


SessionCreateRQ is utilized to initiate a SOAP API session.

API Information

Target Audience
All Sabre APIs Customers
Current Version
Session Token
Service Action Code

Security credentials, consisting of a username, password, organization, and domain are required to connect. When a client sends a correctly-formatted SessionCreateRQ message with valid security credentials to any of the designated endpoints (PROD or CERT), the Sabre Web Services gateway does the following:

  • Authenticates the request
  • Authorizes the client to access the specific service being called
  • Allocates a Sabre session from the client application's session pool
  • Returns a unique, encrypted security token to the client via the SessionCreateRS response message (wsse:BinarySecurityToken, a child of wsse:Security)
  • Returns the same conversation ID via eb:ConversationId, from the SessionCreateRQ message
  • Returns a reference to the message ID of the corresponding request in eb:RefToMessageId

The conversation ID and security token are referred to as the connection ID. Their return means the connection to the Sabre Web Services gateway has been established and a Sabre session is allocated. The client must extract and store the returned values for eb:CPAId, eb:ConversationId, and the entire wsse:security@wsse:BinarySecurityToken node for inclusion in subsequent requests and workflows that use this particular connection.

When the connection is no longer needed, SessionCloseRQ (with the same connection ID) is utilized to close the connection. This properly cleans up the session and releases all resources allocated to the session behind the scenes.
Errors are returned in SOAP fault format, with or without ebXML headers.

Sample request

<SessionCreateRQ returnContextID="true">
    <Source PseudoCityCode="W2PH"/>

Sample response

<SessionCreateRS version="1" status="Approved" xmlns="">

If you are a Sabre customer currently using Sabre APIs in production, access  Resources

Docs Navigation