Skip to content
ODDStageGAME API HUB
Developers

One API for every game in your lobby

Launch games, run a seamless or transfer wallet, award free rounds and receive webhooks through a single, well-documented integration.

Developer workstation with code editors and connected API service icons
API overview

Everything you need to run a casino lobby

The same contract for every provider in the network, so adding content never means another integration.

Seamless wallet

Balances stay on your platform. We call your wallet for every bet, win and rollback in real time.

Transfer wallet

Prefer to move funds into a game session? Transfer in and out with a simple, auditable balance model.

Game launch

One endpoint returns a launch URL for real-money or demo play, on desktop and mobile, for any provider.

Free rounds

Award free rounds on supported games from your CRM, with bet level, count and expiry in a single call.

Webhooks

Subscribe to round results, free-round usage and catalogue updates instead of polling.

Sandbox

A full test environment with demo games, so you can validate every wallet scenario before go-live.

Code samples

From request to first spin

Sign the request body with your secret, call the launch endpoint and redirect the player, or embed the URL in an iframe. Wallet callbacks follow the same signing rules.

  • REST + JSON
  • Desktop & mobile
  • Real money & demo
  • Multi-currency
api / v1
  • POST/games/launchLaunch URL
  • GET/gamesCatalogue & metadata
  • POST/free-roundsAward campaigns
  • CB/wallet/debit · credit · rollbackYour endpoints
  • HOOKround.settledWebhook events
Simplified overview. Names are illustrative; the full reference ships with sandbox access.
import crypto from "node:crypto";

// Launch a game session for a player
const body = JSON.stringify({
  gameId: "slots-studio:example-game",
  playerId: "player-123",
  currency: "EUR",
  language: "en",
  device: "desktop",
  returnUrl: "https://your-casino.example/lobby",
});

const signature = crypto
  .createHmac("sha256", process.env.MG_API_SECRET)
  .update(body)
  .digest("hex");

const res = await fetch("https://sandbox.api.example/v1/games/launch", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-Operator-Id": process.env.MG_OPERATOR_ID,
    "X-Signature": signature,
  },
  body,
});

const { launchUrl, sessionId } = await res.json();

Simplified examples for illustration. Endpoints, headers and fields are described in full in the API reference.

Integration steps

Four steps to production

An integration engineer is assigned to your team for the whole process.

  1. Get sandbox access
    01

    Access

    Get sandbox access

    Request access, receive credentials and the API reference, and whitelist your server IPs.

  2. Build launch & wallet
    02

    Build

    Build launch & wallet

    Implement game launch plus the debit, credit and rollback callbacks on your side.

  3. Run the test scenarios
    03

    Test

    Run the test scenarios

    Validate happy paths, duplicates, timeouts and rollbacks in the sandbox with our engineers.

  4. Go live
    04

    Launch

    Go live

    Switch to production keys, enable providers per market and monitor the first sessions together.

Developer toolkit

Sandbox, security and webhooks

The pieces that make an integration predictable, from the first test call to live traffic.

Sandbox

Test every scenario before go-live

A full test environment with demo games, separate credentials and the wallet edge cases your team needs to validate: duplicates, timeouts and rollbacks.

Security

Signed, restricted and safe to retry

HMAC signatures on every request and callback, IP whitelisting, idempotent transaction IDs and TLS on all traffic.

Webhooks

Events instead of polling

Subscribe to round results, free-round usage and catalogue updates, and react in your own systems as they happen.

Security

Money movements you can trust and trace

Wallet traffic is signed, restricted and safe to retry, so network issues never become balance issues.

HMAC signatures

Every request and callback carries a SHA-256 HMAC signature, so both sides can verify origin and integrity.

IP whitelisting

API calls are only accepted from registered server addresses, and callbacks come from published ranges.

Idempotency

Unique transaction IDs make retries safe. A repeated debit or credit is never applied twice.

Encrypted transport

All traffic runs over TLS, with separate credentials for sandbox and production environments.

API reference

Get the full API documentation

The API reference and sandbox credentials are shared with operators and platforms after a short review.

Request API docs
API access

Request sandbox access

Tell us about your platform. Our integration team reviews each request and shares documentation and credentials with qualified operators and platforms.

  • API reference and integration guide
  • Sandbox credentials with demo games
  • Test scenarios for wallet edge cases
  • A named integration engineer

Request API access

Tell us about your platform and we'll share documentation and sandbox credentials.

For B2B enquiries only. Your details are handled under our privacy policy.

Ready when you are

Talk to an integration engineer

Walk through your stack, wallet model and timeline with our technical team in a 30-minute call.