Game Rounds
Operators that offer a Casino product can send information about players' gaming experience either with Game Round events or Bet/Win Events. A guide on how to send the first is provided below.
⬆️ POST /v1/integration/gameround
RabbitMQ Message Properties
key | value |
type | GAME_ROUND |
The type is expected as a property (but not in the payload) of the RabbitMQ Message. Any header will be ignored.
Kafka Message Headers
key | value |
type | GAME_ROUND |
Sending each Game Round containing a consolidated view of game events.
Request
Key | Type | Required? | Accepted Values | Description |
user_id | string | Yes | N/A | User Id |
round_id | string | Yes | N/A | Gameround Id |
game_id | string | Yes | N/A | Game id |
game_name | string | Yes | e.g. Dead or Alive | Game name |
game_type | string | Yes | e.g. Slots | Game type |
vendor_id | string | Yes | N/A | Vendor Id |
vendor_name | string | No | N/A | N/A |
real_bet_user | float | No | N/A | N/A |
real_win_user | float | No | N/A | N/A |
bonus_bet_user | float | No | N/A | N/A |
bonus_win_user | float | No | N/A | N/A |
real_bet_base | float | No | N/A | N/A |
real_win_base | float | No | N/A | N/A |
bonus_bet_base | float | No | N/A | N/A |
bonus_win_base | float | No | N/A | N/A |
user_currency | string | Yes | N/A | User currency |
device_type | string | Yes | mobile, desktop, app, unknown | N/A |
timestamp | string | Yes | Format: RFC3339 2015-03-02T8:27:58.10Z | Timestamp |
origin | string | Yes | e.g. www.brand.com | N/A |
meta | object | No | { "key1": "value1", "key2": "value2" } | Used for misc/aux values that is brand specific |