An API is the interface

An API defines how one system asks another for information or an action. For a casino platform that may mean requesting a game catalog, opening a session or answering a wallet call. The contract has to specify authentication, identifiers, required fields, errors and retry behaviour.

The WGC API is a server-to-server interface: your server calls it with a key in the X-API-Key header, and every answer arrives in the same envelope with a request id and either data or an error. Its description is public, as an OpenAPI file and a documentation page.

Having an API tells you how to communicate. It does not, by itself, tell you how many studios you can reach or which content is available to your account.

Aggregation is the service behind the interface

An aggregator brings content from many studios into a common integration and operational model. Its work can include a shared catalog, control of which account sees which games, an account structure for partners and clients, reports and support during the connection. The exact scope differs from one service to another.

So ask what is included instead of assuming. The word aggregator does not automatically cover your player accounts, payments, risk tools or every studio in a public directory. With WGC, for example, the directory lists 184 studios, but the games issued to your account are decided by your manager.

Compare the work your team will own

With separate connections to providers, your engineers maintain the individual contracts and their differences. With an aggregator, you work against its shared contract for the supported flows, while still checking the behaviour of individual games. Compare these items:

  • Catalog synchronization: how you get the first full list and then the changes. WGC returns 200 games per page, and after the first download you ask only for changes with the time of your last sync.
  • Game identifiers: one number for the game in your catalog and one for the same game across the catalog.
  • Launch parameters: WGC needs the player id, the currency, the mode and a game number, and returns a launch link.
  • Wallet messages: which calls you answer and how.
  • Support ownership: who helps when something fails.

A smaller first integration helps only if your team can also diagnose errors afterwards.

A game name is not an identifier

Similar game names are not enough to identify the same game. That is why WGC gives each game a stable publicId and a universalId that is the same for the same game across the catalog. Names are for display, and identifiers are for matching. For your launch list, confirm the actual games available to your account and which currencies and countries each game supports, and check commercial terms separately from the brand that the lobby displays.

Questions to bring to a technical review

Use these questions with any aggregator.

  1. Keys. How are revoked credentials handled? With WGC, you create and revoke keys yourself in the back office, with up to five production keys and up to two test keys.
  2. Empty grants. What happens when no games are issued to the account? In WGC, the answer is a successful empty list, not an error.
  3. Catalog changes. How are changes exposed? WGC returns only changes after the time of your last sync, and recommends a full sync at least once a day.
  4. Safe retries. Which operations are safe to retry? An idempotency key, valid for 24 hours, returns the same answer for the same session request, and a repeated open of the same player and game returns the same session while it is open.
  5. Errors. Can you get an example of an error with a support reference? Every answer carries a request id.
  6. The wallet. Establish transaction identity, duplicate handling, timeouts and reconciliation before real traffic. In WGC a bet is recorded once per transaction id, and WGC waits three seconds for your answer.

How this applies to WGC

World Gaming Connect combines a B2B back office with catalog access, session opening and the wallet Callback. For operational control there is an account tree, with team permissions, and a commercial balance in USD. Support is part of the picture: Ask WGC answers from the documentation, and live support works inside the back office.

The next step is to agree on your content scope and test plan with the team; a test key opens a test game without money. Readiness of each project is confirmed separately, so this article does not imply that every listed studio or flow is ready for your project. For the technical details, see the Casino API overview, and for the service itself the game aggregator page, the provider catalog and the integration steps.