Skip to main content

​
Overview

The smatvirtual API is organized around REST. All requests are made to our Unified Gateway, which handles game discovery, account management, and secure session generation. Our API has predictable resource-oriented URLs, accepts form-encoded/JSON request bodies, and returns JSON-encoded responses with standard HTTP response codes.

​
Core Endpoints

To get your platform live, you only need to interact with these three primary endpoints:

Merchant Account

Create and configure your merchant identity.

Get Games

Fetch the list of Instant and Tournament titles.

Launch URL

Generate secure links to start player sessions.

​
Authentication

Unlike standard Bearer tokens, smatvirtual uses a custom header for all requests. You must include your concatenated API key in every call to identify your merchant and operator environment.
Header KeyValue Example
sv-api-keySV.pk_live_xxxx.operator-slug
{
  "header": {
    "sv-api-key": "YOUR_CONCATENATED_KEY"
  }
}

​
Base URLs

Access our API via the following environments:
EnvironmentBase URL
Staginghttps://api-staging.smatvirtual.com/api/v1.1
Productionhttps://api-prod.smatvirtual.com/api/v1.1

​
Swagger Documentation URLs

Access our API swagger documentation via the following environments:
EnvironmentBase URL
Operator [Staging]https://api-staging.smatvirtual.com/v1/merchant/swagger
Operator [Production]https://api-prod.smatvirtual.com/v1/merchant/swagger
Provider [Staging]https://api-staging.smatvirtual.com/v1/provider/swagger
Provider [Production]https://api-prod.smatvirtual.com/v1/provider/swagger
Pro-Tip: Use the “Try It” console on the following pages to test your sv-api-key against our staging environment in real-time.