Quick start — aggregator

If your casino already integrates with an aggregator that speaks our launcher contract, this is the fastest path to a playable embed.

Prerequisites

• Active integration with the aggregator
• Our gamecode (we'll give it to you during onboarding)
• Sandbox credentials from us

Flow

1. Player clicks "Play Bingo" in your casino UI
2. Your backend asks the aggregator to launch the game
3. The aggregator calls our POST /gamelauncher/play
4. We return a launch URL with a short-lived launchCode
5. The aggregator returns the launch URL to your backend
6. Your frontend embeds the launch URL in an iframe
7. The player plays. Round outcomes land in your aggregator's wallet
   record — there are no iframe events to listen for.

You don't implement any of our API directly — the aggregator does.

What you actually do

1. Configure the game in your aggregator panel. Pick our gamecode. Stakes, currencies, and which rooms offer slots are set on our side; tell us what you need.
2. Embed the launch URL the aggregator returns. See Embedding the game for the iframe contract.
3. Provide your own iframe wrapper UI — close button, "back to lobby" etc. The iframe doesn't emit lifecycle events to your page today, so this UI lives outside the iframe.
4. Test in the sandbox before going live, with test player accounts. Note that mode: DEMO still goes through the wallet (see Mode).

Sandbox

For early testing, your aggregator's sandbox can launch our gamecode against its sandbox wallet. We can also give you a test launch URL during onboarding so you can verify the embed before wiring up the aggregator side — just ask.

Going to production

See Go-live checklist.