Skip to main content
Generates a temporary, single-use URL that opens the game for a specific player. The URL is short-lived and must be loaded by the client immediately.

Endpoint

Headers

Always forward the player’s real User-Agent.PlayStarters uses the User-Agent header to detect whether the player is on a mobile or desktop device. Many game providers serve different game builds for mobile and desktop — if the header is missing or incorrect, the player may receive the wrong version.If your backend proxies the launch request (i.e. the call to /operator/launch is made server-side rather than directly from the browser), you must forward the original User-Agent header from the player’s browser.

Body parameters

string
required
Game identifier. Accepts a game slug (e.g. pragmatic:sweet-bonanza), an internal UUID, or an external provider ID. Retrieve values from GET /operator/games.
string
required
Your unique identifier for the player. This is the same value PlayStarters will send to your Seamless Wallet endpoint as playerId.
string
required
ISO 4217 currency code (e.g. EUR, USD, BRL). Must match the wallet currency your backend will return for this player.
string
default:"en"
ISO 639-1 locale code for the game UI language. Defaults to en.
string
URL to redirect the player to when they close the game. If omitted, the request’s Origin header is used as fallback.
string
URL to your deposit page. Some providers display a deposit button inside the game that links here.
boolean
default:"false"
Launch in demo/fun mode. No real-money wallet calls will be made.
string
Player’s IP address. Forwarded to the game provider for geo-checks and fraud prevention.
string
Player’s email address. Some providers require this for regulatory compliance.
string
Player’s first name. Used by providers that display player info in-game.
string
Player’s last name.
string
Player’s display name or username. Defaults to playerId if omitted.
string
ISO 3166-1 alpha-2 country code for the player’s country (e.g. DE, BR). Used by some providers for regulatory compliance.
string
Player auth token (JWT). Used by some game providers for player identification. If omitted, playerId is used as fallback.
string
Arbitrary string echoed back in wallet callbacks. Useful for tracking campaign attribution or session metadata.

Example request

Response — 200 OK

Response fields

string
Temporary URL that loads the game for the requested player. Open this URL in an iframe or a new browser window/tab on the client.
string
Script that must be included on every page embedding the game (required by some providers).
string
The aggregator’s internal game identifier (for debugging).
string
The provider code used.
string
Opaque session token. If present, you can pass it back to POST /operator/close-session when the player leaves the game to clean up the session immediately. This field is optional — if omitted, the session expires automatically after a period of inactivity.
Treat the launch URL as a session token. Do not log it, cache it, or share it across players. Each call to /operator/launch returns a fresh URL.
Before launching, make sure your Seamless Wallet callback is reachable. PlayStarters will call it as soon as the game opens to read the player balance, and again for each bet, win, or refund.