A unique identifier associated with operator calling API.
A SHA256 HMAC signature generated using the request body and timestamp.
Format: HMAC_SHA256(JSON.stringify(data) + ’|’ + timestamp), signed using the
provided secret key.
An Unix timestamp (milliseconds) Used to verify the request’s freshness.
Ensure the same value is used in signature generation.The signature will remain valid for only 5 minutes from the provided
timestamp.
Must be set to application/json.
Request Body
A unique identifier representing the specific game being requested.
A unique identifier for the player initiating the game session.
If an old playerId is sent, it must be a valid playerId and is case-sensitive.
The player name that is initiating the game session.
The player’s current balance available for the game session.To maintain precision and avoid floating-point errors, the balance field is
processed as an integer value by multiplying the actual amount by 100,000.
For example, a balance of 12.34567 will be represented as 1234567 in the
API.
An identifier for the currency associated with the player’s balance.
See the list of supported currencies here.To generate a session in demo mode, you must pass the currency as “XXX” in
the request payload.
Response
Code indicates status of the request weather it is succeed or failed. We have listed error codes
here
The URL to access the game.
A sessionId is identifier for the game session.
This is the expected response from a successful Launch Game request.