Onboarding
From early-access request to sandbox access, Groups and Operators and production go-live, for Providers and Operators.
On this page
We are onboarding two kinds of Partner: pilot Providers (game integration) and pilot Operators (casino integration). The path is the same; the details differ where marked.
How to read it: follow the arrows from the early-access request (top left) along the first row, then continue on the second row to the go-live step.
1. Agreement and checks
We run know-your-business and sanctions checks on every Partner and, for a Provider, on every Operator it wants to connect. The agreement includes the responsibilities in the Go-live checklist chapter. Commercial terms differ by Partner kind.
2. Sandbox
You receive:
- a key id and secret for the sandbox (the secret is shown once; store it in your secrets manager). The sandbox is a completely separate environment with its own servers and data: its keys work only there, and your production keys are made on the production Site, so a test key never reaches production;
- a test Operator with all three Extra Games, EUR and GBP bet ladders, and a Compliance Profile that allows demo;
- test hooks that let you force outcomes (a jackpot hit, a Reel Triple Minor, a timeout) so you can test every display and money path. Test hooks exist only in the sandbox.
Game integration: the test Operator is op-sandbox-<you>, linked to your Provider account.
Casino integration: the casino sandbox gives your Operator Partner its own test Operator, with the same games and ladders. You test the overlay and your trigger rule against it.
3. Groups and Operators
For production, we set up your tree: your Partner, its Groups (a default Group is created for you) and the Operators in them. Each Operator
belongs to exactly one Group and so to exactly one Partner, and has the operator code you send as operatorId.
- Provider: one Operator for each casino you serve.
- Operator Partner: your own Operator, or several if you run several brands.
For each Operator we configure:
- the Extra Games it offers and the Game Variant (RTP) for each;
- the base bet for each game (the price of level 1), the levels it offers (which may have gaps), the currencies it offers (every enabled currency except any we exclude for it) and the fixed factor of each currency; together they set the price of every offered level (read the offered levels and their prices with
GET /v1/partner/games/{gameId}/levels); - the jackpot pool ownership (Operator, Group or Network);
- the reveal mode:
1immediately (casino default) or2when the Partner callsreveal()(game default), plus for mode2the safety timeout if you never call it (1 to 3 seconds, default 2); - widget level control (casino integration): whether the widget shows a level picker (− and +) for your players (off by default). It is a setting of your Operator, not an SDK option; the picker is advisory, so your backend still decides the level of every play. The on/off switch is always shown and is not advisory: ReelXtra enforces it. Also tell us whether new players start on (the default) or off (the Operator's starts-on setting);
- the Compliance Profile (demo allowed, minimum round interval, display rules, maximum win). It is a profile of your Operator's own Domain and of its own jurisdiction, or one with no jurisdiction; without a choice the Domain's default profile applies;
- the Domain (Open, Regulated or White label) your Partner and its Operators belong to. We set it at onboarding and it never changes. Your Partner, its Groups and every Operator in them are in the same Domain. A casino active in two Domains is onboarded once in each, with its own keys. The API has no Domain field: nothing in a request names it.
4. Keys
- Keys are per environment and per licensed site.
- Rotation: we issue a second key while the first stays valid for an overlap window; switch, then confirm, and the old key is retired.
- Emergency revoke: tell us immediately if a key may be compromised. Revocation takes effect within seconds.
- IP allowlist (recommended): give us the egress IPs of your backend. Requests from other IPs are refused.
5. Origins (widget)
There is nothing to register: the widget can be shown on any page or domain you run. Because the widget is served
from the same host as the Partner API, the Site has one origin for you to allow in your own Content Security
Policy (for example https://sandbox.reelxtra.net). The widget only shows results and never sends a bet, so
your backend still decides every play.
6. Certification run
Before production keys are issued you run the scripted scenarios in the sandbox and we check the results in our logs with you.
- Both streams: normal plays, jackpot hit, retries, cancel, carried-over bonus, session replacement, errors, relaunch.
- Game integration: reveal timing with your reels.
- Casino integration: your trigger rule,
roundTooSoonhandling (skip the play before debiting), refund on rejection, andoperatorIdhandling.
Pilots run first on Operators in the Open Domain (or an already-cleared jurisdiction): see Compliance.