Getting started

Overview

The platform is a slots game server for casino operators. Your casino keeps the player accounts and the money; the platform runs the games and asks your wallet to debit and credit every round (a seamless wallet).

What you get#

Capability	Where it is described
Launch any published game for a player and get a ready-to-open link	Game launch
Seamless wallet: balance, debit (`bet`), credit (`win`), round notifications	Wallet callbacks
Embed the game in an iframe on your site	Embedding
Public catalog with per-game languages and capabilities	Catalog and capabilities, Games list
All 157 ISO 4217 fiat currencies	Currencies
47 launch languages in the catalog, chosen per launch	Languages
Operator free spins with a per-grant summary callback	Free spins
Scheduled target outcomes for a chosen paid spin	Target outcomes
Project, game and player bet limits; extended bets above a game's native maximum	Bet limits
Personal RTP 60–100 % per player	RTP management
Free-play demo mode that never touches your wallet	Demo mode
Admin panel for your staff	Admin panel

The catalog#

The catalog currently holds 1010 games from three provider families. The provider id is used in the admin panel and in some API fields.

Provider	Provider id	Games	Free spins	Target outcomes
Endorphina	`endorphina`	235	235	225
Pragmatic Play	`pragmatic`	659	659	634
Nolimit City	`nolimitcity`	116	115	115

Games are identified by a stable string id (for example gates-of-olympus); see the games list for every id, its languages and features. The numbers above come from the catalog snapshot of 2026-11-10.

TEST_ONLY mode#

The platform is a test and demonstration environment:

the units played are non-withdrawable: nothing in the API moves real money;
POST /playGame.do accepts gametype: "demo" (real-wallet mode, played against your wallet) and gametype: "fun" (demo mode, free play); any other value is answered with REAL_MODE_DISABLED;
GET /capabilities and GET /health report "mode": "TEST_ONLY" (/games/health and /games/catalog carry no mode field).

Your wallet can still be a real service that holds your own balances; the platform only calls it according to the wallet contract.

How an integration works#

Operator server                      Platform                         Player browser
      |   POST /playGame.do  ----------->|                                  |
      |   <-- {link, session_id} --------|                                  |
      |   give the link to the player ------------------------------------>|
      |                                  |<---------- plays the game -------|
      |<-- POST <callback>/EUR session_info (at launch)                     |
      |<-- POST <callback>/EUR bet (before each paid round)                 |
      |<-- POST <callback>/EUR round_info start                             |
      |<-- POST <callback>/EUR win (when the round pays)                    |
      |<-- POST <callback>/EUR round_info finish                            |

Your server calls the launch method with the player id, currency and game id.
The platform asks your wallet for the balance (session_info), creates a session and returns a link.
The player opens the link and plays. For every paid round the platform calls your wallet: first bet, then win if the round pays, plus round_info notifications.
Optional server calls: free spins, target outcomes, round cancel and reports via /gameActions.do, personal RTP and bet limits via /playerRtp.do.

Who uses what#

Developers: Quick start, Authentication, Conventions, Wallet callbacks, API reference.
Back-office and support staff: the admin panel guide, free spins, target outcomes, the FAQ.