Skip to content

Quickstart

Use the Integration walkthrough after confirming the prerequisites for your organization.

  • Authorized organization access and a credential issued for your integration
  • Provider and game availability confirmed for that organization
  • A backend that can receive HTTPS wallet callbacks
  • A separately configured callback signing secret
  • Funding or any welcome credits agreed and enabled for real-money validation

Set AGGREGATOR_API_KEY to the issued credential and keep it on your backend. Examples do not select an environment, expand permissions, or establish go-live approval.

  1. Confirm your access, deployment and enabled operations.
  2. List available games: GET /v1/games.
  3. Where available, launch a demo preview with POST /v1/demo-sessions; this does not validate wallet settlement.
  4. Configure and verify your callback URL and separate signing secret using the controls available to your deployment.
  5. Run an authorized real-session test. Verify the HMAC, commit each wallet change and its idempotent result, then return the successful callback response.

Complete the Go-live checklist and applicable commercial approval before opening customer traffic.