Game Events

THNDR calls this endpoint to notify the Operator of a game event. Operators can use these events to display notifications inside their apps.

This feature is optional - it is not required to go live with our games.

For DepositsAPI users: the roundId property has the same value as depositId and can be used to associate transactions with game events.

Endpoint

POST {operatorURL}/thndr/events

ROOM_CREATED Event

The ROOM_CREATED event is sent by THNDR to notify the Operator when a player creates a new room. The player who creates the room is automatically its first participant.

{
    "event": "ROOM_CREATED",
    "userId": "{USER_ID}",
    "roomId": "{ROOM_ID}",
    "roundId": "{ROUND_ID}",
    "gameId": "{GAME_ID}"
}

  • userId - Player identifier on the Operator’s platform.

  • roomId - Identifier for the game room. Players sharing the same roomId are participating in the same PvP match.

  • roundId - Identifier of the game round this room belongs to.

  • gameId - Game identifier. Possible values: solitaire, blocks, twentyone, blackjack, slots.

ROOM_JOINED Event

The ROOM_JOINED event is sent by THNDR to notify the Operator when a player joins an existing room. That player becomes the room’s second participant.

Note: This event is triggered twice when the second player joins — once for the first player and once for the second player.

{
    "event": "ROOM_JOINED",
    "userId": "{USER_ID}",
    "roomId": "{ROOM_ID}",
    "roundId": "{ROUND_ID}",
    "gameId": "{GAME_ID}",
    "opponentNick": "{OPPONENT_NICK}"
}

  • userId - Player identifier on the Operator’s platform.

  • roomId - Identifier for the game room. Players sharing the same roomId are participating in the same PvP match.

  • roundId - Identifier of the game round this room belongs to.

  • gameId - Game identifier. Possible values: solitaire, blocks, twentyone, blackjack, slots.

  • opponentNick - Nick of the opponent that joined the room.

OPPONENT_ROUND_FINISHED Event

The OPPONENT_ROUND_FINISHED event is sent by THNDR to notify the Operator that the opponent of their player has completed their round.

{
    "event": "OPPONENT_ROUND_FINISHED",
    "userId": "{USER_ID}",
    "roomId": "{ROOM_ID}",
    "roundId": "{ROUND_ID}",
    "gameId": "{GAME_ID}",
    "opponentNick": "{OPPONENT_NICK}"
}

  • userId - Player identifier on the Operator’s platform.

  • roomId - Identifier for the game room. Players sharing the same roomId are participating in the same PvP match.

  • roundId - Identifier of the Operator’s player round.

  • gameId - Game identifier. Possible values: solitaire, blocks, twentyone, blackjack, slots.

  • opponentNick - Nick of the opponent that finished their round.

Signature Verification

Verify the request signature using raw request body as the request payload. More in the Request Signing section.

PreviousBalanceNextErrors

Last updated