Skip to content

Introductionnn

Welcome to the documentation for the gaming integration platform. This documentation is intended for agents integrating with our platform.

What is the platform?

The platform provides gaming content and an API for integration. We offer a unified API for working with games, simplifying integration and game content management.

The role of agents in the system

Agents are platform partners who:

  • Provide access to games for their players
  • Manage players’ balances
  • Process game transactions (bets, wins, rollbacks)

Typical flow

A player launches a game

  • The agent sends a request to the platform: POST /api/games/get_game_link
  • The platform creates a game session and generates a game link
  • The platform returns the link to the agent
  • The player opens the game in the browser

The game requests the balance

  • The game sends a balance request to the platform
  • The platform sends a callback to the agent: getBalance
  • The agent returns the player’s current balance
  • The platform returns the balance to the game

The player places a bet in the game

  • The game sends bet information to the platform
  • The platform sends a callback to the agent: makeBet
  • The agent processes the transaction (debits the bet, credits the win)
  • The agent returns the player’s updated balance
  • The platform processes the response

Core concepts

Game Session

A unique session for a player in a specific game. Created when the game is first launched and used for all transactions within that session.

Transaction

An operation that changes a player’s balance:

  • Bet: debiting funds from the player’s account
  • Win: crediting funds to the player’s account
  • Rollback: cancelling a previous transaction

Balance

The player’s current balance in a specific currency. The balance must be kept in sync between the agent and the platform.

Player

A player is identified by two parameters:

  • player_id: the player identifier in the agent’s system. Must be unique per player and must not change over time.
  • player_username: the player’s username. May be non-unique (multiple players can share the same username).

Important

player_id is used by the platform to identify a player and must be unique. player_username is used for display only.

API token

A secret key used to sign requests. Each agent has a unique API token used to:

  • Sign requests to the platform
  • Verify signatures of callbacks from the platform

What’s next?

  1. Read the Authorization section to learn how to sign requests
  2. Review the API Methods section for endpoints (game links, game lists, etc.)
  3. Set up Callbacks handling — requests the platform will send to you

Getting access

To get started, you need to:

  1. Obtain credentials (agent_id and API token) from the platform manager
  2. Configure the callback URL (ask the manager to set it up)
  3. Implement callback handling on your side

If you have any questions, contact your platform manager.