Skip to content
The Aggregator

Introduction

The Aggregator is a B2B game aggregation platform. We connect game providers (casino content studios — TRUE LABS, BGaming, Zillion, Megafair, eBaka, and more) with operators (casinos that run player-facing front-ends) through one normalised REST API.

Who this is for

Section titled “Who this is for”

This documentation covers the Machine API — the server-to-server interface operators use to:

  • Browse and filter the unified game catalog
  • Launch real-money and demo game sessions
  • Receive HMAC-signed wallet callbacks for bets and wins
  • Query transaction history for reconciliation

If you are looking for the cabinet UI, the analytics dashboard, or the affiliate portal, sign in at app.aggregator.gg.

What the platform handles for you

Section titled “What the platform handles for you”
  • Provider integration normalisation — each provider’s launch protocol, callback shape, and signature scheme is translated into one canonical contract.
  • Game catalog deduplication — same game across multiple providers surfaces once.
  • Session state — open, paused, expired, settled.
  • Callback routing + replay protection — HMAC verification, provider-side checks, and transaction-level idempotency using the signed transaction_id.
  • Financial ledger — immutable, append-only, reconciliation tooling included.
  • Compliance gates — self-exclusion, GeoIP jurisdiction blocking, license checks (fail-closed by default).

What you remain responsible for

Section titled “What you remain responsible for”
  • Player wallet — you hold balances. We tell you when to debit (bet) and credit (win).
  • Player KYC — verifying real-money players is on you.
  • Responsible gaming surfaces — deposit limits, reality checks, session caps are operator-configurable; surfacing them to players is your UX.
  • Licensing — your operating licenses for your jurisdiction.
Section titled “Read next”