Agent onboarding
Each operator site gets its own agent ID and configuration during onboarding.
Operator
Player authentication
& wallet callbacks
3i RGS
Game launch
& session handling
Player
Game client
& gameplay
One connected
game experience.
A player session starts with a launch request. Our RGS calls your auth endpoint for the token and balance, sends bet calls to debit stakes and pay wins, and sends cancelBet to roll back any bet that gets no response. Full specifications are shared during onboarding.
Token-based launch
The launch endpoint checks the player token and returns a single-use game URL.
Seamless wallet
You keep the balance. Implement three endpoints: auth, bet and cancelBet.
Session controls
Disconnect one player, or every player in a game, through the API.
Sandbox first.
Then production.
01
Sandbox
Full test environment with test agent credentials, so your team can validate every wallet call before launch.
02
Production
Production credentials are issued after the sandbox integration passes review.
Built for technical teams.
Request the full integration manual and talk through requirements with our engineers.
Integration
at a glance.
What integration model does 3i Studio use?
A seamless-wallet model. The operator keeps the player balance, and the 3i Studio RGS calls the operator auth, bet and cancelBet endpoints.
Which endpoints must an operator build?
Three: auth (validate the token and return the balance), bet (debit the stake and credit wins) and cancelBet (roll back a bet). Other endpoints are optional.
How are games launched?
The operator sends the player token, game ID and language to the launch endpoint. The RGS returns a single-use launch URL.
Is there a sandbox?
Yes. Every partner integrates in a sandbox first. Production credentials follow after the integration is approved.
Where is the full API specification?
The full manual is confidential. Approved partners receive it through a controlled document-sharing process.