Quick Start

Submit Your Configuration

To get started, submit your integration details through our onboarding form:

You'll need to provide the following for your staging environment:

Once submitted, you'll receive:

• Your operatorId - links to your operator configuration (provided by 155.io)
• 155.io's public key - to verify our responses
• 155.io's IP addresses - to whitelist on your server

You'll also need to choose your own partnerId — this is a string you define to identify your website or casino brand (e.g., "my-casino", "my-casino-asia"). You can use different partner IDs to distinguish between platforms or regions under the same operator.

Implement Request Signing

All API requests must be signed using RSA-SHA256. Here's a quick implementation:

import { createSign } from 'node:crypto'

function signPayload(payload: string, privateKey: string): string {
  return createSign('RSA-SHA256')
    .update(payload)
    .sign(privateKey, 'base64')
}

// Usage
const signature = signPayload(JSON.stringify(requestBody), privateKey)
// Add to request: headers['X-Marbles-Signature'] = signature

from cryptography.hazmat.primitives import hashes, serialization
from cryptography.hazmat.primitives.asymmetric import padding
import base64

def sign_payload(payload: str, private_key_pem: str) -> str:
    private_key = serialization.load_pem_private_key(
        private_key_pem.encode(), password=None
    )
    signature = private_key.sign(
        payload.encode(),
        padding.PKCS1v15(),
        hashes.SHA256()
    )
    return base64.b64encode(signature).decode()

# Usage
signature = sign_payload(json.dumps(request_body), private_key)
# Add to request: headers['X-Marbles-Signature'] = signature

function signPayload(string $payload, string $privateKey): string {
    openssl_sign($payload, $signature, $privateKey, OPENSSL_ALGO_SHA256);
    return base64_encode($signature);
}

// Usage
$signature = signPayload(json_encode($requestBody), $privateKey);
// Add to request: $headers['X-Marbles-Signature'] = $signature

See the full Security documentation for more details.

Implement Your Endpoints

You need to implement four endpoints on your server:

See Operator API for full endpoint specifications.

Fetch Available Games

Get the list of games using the /game/games endpoint:

curl -X POST https://api.marbles.xyz/game/games \
  -H "Content-Type: application/json" \
  -H "X-Marbles-Signature: <your-signature>" \
  -d '{"operatorId": "your-operator-id"}'

See Get Games for the full response format.

Generate Game URLs

Create a game session for a player:

curl -X POST https://api.marbles.xyz/game/game/url \
  -H "Content-Type: application/json" \
  -H "X-Marbles-Signature: <your-signature>" \
  -d '{
    "clientSessionId": "session-123",
    "clientPlayerId": "player-456",
    "operatorId": "your-operator-id",
    "partnerId": "my-casino",
    "gameId": "game-uuid-from-step-4",
    "username": "player_username",
    "currency": "USD",
    "platform": "DESKTOP"
  }'

The response contains a URL you can use in an iframe or redirect to directly.

Test Your Integration

1. Generate a game URL on staging and open it in a browser
2. Place a test bet — verify your /bet endpoint receives the request
3. Complete the game — verify /win or /rollback is called correctly
4. Check that balances update correctly throughout

See the full Testing guide for details on track availability, go-live readiness, and what to expect during the final verification.