Environments and limits
Where the RGS runs, the timeouts and sizes both sides must respect, and the wallet latency we require.
Environments
Hostnames are issued at onboarding, together with your keys and market ids. This site does not publish them, and
examples use placeholders such as https://rgs.example.com. Every path, field and signature rule is the same in every
environment.
There is no public sandbox today. Our own development runs in a local cluster with a simulated casino, a mock wallet and demo markets, which casinos cannot reach. What a casino gets before going live is:
- the conformance suite, which we run against a test wallet you provide (its own base URL, key id and secret, and test players), and which moves real balances on it, so use test players only;
- until your wallet passes the conformance suite, your real markets take no new sessions. Whether you can try the launch flow on a market before then is agreed at onboarding; ask us.
Ask us during onboarding which hosts and markets you have.
Limits on the launch API
| Limit | Beyond it | |
|---|---|---|
| Request body | 1 MiB | 400 ERR_VAL, reason body |
Clock skew of X-Timestamp | ±60 s from the RGS clock | 401 ERR_ATE, reason timestamp |
| Catalog page | 1 to 200 games, 200 by default | 400 ERR_VAL, reason limit |
| Launch token | single use, 60 s | the game client cannot open the session; ask for a new URL |
Rate limits
The RGS enforces no request rate limit today: there is no 429 and no rate-limit header. That is not an
invitation to poll. Cache the catalog and revalidate it with If-None-Match (a 304 costs almost nothing), create a
session only when a player opens a game, and retry a 500 with a growing delay.
Limits on wallet calls
| Limit | |
|---|---|
Clock skew of your response's X-Timestamp | ±60 s from the RGS clock |
| Response body | the RGS reads at most 1 MiB; a longer body fails its signature check and counts as an unknown outcome |
reason in an error answer | 64 bytes; longer is cut |
message in an error answer | 512 bytes; longer is cut |
details in an error answer | 16 string entries, keys up to 64 bytes, values up to 256 bytes; the rest is dropped |
Control characters in these fields are replaced by spaces. See Errors and money states for what the fields mean.
Wallet timeouts
Each call to your wallet has a timeout. You choose it per casino, from 1 to 15 seconds; without a choice it is 5 seconds. A call that runs out of time has an unknown outcome: a debit is then rolled back, and a credit or rollback is repeated until it gets a final answer (see Retries, idempotency and reconciliation). The timeout is a ceiling for bad moments, not a target.
Wallet latency
Requirement: p99 debit latency under 2 seconds
The player waits for every debit: a bet does not play until your wallet has answered it. The p99 of your debits, measured over 5-minute windows, must stay under 2 seconds. We measure from our engine, so the time includes the network between us.
We measure the duration of every wallet call, by casino, operation and outcome, and keep each round's wallet time in its journal record, so a slow period can be reported round by round. Two alerts watch your wallet:
- WalletSlow: the p99 of your debits, over 5-minute windows, stays above 2 s for 10 minutes. This is the requirement above; it alerts our operators.
- WalletTimeoutShare: more than 5 % of your wallet calls time out, sustained for 5 minutes, while traffic is at least about 6 calls a minute. This pages our engineers, because debits that time out are rolled back.
Answer credits and rollbacks as fast as debits: they are not on the player's screen, but a slow one keeps the round unsettled for longer.