Thunder API – Authentication Token

Overview

Thunder launch URLs require an authentication token inside the XML payload.

The token is generated through the Thunder SSO service using:

• Thunder Cloud user credentials
• A vendor GUID
• Optional token duration

The returned token is then used in the <authentication> element of a Thunder launch URL.

Endpoint

GenerateToken

POST https://tcssoservices.xosdigital.com/sso/RESTSSOServices.svc/GenerateToken

GenerateTokenWithDuration

For a custom token duration:

POST https://tcssoservices.xosdigital.com/sso/RESTSSOServices.svc/GenerateTokenWithDuration

Authentication Headers

For required authentication headers and how to generate the authorization value, see:

Thunder API – Authentication Headers

Request Body

GenerateToken

{
  "productId": "VENDOR_GUID"
}

GenerateTokenWithDuration

{
  "productId": "VENDOR_GUID",
  "durationInMins": 30
}

Parameters

Vendor GUID

Team integrations commonly use:

960c346c-89db-423a-aede-3011dd3d0b77

Third-party vendors and integrations may be provided with a different vendor GUID.

Note: Do not assume 960c346c-89db-423a-aede-3011dd3d0b77 applies to all integrations. Third-party vendors should use the vendor GUID assigned to them.

Token Duration

Authentication tokens are short-lived.

If no duration is supplied, the default token lifetime is approximately 15 minutes.

If a duration is supplied, the maximum supported duration is 24 hours (1440 minutes).

Example

{
  "productId": "960c346c-89db-423a-aede-3011dd3d0b77",
  "durationInMins": 1440
}

Using the Token

The returned token is used in the Thunder launch XML.

<authentication token='TOKEN' vendor='VENDOR_GUID'/>

Example

<root>
    <authentication token='TOKEN' vendor='960c346c-89db-423a-aede-3011dd3d0b77'/>
    <payload>
        ...
    </payload>
</root>

Notes

• The user credentials must have access to the Thunder database being used.
• The vendor GUID must be enabled for the requesting user.
• Third-party vendors should use the vendor GUID assigned to them.
• Tokens should be regenerated after they expire.

Related Articles

• Thunder API – Authentication Headers
• Thunder API – LaunchPlayerByPlays / LaunchPlayerByEdits
• Thunder API – LaunchPlayerByGSIS / LaunchPlayerByGSISNonPro
• Thunder API – LaunchPlayer
• Thunder API – XOSMessageXMLGet / XOSMessageXML
• Thunder API – MessageXMLGet / MessageXML
• Thunder API – PFFMessageXMLGet / PFFMessageXML