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
Public catalog with per-game languages and capabilities	Catalog and capabilities, Games list
43 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 and an adaptive rule	RTP management
Admin panel for your staff	Admin panel

The catalog#

The catalog currently holds 446 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`	138	138	136
Nolimit City	`nolimitcity`	73	72	72

Game logic and mathematics are provided by the platform. 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-10-14.

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 only gametype: "demo"; anything else is answered with REAL_MODE_DISABLED;
public endpoints report "mode": "TEST_ONLY".

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>/UAH session_info (at launch)                      |
      |<-- POST <callback>/UAH bet (before each paid round)                  |
      |<-- POST <callback>/UAH round_info start                              |
      |<-- POST <callback>/UAH win (when the round pays)                     |
      |<-- POST <callback>/UAH 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 and target outcomes via /gameActions.do, personal RTP 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 and target outcomes screens, the FAQ.