
Access
Get sandbox access
Request access, receive credentials and the API reference, and whitelist your server IPs.
Launch games, run a seamless or transfer wallet, award free rounds and receive webhooks through a single, well-documented integration.

The same contract for every provider in the network, so adding content never means another integration.
Balances stay on your platform. We call your wallet for every bet, win and rollback in real time.
Prefer to move funds into a game session? Transfer in and out with a simple, auditable balance model.
One endpoint returns a launch URL for real-money or demo play, on desktop and mobile, for any provider.
Award free rounds on supported games from your CRM, with bet level, count and expiry in a single call.
Subscribe to round results, free-round usage and catalogue updates instead of polling.
A full test environment with demo games, so you can validate every wallet scenario before go-live.
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.
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.
An integration engineer is assigned to your team for the whole process.
The pieces that make an integration predictable, from the first test call to live traffic.
SandboxA full test environment with demo games, separate credentials and the wallet edge cases your team needs to validate: duplicates, timeouts and rollbacks.
SecurityHMAC signatures on every request and callback, IP whitelisting, idempotent transaction IDs and TLS on all traffic.
WebhooksSubscribe to round results, free-round usage and catalogue updates, and react in your own systems as they happen.
Wallet traffic is signed, restricted and safe to retry, so network issues never become balance issues.
Every request and callback carries a SHA-256 HMAC signature, so both sides can verify origin and integrity.
API calls are only accepted from registered server addresses, and callbacks come from published ranges.
Unique transaction IDs make retries safe. A repeated debit or credit is never applied twice.
All traffic runs over TLS, with separate credentials for sandbox and production environments.
The API reference and sandbox credentials are shared with operators and platforms after a short review.
Tell us about your platform. Our integration team reviews each request and shares documentation and credentials with qualified operators and platforms.
Walk through your stack, wallet model and timeline with our technical team in a 30-minute call.