Games

Overview

The Games endpoint is part of the Provider API for Aggregators. Its main purpose is to return a list of available games along with key metadata about each game, allowing an Aggregator to display these games in its lobby and let users select one to play.

The Games method allows the Aggregator to:

Retrieve a full list of games offered by the Game Provider.

Display game options — including names, categories, odds information, and lobby images — to end users in the Aggregator’s interface.

Dynamically update the lobby based on the available games without manual intervention.

This endpoint does not require a request body since it is a read-only operation.

Security and Authentication

Even though the Games method does not include a request body, the request must still be authenticated using the required HTTP headers. Please see the required headers below in the Header Params section.

📌

Signature of the request shall be calculated using HMAC-SHA256 algorithm and sent in "X-Sign" header of the request.
Please see How to calculate the X-Sign value.

curl --location --request GET '/v1/games' \ --header 'X-Counterparty-Id: 933a215f-a9e6-4f88-9d91-52a87cd50499' \ --header 'X-Timestamp: 1719766120806' \ --header 'X-Request-Id: 5a0679b6e5fa48f6892c777b0fa92392' \ --header 'X-Sign: c4d62f77cdfaadb6690b3bcbe5a0ca9ef1e5bf41d746d361a1269558eeb7ccd1'

[ { "gameId": 1, "name": "FirstGame" "gameCategory": "crash", "maxOdd": 1000, "lobbyImgUrl": "https://providers-domain/first-game-logo.jpg" }, { "gameId": 1, "name": "SecondGame" "gameCategory": "slot", "maxOdd": 50, "lobbyImgUrl": "https://providers-domain/second-game-logo.jpg" } ]

Overview#

Security and Authentication#

Request

Responses

Overview

Security and Authentication