Thunder API – LaunchPlayer

Overview

LaunchPlayer launches STATS plays in Thunder using STATS play IDs.

This launch method uses the simplified LaunchPlayer payload structure, where the <payload> element contains a comma-delimited list of play identifiers.

URL Format

/XOS/launchplayer?plays=<root>...</root>

Authentication

LaunchPlayer requires a valid authentication token in the launch XML.

For information on:

• Generating authentication tokens
• Vendor GUID requirements
• Token duration and expiration
• Authentication examples

See:

Thunder API – Authentication Token

Common XML Structure

LaunchPlayer uses the following XML payload structure.

<root>
    <authentication token='TOKEN' vendor='VENDOR_GUID'/>
    <payload>
        PLAYID_1,PLAYID_2,PLAYID_3
    </payload>
</root>

Request Parameters

Play IDs

LaunchPlayer uses STATS play IDs.

GameKey is not required for LaunchPlayer.

Multiple play IDs are separated using a comma.

Example:

PLAYID_1,PLAYID_2,PLAYID_3

Example XML Structure

<root>
    <authentication token='TOKEN' vendor='VENDOR_GUID'/>
    <payload>
        PLAYID_1,PLAYID_2,PLAYID_3
    </payload>
</root>

Notes

• Uses STATS play IDs.
• Play IDs are comma-delimited.
• GameKey is not required.
• The query string parameter is plays.

Related Articles

• Thunder API – Authentication Token
• Thunder API – Creating Thunder Launch URLs
• Thunder API – LaunchPlayerByPlays / LaunchPlayerByEdits
• Thunder API – LaunchPlayerByGSIS / LaunchPlayerByGSISNonPro