Getting Started
Connect your backend, find an entitled game, and launch a session with reliable settlement handling.
On this page
Your backend calls one JSON endpoint to browse games, create players, launch sessions, and manage supported free rounds.
Aggregator supplies this casino game aggregation API to gaming operators and platform developers. Begin with the integration checklist for authentication, demo testing, player-wallet settlement, recovery, and production prerequisites. Compare activation and GGR pricing when planning provider access.
For a guided reading path, use the casino API integration handbook. The wallet architecture guide connects reservations, signed callbacks and reconciliation without replacing the method contracts below.
Endpoint and authentication#
POST https://aggregatornetwork.com/v1/commands
X-API-Key: YOUR_APPLICATION_API_KEY
Content-Type: application/jsonCreate an Application API Key in API Keys. Keep it on your server. Its scopes, IP allowlist, expiry, and workspace entitlements apply to every command. Demo play uses getGameDemo; it still requires an authorized key and workspace access.
Basic flow#
- Check Access & Limits for enabled currencies, providers, and games.
- Configure your HTTPS callback, signing secret, and exact HTTPS return origins in Workspace Settings.
- Call
getGameListfor your currency and copy a returned game identifier. - Reserve the player's starting funds in your wallet. Call
getGamewith that numericbalanceand a persistedIdempotency-Key. - Open the URL from a successful response. Process settlement callbacks once per
serial_number, preserving decimal amounts.
Player creation is optional: the gateway maps the player at launch. Production activation and a positive workspace GGR balance are required for real-money play.
Documentation contents#
| Task | Guide |
|---|---|
| Build a backend request | PHP, Node.js, and Java |
| Find available inventory | Providers and currencies, game catalogue |
| Prepare and launch a player | Create player, launch game, launch demo |
| Configure supported features | RTP, grant free rounds, cancel free rounds |
| Operate the integration | Settlements, workspace balance, validation and recovery |
| Plan a player-facing website | Turnkey Casino Website |
| Resolve common questions | FAQ, 9Wicket availability |
Mutation keys must identify one operation and be retained with its request. Read-only and demo methods reject the header. If an outcome is unknown, reconcile before issuing a new operation.