Slot games API for casino platforms

Slots are one of three sections of the WGC catalog, next to live dealers and sport. Your casino platform lists and opens slot games through the same API it uses for every other game type (see the Casino API overview), and your players' balances stay on your side. This page describes what the slot integration looks like for a technical team.

Slots in the WGC catalog

The provider catalog lists 184 studios, and the slots section also holds crash games, RNG table games and lotteries. In the API, a game has a type. Slot games use slot, and crash and similar quick games use fast_games. You can filter the games request by type and, if you need only games that cover your currency, by currency.

The request returns the games issued to your account, 200 per page. Each game has a publicId that never changes and identifies the game in your catalog, and a universalId that is the same for the same game across the catalog. For each game you also receive a name, a studio, ready-made image addresses in WebP and its capability flags.

Crash and other fast games

Crash games arrive as the fast_games type and are opened exactly like slots: the same session request, the same launch link and the same wallet calls. Nothing in your integration changes for them, apart from the game number you send. Whether a crash game supports demo, free spins, jackpot or RTP settings is stated in its own capability flags, not assumed from its type.

Opening a slot for a player

Your server asks WGC to open a game with the player id, the currency, the mode and the game number. Optional fields set the language, the platform (desktop or mobile), the player's country, your own session id and a return address. WGC answers with a launch link that the player's browser opens, in a frame if you prefer.

An unknown language falls back to English and never causes a refusal, while a launch from a known restricted country does. A game that is unavailable in a currency is marked in the catalog, and a launch in that currency is refused at once while the other currencies keep working.

RTP and bet limits per launch

For games that support it, you can pass an RTP and a bet range with the launch request. RTP is a whole number from 75 to 96, and the minimum and maximum bet are amounts in the game's currency. The value in the request wins over the brand setting, and the brand setting wins over the setting for all brands.

Not every game accepts these values. The catalog flags rtpSettable and betLimitsSettable tell you which do, and the launch answer states what was actually passed to the studio. A game that does not accept the values is still opened. A chosen RTP is a setting handed to the studio, not a result to expect from a single session.

Wallet calls for slot rounds

Slots use the seamless wallet model. When a spin is played, WGC calls your Callback URL, and a bet with its win can travel in a single call. If a studio sends the bet and the result separately, WGC joins them into one round with a round id. Round actions are described in plain WGC words such as bet, bonus buy, free spins, respin and win, instead of raw studio fields.

Test before you go live

A test key opens WGC Test Slot, a game that makes real calls to your Callback URL without money, without commission and without ledger entries. Use it with the integration check in the backoffice, then move to real games. The steps are on the integration page, and the demo and test mode page explains the details. For tables with dealers, read the live casino API page.

FAQ

Are crash games part of the slot API?

Yes. They are a separate game type in the same catalog and are opened with the same requests.

Can I set RTP for every slot?

Only for games that accept it. The catalog flags show which ones do.

Do I need a different wallet integration for slots?

No. One Callback handles all game types.

How do I know a game can run in my currency?

Each game lists the currencies in which it is unavailable, and the catalog can be filtered by currency.

Ready to add slots to your platform? Let's talk about your integration.

Your next connection
starts here.

Tell us what you’re building. We’ll take it from there.

Let’s connect