Environments
New operator integrations use the production API with an agg_ key. There is no new public test-key onboarding path or universal free sandbox. Existing legacy credentials keep their stored environment subject to authentication and revocation; see API keys. Provider staging validation is a separate track.
Environment model
Section titled “Environment model”The public operator base URL is:
https://api.aggregator.gg/v1A demo checks game presentation without wallet movement. An ordinary session using a new live key enters the money path, even when you call it a test. The human must confirm game access, available organization credits, a controlled player wallet and spending limits before running it. Key issuance alone does not establish those conditions.
Welcome credits
Section titled “Welcome credits”A welcome grant may be available in the cabinet. Check the actual credited balance and applicable limits for your organization; do not assume every account receives the same grant, amount or free test access. A welcome grant is not a paid package.
If the budget or access is missing, resolve that blocker with the cabinet or support before running the money test. Buying a package early is optional. It does not replace the test or impose a new billing gate on registration or key issuance.
Step check: the human has verified access, balance and the test’s budget before launching, and the resulting session, signed callback and ledger evidence agree. A demo, quote or purchase transaction hash alone does not establish that result.
Demo sessions
Section titled “Demo sessions”To launch a game purely to inspect the UI or render a preview without any wallet movement, use POST /v1/demo-sessions instead of /v1/sessions. Demo sessions:
- Do not debit any wallet
- Do not emit
betorwincallbacks - Have no impact on your welcome credit balance
Use them for marketing previews, lobby thumbnails, or showing a game inside your own cabinet without any money flow.
Platform IP addresses
Section titled “Platform IP addresses”When the platform calls out to your systems, forwarding bet and win callbacks to your callback URL or, for game providers, calling your game API, use the active egress list shown in the cabinet or confirmed by support. These are the production-source defaults, which deployment configuration can override:
| Environment | Egress IP (IPv4) |
|---|---|
| Production | 116.202.36.242 |
| Staging | 46.224.211.29 |
- Operators integrate against production only: allowlist the production IP on the endpoint that receives wallet callbacks.
- Game providers validate against staging before go-live: allowlist both addresses on the systems the platform calls.
Do not treat the source defaults as a permanent or exhaustive live network contract; recheck the active list when configuration changes. HMAC signature verification remains mandatory regardless of source IP. The allowlist is an additional network control, never a replacement for verifying the signature.
Testing model
Section titled “Testing model”Use the test that answers the question you are trying to verify:
| Need | Use | Money moves |
|---|---|---|
| Inspect a game’s UI | Demo session | No |
| Exercise the ordinary wallet path | Human-run session with confirmed access, credits and limits | Yes |
| Run customer traffic | Approved live integration and funded usage | Yes |
Follow Getting started for integration evidence, then let the human purchase a package, confirm server-reported paid status and credit, and review Go-live. Readiness checks remain advisory; payment and launch are human decisions.
Step check: record what was actually tested and what remains unverified. Do not label a demo or an isolated readiness result as end-to-end wallet acceptance.