JRGS Casino API

Getting started

The shortest path from a signing key to a player's first round.

This is the order that works. Each step links to the page with the detail.

Make a launch key pair

Generate an Ed25519 key pair on your side. The private key never leaves you; the RGS keeps only the public key.

openssl genpkey -algorithm ed25519 -out launch-key.pem
# The public key as the RGS wants it: the 32 raw bytes, standard base64.
openssl pkey -in launch-key.pem -pubout -outform DER | tail -c 32 | base64

Send us the base64 public key and choose a key id (for example casino-2026-11). With it we register:

  • the scopes the key may use: catalog to list games, launch to start sessions;
  • the networks (CIDRs) your requests come from. A key with no networks is refused from everywhere, so list every egress address of your platform;
  • optionally a validity window (notBefore, notAfter).

The key works as soon as the change reaches the RGS. See Authentication and signing.

Give us your wallet

Your wallet is a service (HTTPS in production) with five POST routes under one base URL, for example https://wallet.casino.example/rgs: /balance, /debit, /credit, /rollback and, optionally, /operations. We register the base URL, a key id that the RGS sends in X-Key-Id, and a shared secret for the HMAC signature in both directions. Agree the secret with us over a secure channel at onboarding. Optionally, a timeout for one call between 1 and 15 seconds (5 seconds if you set none; see Environments and limits).

Implement the wallet

Implement the five routes from the Wallet pages:

Pass the conformance suite

Give us a test wallet: its base URL, key id and secret, three test players (one with funds, one with less than the test amount, one blocked), optionally a fourth whose bets your rules refuse with BET_REJECTED, a currency and an amount. The suite runs real calls against it and stores the result. Until your wallet has a current pass, POST /sessions on a real market is refused with ERR_WALLET_NOT_CERTIFIED. See Conformance and going live.

List your games

Call GET /catalog/games?market=<your market id> with a key that has the catalog scope. Each item gives the game id, RTP variant, bet range per currency in micro-units and a thumbnail. See Launching a game.

Start a session

Call POST /sessions with a key that has the launch scope:

{
  "requestId": "launch-7f3a",
  "marketId": "gb",
  "gameId": "slots",
  "player": { "id": "p-1001", "country": "GB", "currency": "GBP" },
  "lang": "en",
  "device": "desktop"
}

A 201 carries sessionId and launchUrl. See Launching a game.

Open the URL

Send the player's browser to launchUrl exactly as you received it, within 60 seconds: the token in it works once and expires after a minute. If the player did not get there in time, ask for a new URL with POST /sessions/{id}/launch-url. The RGS then calls your wallet as the player plays.

Hostnames of the RGS are issued with your keys; there is no public sandbox today. See Environments and limits.

On this page