Casino API Sandbox

Full API Access. No Sales Call. Credentials in Under 24 Hours.

Every provider in our library. Every endpoint. Every game. The fastest way to know whether the SoftAPI aggregator fits your platform is to integrate it — not sit through a demo deck.

Get sandbox credentials Read the docs →

✓ Free — no credit card ✓ No time limit ✓ No NDA required ⏱ Credentials in <24h

bash

curl -X POST https://sandbox.softapisolutions.com/v1/session \ -H “Authorization: Bearer YOUR_SANDBOX_KEY” \ -H “Content-Type: application/json” \ -d ‘{ “playerId”: “test-player-01”, “currency”: “USD”, “gameId”: “pragmatic/sweet-bonanza”, “language”: “en” }’

Response

{ “sessionId”: “sess_8K2x9pQ4mR3L7vW”, “gameUrl”: “https://launch.softapisolutions.com/…”, “expiresAt”: “2026-06-21T15:42:11Z” }

Why no gate

Why we don’t gate the sandbox

Almost every casino aggregator forces prospective operators through a sales gate before they can see the product working. Discovery call. NDA. Demo deck. Reference call. Maybe — maybe — a sandbox key, four weeks in, after you’ve already invested days in conversations.

We think that’s backwards. The fastest way to evaluate a casino games aggregator is to integrate it. If the API doesn’t fit your architecture, if the documentation isn’t clear enough, if the response shapes don’t match — you should know now, not three months into a contract.

Submit a short form. Get credentials within one business day. Build against the real API with the real game library. Take as long as you need. When you’ve evaluated enough to want a commercial conversation, we’ll have one. Until then, you won’t hear from us.

Everyone else vs SoftAPI

Discovery call45 minutes with a sales rep who hasn’t seen your codebase

NDALegal review, signatures, two weeks

Demo deckSlides that don’t show you whether it fits your stack

Maybe sandbox accessWeeks later, limited scope

✓

SoftAPI: fill out a formName, email, company, market. One minute.

✓

Credentials within 24 hoursFull library, full endpoints, no time limit

What’s included

What’s in the sandbox

The sandbox is functionally identical to production. Same providers, same endpoints, same response shapes — only the credentials, wallet, and player accounts differ.

✅

Full provider library

Every studio — Pragmatic Play, Evolution, NetEnt, Hacksaw Gaming, BGaming, Spribe, Nolimit City, Play’n GO, Ezugi and all others in the SoftAPI library. No premium providers gated to production.

✅

Every game in every catalogue

Not a curated subset. Not three demo titles per studio. Every game available to operators in production is available to test.

✅

Every API endpoint

Session creation, bet placement, game state, settlement webhooks, rollback, reporting, agent management, player management — all production endpoints with sandbox credentials.

✅

Both wallet architectures

Seamless wallet and transfer wallet are both available. Pick the one your platform uses, or test both.

✅

Full agent system

Create master agents, sub-agents, configure tier depth, run multi-tier reporting — everything that’s available in production.

✅

All webhooks and response shapes

Bet settlements, rollbacks, void notifications, jackpot triggers, free-spin bonuses — every webhook your platform needs to handle fires in the sandbox.

✅

No time limit

Sandbox credentials don’t expire. Use them for a week, a month, or six months. We won’t pressure you into a commercial conversation before you’re ready.

✅

Multi-currency including crypto

BRL, MXN, COP, NGN, KES, INR, PHP, EUR, USD, BTC, ETH, USDT and every other supported currency — test the full settlement shape before you go live.

Quick start

Get started in 3 steps

From zero to a working game session in under 24 hours.

Submit the request form

Short form — name, email, company name, target market, and rough expected GGR (optional). Takes about a minute. No NDA, no discovery call, no deck.

Get sandbox credentials →

Receive credentials within 24 hours

We verify requests manually (the iGaming industry attracts enough competitor probing that we don’t auto-issue keys). We’ll email you sandbox API keys, dashboard login, and the documentation link. Most requests turn around in under 4 hours during business days.

Authenticate and make your first call

Use your sandbox API key as a Bearer token. Create a game session and watch bet settlements stream to your webhook endpoint.

bash — session creation

json — response

{ “sessionId”: “sess_8K2x9pQ4mR3L7vW”, “gameUrl”: “https://launch.softapisolutions.com/game/sweet-bonanza?session=…”, “expiresAt”: “2026-06-21T15:42:11Z” }

You’ve now created a game session. Open the gameUrl in an iframe or new window — watch bet settlements stream to your webhook as the simulated player plays.

Full integration guide → API reference →

Testing checklist

What you can actually test

Use the sandbox to validate everything you’ll need in production before committing to anything.

✅

Game library coverage — load every game in every category; check whether the studios you need for your market are there

✅

Game launch and rendering — embed launch URLs into your platform’s lobby and verify the player experience

✅

Wallet integration — wire up seamless or transfer wallet; confirm bet debits, win credits, and rollbacks settle as expected

✅

Webhook handling — receive bet settlement, void, and rollback webhooks; validate HMAC signatures

✅

Currency and language coverage — test BRL, MXN, NGN, INR, EUR, USD, BTC, ETH, USDT and every supported language

✅

Agent system configuration — build a multi-tier hierarchy, set per-agent rev share and game allowlists, confirm reporting rolls up

✅

Reporting API — pull GGR, NGR, hold %, and per-provider performance through the reporting API and dashboard

✅

Compliance toggles — enable jurisdictional restrictions, RTP caps, and RG controls; confirm they propagate to the games

✅

Load and latency — measure response times from your infrastructure region against your platform’s SLA requirements

✅

Error handling — trigger insufficient balance, invalid session, rollback after settlement; confirm your platform handles them gracefully

If anything on this list doesn’t work the way you need it to in the sandbox, raise it before you sign. We’d rather fix a webhook spec upfront than find out post-launch.

Sandbox vs production

What’s actually different

The sandbox is built to be as close to production as practically possible. Only three things differ.

	Sandbox	Production
Credentials	Sandbox API key + sandbox dashboard	Production API key + production dashboard
Money	Simulated wallet — top up freely from the dashboard	Real money, settled per your commercial agreement
Player accounts	Test player IDs, freely created	Real players, KYC’d per market requirements
Game results	Same RNG as production	Same RNG as sandbox
Provider library	Every provider, every game	Every provider, every game
API endpoints	Same shape, same auth	Same shape, same auth
Webhooks	Fire to your test endpoints	Fire to your production endpoints
Reporting	Real-time, same schema	Real-time, same schema
Latency	Slightly higher (shared infra)	Lower (dedicated infra)
Uptime SLA	Best effort	99.95% — status page

Migration from sandbox to production is essentially swapping the base URL and API key. No rewriting of integration logic required.

Authentication

Authentication and environment basics

Sandbox API keys are scoped to your operator account and issued as Bearer tokens.

base URL

https://sandbox.softapisolutions.com/v1/

All requests require:

🔑

Authorization: Bearer YOUR_SANDBOX_KEY

API key issued with your sandbox credentials

📋

Content-Type: application/json

Required on all POST requests

Webhooks are signed with HMAC-SHA256 using a secret you set in the dashboard. Verify every incoming webhook signature — the docs include verification code in TypeScript, Python, PHP, Go, and Java.

Rate limits in the sandbox are slightly tighter than production to discourage scraping. If you bump into the limit during legitimate load testing, ask support to lift it for your account.

Quick links

📖

Documentation

Full API docs including webhook verification examples in 5 languages

📡

API Reference

Complete endpoint reference with request/response schemas

🔗

Integration Guide

Step-by-step walkthrough from sandbox to production

💼

Seamless Wallet

Wallet architecture guide and integration spec

📊

Status Page

Sandbox and production uptime, incident history

FAQ

Frequently asked questions

Is the casino API sandbox really free?

Yes. No charge, no credit card, no minimum commitment. We don’t charge for sandbox access because we’d rather have you evaluate the product properly than rush you into a contract.

How long does it take to get sandbox credentials?

Most requests are approved and credentials issued within 4 hours during European business hours. The maximum is 24 hours. We verify manually because the iGaming industry sees a lot of competitor probing — we don’t auto-issue keys to anonymous emails.

Is there a time limit on sandbox access?

No. Once issued, sandbox credentials don’t expire. Use them for as long as you need to evaluate, integrate, and test.

Do I need to sign an NDA before getting sandbox access?

No. Public documentation, public sandbox. We only formalize agreements when there’s a commercial conversation worth formalizing.

What’s the difference between the sandbox and a demo call?

A demo is a sales rep walking through a deck. The sandbox is your engineers writing code against the real API. We offer both, but most prospects find the sandbox more valuable — it answers technical questions a demo never can.

Can my entire engineering team use the sandbox?

Yes. Sandbox credentials are issued per operator account, and you can create additional team logins for the sandbox dashboard at no cost. Most operators have between 3 and 10 engineers working in the sandbox during evaluation.

Are the games in the sandbox the same as in production?

Yes. Same providers, same RNG, same game logic, same RTP. The only differences are the wallet model (simulated money) and that the sandbox runs on shared infrastructure with a slightly looser uptime SLA.

Can I test the agent system in the sandbox?

Yes. The full agent-under-agent system is available — create master agents, configure tier depth, set per-agent commercial terms, and validate multi-tier reporting. Most agent-driven operators model their entire planned hierarchy in the sandbox before going live.

Can I test multi-currency and crypto settlement in the sandbox?

Yes. Every supported currency works in the sandbox — fiat (BRL, MXN, COP, NGN, ZAR, KES, INR, PHP, EUR, GBP, USD) and crypto (BTC, ETH, USDT, SOL, LTC, TRX). Crypto wallet settlement uses simulated balances; the integration shape is identical to production.

Will sandbox response times match production?

Sandbox infrastructure is shared and slightly higher-latency than production by design. For accurate latency benchmarking, ask support to enable production-equivalent routing for a defined load test window — we’ll provision it on request.

Do I need a gaming license to get sandbox access?

No. Many operators evaluate the SoftAPI aggregator before they’ve finalized their license. Production access does require a valid license in your target jurisdiction, but the sandbox is open to anyone seriously evaluating.

What happens when I’m ready to move to production?

Three things change: swap your API key and base URL to production, sign the commercial agreement for your chosen pricing model, and we provision a production account. Everything you built in the sandbox works identically against the production endpoint.

Start integrating today

Submit a request and you’ll have credentials within one business day — sandbox API key, dashboard login, and a link to the integration guide. Everything else is yours to test.

Get sandbox credentials Read the docs → Integration guide →