Casino API integration steps

Work through your requirements, data and wallet flow with WGC. A shared plan makes the next step clear for both teams.

  1. 1

    Align the scope

    Tell us about your platform, target content, account structure and existing wallet. We agree on what the integration needs to cover.

  2. 2

    Map the content

    Align provider labels and studio names with the WGC catalog. Review ambiguous matches while preserving each provider offer and its game identifier.

  3. 3

    Verify the flow

    Check the contract, authentication, error handling and repeated transactions in a test environment before real traffic.

  4. 4

    Agree on launch

    Confirm availability, terms and readiness together. A launch date follows completed validation, not a generic promise.

An integration with WGC is a short sequence: get access, create keys, load the catalog, open a game, answer wallet calls, test, and go live. Each step has a tool or a document behind it, so a team can move without waiting for a call. This page puts the steps in order.

1. Get access

The client area 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: an OpenAPI file and a documentation page that need no key, so your engineers can read the contract before access arrives.

2. Create keys

In the back office, under Settings, Integration, you create and revoke keys yourself: up to two test keys and up to five production keys. The value of a key is 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. The Casino API overview lists the endpoints.

3. Load the catalog

Request the games issued to your account. The first call without a time filter returns the full catalog, and you store the sync time. Later calls send that time and return only the changes, with a removed flag for games to take down. Key your database on the universal number of a game. More in the game aggregator overview.

4. Open a game

Your server sends the player id, the currency, the mode and a game number, and receives a launch link for the player's browser. A demo session opens with a test key and moves no money. A session in real mode needs funds on your commercial account: the balance plus the credit limit must be above zero.

5. Build the wallet handler

Player balances stay with your platform. 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. Rollbacks are repeated for up to 30 days, so keep records of operations for at least that long. The contract is in seamless wallet integration, and see security for how access is protected.

6. Test

Test mode gives you a test key and a test game, WGC Test Slot. Each spin makes two real calls to your Callback URL, a bet and a result, without money, commission or ledger entries. An option to lose the answer checks that your rollback works. Public examples in Node.js, PHP and Python, a check script and a go-live checklist of 14 points need no sign-in.

In the back office, the integration check runs a real game of your account through your wallet, with a live log of every call, and the integration test runs 14 checks and tells you what to fix. Details are in demo and test mode.

7. Go live

Before you switch to production keys, walk through the go-live checklist. Readiness of each project is confirmed with your manager. After go-live, the back office shows the health of the integration on its first screen, with reports, alerts and balances; see the back office.

Help while you work

Ask WGC is the assistant in the back office. It answers from the documentation with sources and knows the rights of your account. In integration mode, with the proper right, it reads a limited snapshot of your own integration from the last seven days, without secrets or request bodies, and explains why your calls fail. Live support is also inside the back office; when you write to it, quote the request id, transaction id, round id and the time in UTC.

FAQ

Do I need to read the documentation before I get access?

It is public, so yes, you can read it at any time. It includes an OpenAPI file.

Can I test without a real game?

Yes. A test key opens WGC Test Slot without money.

How long does a new production key take?

On an account with real traffic, 30 minutes, or immediately after a second person confirms it.

Is there a checklist?

Yes. The public go-live checklist has 14 points.

Ready to plan your integration? 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