Skip to main content
Games are referenced everywhere by their slug — a stable, human-readable identifier such as lucky-duck. Slugs appear in launch URLs, in every wallet callback as gameId, and in free round campaigns.
The table below is a snapshot. The authoritative list for your account — including availability, languages and country restrictions — comes from List games. Never hardcode the catalogue.

Current games

Game types

gameType in the API tells you how a game behaves, which is what you need to group and filter a lobby.

crash-multiplier-single

Single player, Aviator-like: a multiplier climbs, the player cashes out before it crashes.

crash-multiplier-multi

The same, played by everyone on a shared round. Adds chat and a live bet list.

crash-single

Single player instant game — plinko, dice and similar. Bet, resolve, repeat.

crash-multi

Multiplayer instant game, such as multiplayer roulette.

table-game

Blackjack, baccarat, poker.
Multiplayer types share a round across players, so they also share surfaces such as chat. If several brands sit behind one integration, return subOperatorId from your Player authorization callback to keep those surfaces separate per brand.

Reading the games list

Keeping it in sync

Poll on a schedule

Every few minutes is plenty. The catalogue is not a hot path — do not fetch it while rendering a lobby page.

Send If-None-Match

Store the ETag next to your cached copy and send it back. Unchanged catalogues cost you a 304 instead of the full payload. See Caching.

Reconcile, do not replace

A slug that disappears means the game is no longer provisioned for you. Keep your historical rows — old rounds still reference that gameId in reporting.