Choose your integration path

Two integration paths serve three groups, and the split follows what your team owns. Operators bring a wallet and players, run the integration themselves, and prove every step with a check. Platforms do the same across several brands under one account. Game providers bring games, and our team runs the integration together with theirs.

Prove the API is up right now

One command, before you choose anything:

curl -sS https://api.aggregator.gg/health

Expected response: {"status": "ok"}. This call needs no API key, so it works before you register. Business API calls use a Bearer key; public docs and specifications do not. Provider protocols have their own agreed authentication.

How the paths differ

	Operators	Platforms	Game providers
You bring	A wallet and players	Brands and players	Games and a game API
Who runs the integration	Your team, self-serve	Your team, with assisted wallet setup when needed	Our team, together with yours
The work	Call the session API, answer wallet callbacks	Same as an operator, plus brand attribution	Serve launch and session calls, send bet and win
Starts at	Getting started	Platforms	Provider onboarding

Each group has its own orientation page covering the business model, the functionality available today, and where to start: Operators, Platforms, and Game providers.

Operator self-serve

The operator track is six steps, and each one ends with a check that tells you it is done. Implementation time depends on your wallet, access and required evidence:

1. API key. Create your agg_ key in the cabinet; GET /v1/games answering 200 proves it works.
2. Catalog. Pick a launchable game id in your player’s currency.
3. Demo session. Open the game on screen with no money involved.
4. Wallet callback. Stand up the endpoint that verifies signatures and settles bet and win.
5. Real session. Run a controlled round within confirmed access and budget and watch it settle in your ledger.
6. Proof. Run the readiness check and reconcile GET /v1/transactions against your wallet.

Platforms first create a brand and confirm its catalog and shared wallet. Follow Platform accounts alongside this track. Production hardening and internal review are additional work.

Getting started walks the whole track. The contracts it leans on each have their own page: callbacks, request signatures, idempotency, errors, and the go-live checklist.

Game providers: assisted integration

Provider integration is assisted today: our team runs the technical integration together with yours. The track has its own documentation, starting at Provider onboarding. Prepare these and the work moves quickly:

• A game catalog with metadata. The list of games you want distributed, with the metadata operators see, including RTP and the source it comes from.
• Launch and session ingress. The platform calls your game API to launch sessions; your endpoint accepts those calls from our egress addresses.
• Authenticated money calls. Your games settle through the signing and replay rules agreed for the connector; normalized operator wallet callbacks use HMAC-SHA256.
• A latency budget. The money path is synchronous: a bet or win completes only after the operator’s wallet answers, and operators are held to a 5 second budget with an under 2 seconds p95 aim. Size your timeouts to that budget.
• Egress allowlist. Confirm the active production and staging egress lists before allowlisting. Environments explains the source defaults and configuration overrides; providers validate against staging before go-live.

Provider onboarding walks the whole track: the adapter model, the five stages, who does what, and where to write when your catalog is ready. The specification pages behind it are Catalog requirements, Runtime expectations, and Certification and go-live.