Create Access Token

 

TokenCreateRQ is utilized to request a SOAP API access token.

API Information

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

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

  • Authenticates the request
  • Authorizes the client to access the specific service being called
  • Returns a unique, encrypted security token to the client via the TokenCreateRS response message (wsse:BinarySecurityToken, a child of wsse:Security)
  • Returns the same conversation ID via eb:ConversationId, from the TokenCreateRQ message
  • Returns a reference to the message ID of the corresponding request in eb:RefToMessageId

The conversation ID and security access token are referred to as the connection ID. Their return means the connection to the Sabre gateway has been established and a Sabre Access Token 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.

Sample request

<SOAP-ENV:Envelope>
    <SOAP-ENV:Header>
        <eb:MessageHeader eb:version="1">
            <eb:From>
                <eb:PartyId>Client</eb:PartyId>
            </eb:From>
            <eb:To>
                <eb:PartyId>SWS</eb:PartyId>
            </eb:To>
            <eb:CPAId>PCC</eb:CPAId>
            <eb:ConversationId>1234</eb:ConversationId>
            <eb:Service>Session</eb:Service>
            <eb:Action>TokenCreateRQ</eb:Action>
            <eb:MessageData>
                <eb:MessageId>1234</eb:MessageId>
                <eb:Timestamp>2015-01-01T00:00:00</eb:Timestamp>
            </eb:MessageData>
        </eb:MessageHeader>
        <wsse:Security>
            <wsse:UsernameToken>
                <wsse:Username>USER</wsse:Username>
                <wsse:Password>PASSWORD</wsse:Password>
                <Organization>PCC</Organization>
                <Domain>DOMAIN</Domain>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <sws:TokenCreateRQ Version="1.0.0" />
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Sample response

<SOAP-ENV:Envelope>
    <SOAP-ENV:Header>
        <eb:MessageHeader eb:version="1">
            <eb:From>
                <eb:PartyId>Client</eb:PartyId>
            </eb:From>
            <eb:To>
                <eb:PartyId>SWS</eb:PartyId>
            </eb:To>
            <eb:CPAId>PCC</eb:CPAId>
            <eb:ConversationId>1234</eb:ConversationId>
            <eb:Service>Session</eb:Service>
            <eb:Action>TokenCreateRS</eb:Action>
            <eb:MessageData>
                <eb:MessageId>1234</eb:MessageId>
                <eb:Timestamp>2015-01-01T00:00:00</eb:Timestamp>
            </eb:MessageData>
        </eb:MessageHeader>
        <wsse:Security>
            <wsse:BinarySecurityToken valueType="String" EncodingType="wsse:Base64Binary">T1RLAQKvhOegyUujiZpE+uDAjHHmRfRmxRDDuJCPlszyUSmyhKGXWR0JAACgeveXEFWUPWzsmw9+Ihd9BSDYEtpikXHi8yJ9iW7vXgJpDNqnktLD4W8P7UP3zdra5szeuNXQB3yNbkjcK+3Vl1Gr/f8g00qU8ZhtzIBVz/PoD48GuaxNH7/Uq7ZztI1bXu7ve9NEW6tVsp6qxbt9Jatn/B5IXf2t+T7S2l5QJU46kNg3r1H0ndhCp/pDwVT3FIo8sVSnWNZbIvUhrH6gQg**</wsse:BinarySecurityToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <sws:TokenCreateRS Version="1.0.0">
            <sws:Success/></sws:TokenCreateRS>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

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

Docs Navigation