Player authorization
Called once when a player opens a game. Validate the launch token, then return the player’s identity and current balance.
Reject the request if the token is unknown, expired or belongs to a different player — the game will refuse to start.
The accountId you return here is the identity Zero-Dash uses for every bet, transaction, report and audit for the lifetime of that player. See Account ID.
Authorizations
Hex-encoded HMAC-SHA512(apiPath|timestamp|data, secretKey) computed by Zero-Dash. Recompute it and compare before doing anything else. See Request signature.
Unix time in milliseconds, and the exact value that was signed. Reject requests older than 5 minutes.
Query Parameters
Human-readable game slug the player is opening.
"lucky-duck"
The session token you generated and passed to the launch URL.
Response
Player authorized.
Unique, permanent, non-personal player identifier. One account ID maps to exactly one currency. See Account ID.
Name shown to other players in the same session. Must not expose personal data.
"Matthew S."
The player's balance after the operation was applied.
Optional. When several brands sit behind one integration, identify the player's brand here — the games use it to separate chat rooms and similar shared surfaces.
"9"