Demo and test mode for your casino API integration

You should be able to test an integration before any real money is involved. WGC gives operators three tools for that: a test mode with its own keys and a test game, demo launches of real games, and checks inside the backoffice that show what your platform did. This page describes how they fit together.

Test keys and the test game

You create test keys yourself in the backoffice, under Settings, Integration. An account can have up to two. Their value is shown once, so store it when you create it. A test key opens one game, WGC Test Slot: a page with three bet sizes and a Spin button.

Each spin makes two real calls to your Callback URL, a bet and then a result, marked with a test flag and a test header, so your handler can tell them apart from real play. No money moves, no commission is charged and no ledger entries are made. The test rows appear in the Test tab of the reports. Limits apply: two spins per second for a session and 2,000 spins a day for an account.

Demo launches of real games

A game session can be opened in demo mode. Demo does not move money and is not refused for lack of balance, and it opens only with a test key; a production key opens only games for money. Games that support demo say so in their demoSupported field and in their capability flags, so you can show a demo button only where it works. WGC also runs a demo lobby at its own address. The catalog is described in the game aggregator overview, and slot details are in the slot API page.

Test the failure path

A wallet integration is defined by how it fails. The test page has an option to lose the answer: the operation becomes unknown and, after about a minute, a rollback with an unknown-outcome reason arrives at your Callback URL. This lets you confirm that your handler cancels a bet once and that a repeated rollback is harmless. Read more about the contract in seamless wallet integration.

Checks in the backoffice

The backoffice has two tools that go beyond the test game:

  • Integration check runs a real game of your own account through your own wallet. It shows a live log of the launch and of every getBalance, writeBet and rollback call, with request and answer, and a tab for signatures.
  • Integration test runs 14 checks of your wallet and gives a verdict, with a hint on what to fix.

Both are described with the other tools of the backoffice.

Public examples

Handlers for the Callback, a self-check script and a go-live checklist are public and need no sign-in. They cover Node.js, PHP and Python, and the checklist has 14 points. The API description is public as an OpenAPI file and as a documentation page. Both open without a key.

Help while you test

Ask WGC, the assistant inside the backoffice, answers from the documentation with sources. With the integration right enabled, its integration mode reads a limited snapshot of your own integration from the last seven days: key prefixes, recent calls, sessions and wallet calls with error codes and durations. It does not see secrets or request bodies, and it explains why your calls fail.

The path from test to production

  1. Create a test key and open WGC Test Slot.
  2. Verify signatures, answers and the rollback path.
  3. Run the integration check and the integration test.
  4. Open demo sessions of real games.
  5. Move to real games with a production key.

The full sequence is on the integration page. For the endpoints, read the Casino API overview.

FAQ

Does the test mode cost anything?

No money moves, no commission is charged and no ledger entries are made.

How many test keys can I have?

Up to two.

Can I open a demo of real games?

Yes, in demo mode with a test key, for games that support demo.

Is there a self-check tool?

Yes: a public check script, example handlers and a go-live checklist.

Ready to try it? 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