Quick start

The shortest path from credentials to a first real round in the sandbox.

1
Receive sandbox credentials
Your account manager issues a key_id and a secret. See Credentials.
2
Give us your wallet URL
One HTTPS URL on your side; the action travels in the body. If it sits behind an allow-list, admit the address we call from, listed in the Operator Portal under Credentials.
3
Call GET /v1/ping
Proves your signature and your clock. server_time should be within seconds of yours.
4
Fetch the catalogue: GET /v1/games
Page through with next_cursor and cache the result. Store each game's id.
5
Create a session: POST /v1/sessions
Send player_id, currency and the catalogue game_id; open the game at launch_url.
6
Implement the wallet
getbalance, bet, win, rollback, idempotent on transaction_id. Answer balances as strings.
7
Verify transactions and rounds
Look up a few of your test movements with GET /v1/transactions/{id} and GET /v1/rounds/{id}.
8
Complete the go-live checklist
We compare your test rounds with our journal and issue production credentials.

Your first call

curl

KEY_ID=ak_5f2c9e01a34b7d8e2f0c1b6a
SECRET=…                               # sandbox secret; never in a URL or a log
TS=$(date +%s)
SIG=$(printf '%s.%s' "$TS" 'GET /v1/ping' | openssl dgst -sha256 -hmac "$SECRET" -hex | awk '{print $2}')
curl https://sandbox-api.example.com/v1/ping \
  -H "X-Agg-Key-Id: $KEY_ID" -H "X-Agg-Timestamp: $TS" -H "X-Agg-Signature: $SIG"

Prefer a client? Import the Postman collection and the sandbox environment; the collection signs every request for you.