Live casino API for operators

Live dealer games are one of three sections of the WGC catalog, next to slots and sport. For your platform they are opened and paid through the same API as every other game type, so a team that has integrated slots (see the slot API) has already built most of what live casino needs. The whole interface is summarized in the Casino API overview. Player balances stay with your casino.

Live dealer games in the catalog

The provider catalog lists 184 studios, with a separate live dealers section. In the API, live games carry the type live_dealers. A request for games can be filtered by this type, and by your currency, and returns the games issued to your account: 200 per page, each with a stable publicId, a universalId, an image address and its capability flags.

The games of a studio are issued to your account by your WGC manager. A studio listed in the directory is not automatically open for every client.

Opening a live table

Your server asks WGC to open a game for a player with the player id, the currency, the mode and the game number. You can add the platform (desktop or mobile), the player's country, the language and your own session id. WGC answers with a launch link for the player's browser.

An unopened link works for five minutes. Once opened, it works while the player is active, and after the session closes it answers with a clear page instead of an error. The link can be placed in a frame; use allow="fullscreen; autoplay" on the frame. A return address brings the player back to your lobby, but not every game accepts one, so give players a way out of the frame on your own page.

Restrictions you should expect

Each game lists restricted countries, and a launch from a known restricted country is refused. If the country cannot be determined, the game opens, so keep your own geographic check. A game that is unavailable in a currency is marked in the catalog, and a launch in that currency is refused while other currencies keep working.

Wallet calls during live rounds

Live games use the seamless wallet model: WGC calls your Callback URL to read the balance and to record bets and wins. A bet and its win can arrive in one call. When a studio reports them separately, WGC joins them into one round with a round id.

Your answer is expected within three seconds. If it is not received in time, the bet is refused to the studio, the operation is marked unknown and WGC later asks you to cancel it with a rollback. A bet that waited inside WGC for more than a second and a half is never sent to you at all, so nothing is debited from the player. Repeated calls are recorded once per transaction id.

Looking up a round

After the round, your platform can ask for an operation, a round or a session by your own numbers. A round reports bet, win and the difference. Lookups cover the last 65 days; older events move to an archive that WGC searches on request. Round actions use plain WGC words, and the list is open: treat an unknown code as information and do not branch money on it.

Test before you go live

Opening a game in demo mode with a test key does not move money. The WGC Test Slot makes real calls to your Callback URL, so you can verify signatures, answers and rollback before real play. The full path is described on the integration page and in demo and test mode.

FAQ

Which API type do live dealer games use?

live_dealers. You can filter the games request by it.

Do live games need a different wallet integration?

No. They use the same Callback as slots.

Can I put a live game in a frame?

Yes. The launch link can be placed in a frame; provide your own exit for games that ignore the return address.

What happens if my wallet answers late?

The bet is refused to the studio and the operation is cancelled with a rollback.

Planning live content? 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