Connect once.
Start playing.

Configure your casino

Your administrator creates a casino connection and assigns it to your account. Open API & integration to set your HTTPS callback URL and generate a secret key. Keep the secret on your server.

Resolve a player session

Provide your casino's public key, an opaque player session token, and a registered game slug. The session token must identify the player in your system.

POST https://api.polarisgames.org/casino/session
Content-Type: application/json

{
  "publicKey": "your-public-key",
  "token": "your-player-session-token",
  "game": "game-slug"
}

Respond to wallet callbacks

Polaris sends POST requests to your callback with Authorization: Secret <secret-key>. Validate this header before processing requests. For action: "session::info", return your player's wallet information in the response envelope:

{
  "response": {
    "user_id": "player-123",
    "display_name": "Player",
    "currency": "EUR",
    "balance": 100,
    "balance_type": "main"
  }
}

For action: "transaction", process eventId idempotently, use direction to debit or credit the wallet, and return the updated session information. Reject insufficient funds without changing the wallet.

Validate in staging

Check session loading, balance changes, repeated transaction IDs, and callback failures before your production rollout. Ask your platform administrator for the game launch URL and the catalogue available to your casino.