Step 1: get access
The client area of WGC is opened personally by a manager, who creates the first login. There is no self-service sign-up. The API description is public from the start, as an OpenAPI file and a documentation page that need no key, so your engineers can read the contract before access arrives. After that you create keys yourself in the back office: test keys for the test mode and production keys for real play.
Step 2: agree on the games
Slot games are issued to your account by your WGC manager, studio by studio, and your platform sees exactly those games. The public provider catalog lists 184 studios, and a studio listed there is not automatically open to every client. Tell your manager which studios you need and which currencies you plan to sell, and readiness is confirmed for each project.
Step 3: load the catalog
Your server asks for the games issued to the account. The first request without a time filter returns the full catalog, 200 games per page, and you store the sync time. Later requests send that time and return only the changes, with a removed flag for games to take down. The changes overlap by the last ten minutes, so write them as an upsert by publicId. Run a full sync at least once a day, because a change in what is issued to your account is learned from a full sync.
Each game has two numbers. The publicId identifies the game in your catalog and is never rewritten. The universalId is the same for the same game across the catalog, and your own database should be keyed on it. Slots have the type slot, and crash games the type fast_games; you can filter the request by type and by currency. See the slot API page.
Step 4: build the lobby from the catalog data
The catalog gives your lobby what it needs: the name, the studio brand, the type, ready-made image addresses in WebP in three proportions (square, portrait and landscape) and the capability flags: demo, free spins, free bets, jackpot, and whether RTP and bet limits can be set. A game lists the countries where its studio does not allow it and the currencies in which it does not open, so your lobby can hide it where it would be refused. The lobby is built on your own platform: WGC has no lobby for your players, and the Games page of the back office is a tool for operators.
Step 5: open a game
When a player picks a game, your server sends the player id, the currency, the mode and the game number, and WGC returns a launch link. The player's browser opens the link, in a frame if you prefer. Demo launches open with a test key and move no money; a real launch needs funds on your commercial account. The details are in the article on the launch link and session.
Step 6: build the wallet handler
This is the one real piece of development, and an aggregator does not remove it. The player's money stays in your casino, and WGC calls your Callback URL for the balance, for a bet with its win and for a rollback. Your handler must verify the signature on the raw body, record a bet once per transaction id and answer within three seconds. Where a studio sends the bet and the result apart, WGC joins them into one round, and the same handler serves every slot of every studio. The contract is on the seamless wallet page, and the idempotency article explains repeated calls.
Step 7: test before real play
Create a test key and open WGC Test Slot, which makes real calls to your Callback URL without money. Then run the integration check and the integration test in the back office, open demo sessions of real slots, and finish with a small real launch. The testing article gives the whole plan, and demo and test mode explains the tools.
Step 8: go live and watch
Walk through the public go-live checklist, which has 14 points, and confirm readiness with your manager. After go-live, the back office shows turnover, wins, GGR, RTP and commission by round, session, player and game, with an export to CSV, and you can search your games by name, brand or number. Keep one full catalog sync a day and look at the reports for the first rounds. The integration steps describe the same path in short.
What you build and what you leave to the platform
| Your team | WGC |
|---|---|
| The lobby and the player accounts | The catalog, with identifiers and images |
| The wallet handler | The session request and the launch link |
| The catalog sync job | Rounds that join a bet and its result |
| Your own geographic checks | Reports, lookups and test tools |
For the difference between connecting studios one by one and through an aggregator, read Casino API vs game aggregator and the game aggregator overview. For the other types of content, see types of casino content.