Game Rounds (API)Overview

Game Rounds - Backend integration

Game rounds (or, alternatively, game transactions, i.e. bets and wins) form the backbone of our ranking algorithms. These are transmitted server to server. It’s essential that we receive this data in near real-time to compute leaderboard updates as quickly as possible, thereby ensuring the best user experience for players.

Different casino platforms operate uniquely, but we are flexible and can accommodate various data formats and communication methods to receive game rounds. The exact details are discussed with the client’s tech team at the beginning of the integration to determine the best option. Below are examples from integrations we’ve successfully completed with other clients.

Payload format

Although we can accept individual transactions (i.e., separate bets and wins), we prefer receiving final game rounds that consolidate all the transactions within that round — e.g. the total bet and win amounts in a single payload. This approach reduces network traffic and eliminates the need to verify if all transactions for a specific round have been received.

Example game round payload:

{
    "roundId": "f9c15be2-7164-11ed-a1eb-0242ac120002",
    "brandId": "superkingz",
    "playerId": "Player-4",
    "gameId": "EVO_ANDAR_BAHAR_1",
    "roundType": "REGULAR",
    "betAmount": 2.5,
    "winAmount": 1,
    "currency": "EUR",
    "timestamp": "2022-04-30T04:03:10.200Z"
}

Depending on the communication channel, we can adapt to specific formats determined by the client system or, alternatively, we can provide a specific expected format, such as the example payload above.

Communication methods

We can receive game rounds in a number of different formats, such as:

  1. The client system calls Gamity’s standard Game Round HTTP API, effectively pushing the data to Gamity.
  2. Gamity’s server periodically (e.g., every second) pulls a batch of game rounds from an HTTP API hosted by the client’s server.
  3. Gamity’s server connects directly to the client’s database via a secure channel.
  4. Gamity’s server reads game rounds from a Kafka event stream (or other event log) hosted by the client.

Additionally, we can adapt to other communication methods and data sources.