Set Client Seed

Sets the player's client seed for the game and resets the nonce to 0. FE calls it when the player changes the client seed in the provably-fair panel.

Auth: Player session — Authorization: Bearer {token}
Rate limit: 100 requests per 60 s per IP (GAME_SET_CLIENT_SEED)
Games: THAI-HILO, LOTTO

Rules

clientSeed is any non-empty string, stored as sent (no trimming, no length or character rules).

The server seed is not rotated: its hash stays the same, so earlier bets remain under the same commitment.

THAI-HILO: the next single-player bet uses the new clientSeed with nonce 0, and that bet's response has no nonce key.

Both games: the next bet that claims a slot in a MULTI_CSEED room contributes this clientSeed and nonce; rounds already bet in are not affected.

LOTTO: serverSeedHash is always "" (key present) — LOTTO has no per-player server seed.

The response nonce is always 0. For reference, the nonce is 1 on a new or rotated seed and 0 after a client-seed change.

Demo and real play keep separate client seeds.

Flow

Validates the token, checks system maintenance and resolves gameCode.

Rejects an empty clientSeed.

Loads or creates the player's state for this game, sets the clientSeed and resets the nonce to 0.

Returns the (unchanged) server seed hash, the clientSeed and nonce 0.

curl --location 'https://dev-api.ambfairgame.com/gapi/v1/gapi/v1/c/g/THAI-HILO/provably-fair/client-seed' \ --header 'Authorization: Bearer 3f9a1c7e5b2d4f6081a3c5e7f9b1d3f5a7c9e1b3d5f7a9c1e3b5d7f9a1c3e5b7' \ --header 'Accept-Language: th' \ --header 'Content-Type: application/json' \ --data '{ "clientSeed": "my-lucky-seed" }'

{ "code": "0", "description": "Success.", "traceID": "0f8e2c1a-6b3d-4e5f-9a7b-1c2d3e4f5a6b", "data": { "serverSeedHash": "cecfc34e5de06b8028c4cadba0675e8afc6c4f4bf531327c5697c6f3cfa943c0", "clientSeed": "my-lucky-seed", "nonce": 0 } }

Request

Responses