Operators

You run a casino: players, a wallet, a storefront. Aggregator.gg gives that storefront a game catalog from many studios behind one API, so you integrate once and add content by enabling it, not by building it. This page is the orientation; the six-step track is where the work happens.

The business model

You own the player wallet, and Aggregator.gg never holds player funds. Paid bets debit your ledger and wins credit it; grant-funded bets preserve cash, delivered as HMAC-signed callbacks your backend answers. Money moves in your books; the platform routes, verifies, and records it.

You pay for content in prepaid spin packages, a pool of spins drawn down by your traffic. Before the human runs a money-path test, confirm access, available credits and spending limits. A welcome grant may help if actually present; a completed paid purchase requires server-confirmed paid status and matching credit. Session balances and normalized wallet callback amounts use integer minor units: 10000 is 100.00 EUR. Grant stakes and catalog metadata have their own units, so follow each endpoint’s schema.

What you can use today

• One catalog across studios: GET /v1/games with filters for type, volatility, RTP, features, and currency.
• Real and demo sessions: real play against your wallet, and demo launches that move no money at all.
• Signed wallet callbacks: the callback contract with signatures, idempotency, and structured errors.
• Free rounds: issuing and settling free rounds on games that support them.
• Multi-brand attribution: platform accounts when one key serves several brands.
• Reconciliation: GET /v1/transactions as the platform-side record to check your ledger against.

How you integrate

Self-serve, against one wallet API, in six steps that each end with a check: create your API key, pick a game from the catalog, launch a demo session, stand up the wallet callback, play a real round on available credits, and prove readiness with the reconciliation check. Implementation time depends on your wallet and available access; Getting started walks every step.

Before you start you need three things: a cabinet account, your agg_ API key stored in an environment variable, and an HTTPS endpoint for wallet callbacks.

Where to start

Start the track at Getting started. The contracts it leans on each have their own page in the Docs journey: How a round works, Callbacks, Request signatures, Errors, and the go-live checklist when you are ready to open real traffic.