Get integrated in three steps
This guide will walk you through authenticating your requests, syncing our casino catalog, and generating your first game launch URL.Step 1: Prepare your Authentication
To communicate with our gateway, you need to construct yoursv-api-key. This header tells our system who you are and which operator environment to load.
Construct your API Key
Construct your API Key
Your key is a concatenation of three values provided by your account manager:
PUBLIC_KEY . OPERATOR_SLUGExample: SV.pk_live_12345.smatvirtual-usTest your Connection
Test your Connection
Try a simple
GET request to our staging environment to verify your key:cURL
Step 2: Sync the Casino Portfolio
Before you can launch a game, you need its uniquegameId. Use the Games endpoint to pull the latest list of available Instant and Tournament titles.
Fetch Game IDs
Fetch Game IDs
Call the
/games endpoint. You will receive a JSON array of available
titles. 1. Identify the gameId (e.g., spin-win, tournament). 2. Store
these in your database to populate your game lobby.Filter by Category
Filter by Category
Our API allows you to distinguish between Instant Games (Single Player)
and our Flagship Tournament engine. Use these categories to organize
your UI.
Step 3: Launch your first Game
The final step is to request a signed URL. This URL is what you will use to redirect your player into the game.Request a Launch URL
Request a Launch URL
Send a
GET request to the /launch-url endpoint with the following required parameters:- gameId: The slug you retrieved in Step 2.
- playerId: Your internal unique ID for the user.
- sessionId: A unique token for this specific session.
Response.json
Next steps
Now that you have mastered the basics, dive deeper into our advanced features:Demo Mode
Learn how to trigger free-play sessions with a single query parameter.
Authentication Deep Dive
Detailed breakdown of security and key management.
Tournament Engine
Explore the unique logic behind our flagship competitive games.
API Reference
Browse the full specification for every smatvirtual endpoint.
Pro-Tip: Always perform your initial integration against our Staging
Environment before moving to Production.
