Getting started

This site is for operators — the sites/apps that embed games from moose-platform's catalog for players. If you haven't read it yet, Introduction & concepts covers the mental model this whole site assumes.

Prerequisites

• An operator tenant ID and HMAC secret, issued by the platform's admin team out-of-band when your tenant is created. Keep the secret server-side only — it signs every call you make to the platform and verifies every call the platform makes back to you, and must never reach the browser.
• A wallet backend implementing the platform's wallet callback API — the platform calls this to debit/credit players and query balances. Without it, REAL mode has no wallet to settle against (DEMO mode doesn't need it — see Launching games). This is normally the largest piece of work in the integration — see Implementing the wallet callback.
• A page to embed the game in — typically an iframe pointed at the launchUrl you get back from launching a session.

The end-to-end flow

1. Your server launches a session. Sign and call POST /v1/operator/games/launch with the player, game, and currency. You get back a launchUrl and sessionToken.
2. Embed the game. Load launchUrl into an iframe on your page.
3. Run the shell. Attach a postMessage listener against the documented bridge protocol to receive the game's lifecycle events (loaded, bet start/end, balance exhausted, exit) — see Shell bridge.
4. Settle transactions. As the player bets and wins, the platform calls your wallet callback API in real time to debit/credit their balance in your own system — see Implementing the wallet callback.

From here: Launching games walks through step 1 in full, with a worked signing example.