Quick Start
Overview
The VCT Gaming Integration Platform provides unified Open APIs for Agents, integrating BG (Big Gaming), GSC, SA Gaming, and WM Casino into a single interface.
All API calls require authentication via a Custom Token.
Base URLs
| Environment | Base URL |
|---|---|
| Production | https://api.vct-gaming.com |
| Staging | https://staging-api.vct-gaming.com |
Credentials
Each Agent is assigned a unique pair of API credentials:
| Field | Description | Usage |
|---|---|---|
agent_api_key | API Key (public identifier) | Identity in the Token, transmitted in plaintext |
agent_api_secret | API Secret (private key) | HMAC-SHA256 signing key, never included in the Token |
Security Warning
agent_api_secret is used for server-side signing only. Never expose it in frontend code, logs, or public repositories.
Common Request Headers
| Header | Value | Description |
|---|---|---|
Authorization | Bearer {token} | Agent Token (required) |
Content-Type | application/json | Request body format |
Common Response Format
json
{
"code": 0,
"message": "success",
"data": { ... },
"timestamp": 1711411200000,
"request_id": "req_xxxxxxxxxxxx"
}| Field | Type | Description |
|---|---|---|
code | int | Status code, 0 = success, non-0 = failure |
message | string | Status description |
data | object | Business data |
timestamp | long | Response timestamp (milliseconds) |
request_id | string | Unique request ID for troubleshooting |
Next Steps
- Learn about Authentication — Token encryption rules and flow
- View Code Examples — Multi-language Token generation examples
- Browse API Reference — Complete API documentation