Casino API integration for gaming platforms

The WGC casino API is a server-to-server interface for operators. Through it your platform receives the game catalog issued to its account, opens games for players, answers wallet calls and reads the status of its own operations. This page summarizes how it works; the steps to go live are on the integration page.

One envelope, one key

Your server calls the API with a key in the X-API-Key header. Every answer uses the same envelope with an ok flag, a request id and either data or an error. Branch your code on the error code only; the message is written for people. The API is not meant for browsers and does not support cross-origin calls.

You create and revoke keys yourself in the back office: up to five production keys and up to two test keys, with the value shown once. A new production key on an account with real traffic starts answering after 30 minutes, or immediately once a second person confirms it.

What is live

The live methods are a health check that needs no key, the games catalog, opening a session, three status lookups by your own numbers (a transaction, a round and a session), a lookup of sessions by your own session id, win limits and the wallet calls that WGC makes to your platform. The machine-readable description is an OpenAPI 3.1 file that opens without a key, and the readable description is a public documentation page. If they differ, the file is right.

Games and sessions

The games request returns the games issued to your account, 200 per page, each with a publicId, a universalId, a type, an image address and capability flags. After a first full download you ask only for changes by sending the time of your last sync. See the game aggregator overview and the slot API for catalog details.

A session request needs the player id, the currency, the mode (real or demo) and one game number. You may add the language, a return address, the platform, the player's country, your own session id and, for games that accept them, an RTP from 75 to 96 and bet limits. An idempotency key, valid for 24 hours, returns the same answer for the same request, and a repeated open of the same player and game returns the same session while it is open.

Wallet and status lookups

Player balances stay with your platform. WGC calls your Callback URL with signed requests for the balance, for a bet and its win, and for a rollback; the contract is described in seamless wallet integration. Afterwards you can read the status of an operation, a round or a session by your own numbers. The log of your API requests is kept for 90 days.

Free spins

Free spins for a player can be issued through the API, but the feature is off by default and is switched on at your request. It does not work for every game, and the bonus is paid for as a bet. Ask your manager whether it fits your project.

Win limits and RTP

Win limits can be read and changed through the API with the proper right, and in the back office you set stop lines for suspicious wins: one win, a player's wins in an hour and an account's wins in an hour, within the boundaries of the platform. RTP and bet limits for a launch are set in the request or in the back office, for games that support them.

Limits and stability

By default a key can open 600 games a minute, and the catalog and status requests allow 120 a minute. Bursts from one address are limited, and an excess gets a rate-limit answer with a wait time. Your manager can raise the limits of an account. On request, calls of your account can also be restricted to a list of addresses, up to 50 entries.

A version of the API does not break without notice. New fields may appear, so ignore fields you do not know. A field is removed or changes its meaning only after a deprecation notice and not earlier than 90 days later. An incompatible change would be a new version, and the current one keeps working next to it.

Try it first

A test key opens a test game that makes real calls to your Callback URL, without money. See demo and test mode, currencies for currency rules, and the integration steps.

FAQ

Is there a public API description?

Yes: an OpenAPI 3.1 file and a documentation page, both open without a key.

Can I call the API from a browser?

No. It is a server-to-server API.

How do I get a key?

You create it in the back office, which your manager opens for you.

Ready to integrate? 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