Skip to main content
GET
Player authorization

Authorizations

X-Zd-Signature
string
header
required

Hex-encoded HMAC-SHA512(apiPath|timestamp|data, secretKey) computed by Zero-Dash. Recompute it and compare before doing anything else. See Request signature.

X-Zd-Timestamp
string
header
required

Unix time in milliseconds, and the exact value that was signed. Reject requests older than 5 minutes.

Query Parameters

gameId
string
required

Human-readable game slug the player is opening.

Example:

"lucky-duck"

token
string
required

The session token you generated and passed to the launch URL.

Response

Player authorized.

accountId
string
required

Unique, permanent, non-personal player identifier. One account ID maps to exactly one currency. See Account ID.

displayName
string
required

Name shown to other players in the same session. Must not expose personal data.

Example:

"Matthew S."

balance
object
required

The player's balance after the operation was applied.

subOperatorId
string

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.

Example:

"9"