<aside> ⚠️

Use JWT wherever possible. The standard JWT authentication flow is Splash's recommended method for every integration. This custom endpoint exists only as a last-resort compatibility bridge for platforms that genuinely cannot generate a JWT, and is arranged case by case — please raise it with Splash before planning around it.

</aside>

For the rare platform that cannot implement the standard JWT flow, Splash can provide a custom integration endpoint that bridges the gap between the Splash token and an existing platform. It is arranged case by case during integration. The following URL can be launched or embedded as a full-screen iframe:

Production

https://api.splash.tech/public/launchGame?client={{client}}&game={{gameType}}&instance={{instance}}&param1={{param1}}&param2=…

Staging

https://api-staging.splash.tech/public/launchGame?client={{client}}&game={{gameType}}&instance={{instance}}&param1={{param1}}&param2=…

• {{client}} — the unique client ID provided by Splash during integration.
• {{gameType}} — the game to launch: QUIZ, SPIN_MACHINE, WHEEL, HUB, BOARD, MULTI_WHEEL, or STREAKS. See Reference.
• {{instance}} — an instance identifier agreed during integration (e.g. soccer, nfl).
• {{param1}} — a custom parameter required for the user authentication callback, e.g. sessionToken=SecretOneTimeToken. Append additional parameters as required for the custom authentication flow with your platform.

Splash will implement a custom handler which can call a third-party system on an endpoint you provide. Inside this callback, both systems exchange information to reliably authenticate the user. Ultimately, the Splash handler constructs the token and redirects to the standard flow described in Authentication (JWT).