ii-gaming.co
Login
Onboarding in minutes

Integration checklist

Paste your operator token and run a live check of headers, authentication and the essential routes. Each step shows the real response of the public v1 API at i-gaming.co.

Your token never leaves your browser — every request goes straight from your browser to the API. Header sent: X-Operator-Token.

1. Authentication with X-Operator-Token

POST /auth/check

Confirms the header reaches the server and the token is active.

2. Introspection (domain whitelist)

GET /auth/introspect

Lists the domains allowed to embed your iframe.

3. Games enabled for the operator

GET /games/list

Confirms which games show up in your iframe.

4. Statistics (last 24h)

GET /stats?days=1

KPI endpoint for dashboards.

5. Bet listing

GET /bets?limit=1

Round audit — the basis for reconciliation.

6. Negative check (no token)

GET /bets?limit=1

Proves the server rejects calls without credentials.

Payments: ready to use, or bring your own

You do not have to build a payment integration to go live. We ship 116 payment gateways already mapped across 73 countries — you paste the key your provider gave you and switch it on.

116 gateways ready in the panel

Pix, cards, wallets and local bank transfers, covering 73 countries. Pick the provider, paste the credentials it gave you (API key, merchant ID, Pix key) and activate. No code required.

Or integrate whichever you want

Already have a PSP contract? Connect it through our deposit/withdrawal API with HMAC-signed webhooks. Any gateway that answers the callback contract works — you are never locked into ours.

Test with fake money first

Sandbox mode returns a mock QR code and settles deposits and withdrawals instantly, so you can validate the whole cashier flow before going live.

Who receives the money

Player money lands directly in your provider account — we never hold your funds. We only read the settlement event to credit the player wallet.

Open payment settings

Next steps

  • • Risk-free test environment: /sandbox
  • • Full endpoint documentation: /docs
  • • Troubleshooting common errors: /docs/integracao-troubleshoot
  • Dica: se Authorization: Bearer fail on some CDN in your stack, use X-Operator-Token ou x-api-key — todos são aceitos.

How game health checks work

The portal probe tests two routes on each game (historical compatibility) and accepts either one that answers with a valid HMAC:

  • • /api/public/dl/seamless-ping — current standard
  • • /api/public/dl/ping-hmac — legacy standard (4 games)
✅ HMAC OK (online)
  • launch_not_found
  • session_missing
  • launch_token_invalid
  • unknown_round
  • ok: true

Signature accepted — the ping token simply does not exist in the database.

❌ Real failure
  • bad_signature (401)
  • portal_response_bad_signature (403)
  • HTML/404 → unpublished route

Rotate PORTAL_HMAC_SECRET on both sides, or publish the ping endpoint.