Launching your first operation

You are launching a casino operation, and game content is one workstream among several. This page separates the work honestly: what only you can bring, what the integration with Aggregator.gg closes for you, and the order to do it in. If any term here is unfamiliar, start one page back at How the iGaming supply chain works.

What you bring

Four things have to exist on your side; no aggregator supplies them:

• A licence. You need a licence for the jurisdiction where you operate. Which jurisdiction and which licence is a question for your counsel; it is not an integration step, and nothing on this hub answers it.
• Payments. Agreements with payment providers so players can deposit and withdraw. The wallet those deposits fund is the wallet game rounds will settle against.
• KYC and AML processes. You verify who your players are and watch how money moves through their accounts. The obligations come with your licence; the tooling and the process are yours.
• A site or app with a player wallet. The storefront players visit and the account that holds each player’s balance. The integration plugs games into that wallet; it never holds the money itself.

The technical prerequisites next to these are small: Before you start lists them, and a server that can receive HTTPS callbacks is the heart of it.

What the integration covers

One integration with Aggregator.gg closes the game-content workstream:

• A catalog across studios behind one key. Games from many providers through one API, with one agg_ key created in the cabinet. Adding a studio’s games later means enabling them, not building a new integration; Operators lists the full surface.
• One production environment. New operator onboarding uses the production API without new test-key issuance. Existing legacy credentials and assisted provider staging have separate boundaries; do not treat a new live key as a sandbox.
• Controlled integration tests. Verify game access, available credits and spending limits before a wallet test. A welcome grant may help if present; it is not a universal free sandbox.
• Demo sessions. Game launches with no wallet involvement at all, for previews, lobby thumbnails, and UI checks.
• Public documentation with checks. The six-step track, where every step ends with a check you can run, and the go-live checklist before real traffic.

Content is billed as prepaid spin packages your traffic draws down; How billing works covers the mechanics.

From registration to first bets

The order that works:

1. Confirm your path. Choose your integration path sorts the three groups. A casino with its own wallet and players follows the operator path; several brands under one roof start at Platforms.
2. Register. Create the operator account in the cabinet and start KYB in parallel. Business verification is not a technical precondition: it blocks neither key creation nor the six-step track. It is a commercial and compliance requirement of working with us, so start it on day one rather than in the week you launch.
3. Create your API key. Store it in an environment variable, never in code: API keys.
4. Walk the six-step track. Getting started takes you from the key to a settled real-money round within a confirmed test budget, each step with its check.
5. Close the go-live checklist. Go live is the pre-launch pass over money handling, security, and operations. After it, open real traffic.

First bets from real players settle through the same callback endpoint you proved within a confirmed test budget; nothing changes shape at launch.

When to write to us

The operator path is self-serve, so most days you will not need us. Write when something on the platform side blocks you:

• An error whose reference entry says to contact support, or a persistent E0001 after the Errors triage.
• An exhausted or ambiguous callback requiring investigation and a safe recovery decision; not every delivery supports manual replay.
• A question these docs do not answer. That gap is ours to fix, and the report helps.

Before you write, check status.aggregator.gg: check current incident information there, alongside your own monitoring. The address is support@aggregator.gg. Include what the Errors page suggests you log: HTTP status, an allowlisted error code and a reviewed correlation ID, without raw bodies or secrets, so the conversation starts with the facts.