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

PLAYER_ROUND_FINISHED Event

The PLAYER_ROUND_FINISHED event is sent by THNDR to notify the Operator when a player completes their round.

{
    "event": "PLAYER_ROUND_FINISHED",
    "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.

OPPONENT_JOINED Event

The OPPONENT_JOINED event is sent by THNDR to notify the Operator that an opposing player has joined a room previously created by the Operator’s player.

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

  • userId - Identifier of the player on the Operator’s platform that created the room.

  • 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.

PLAYER_SCORE_ACCEPTED Event

The PLAYER_SCORE_ACCEPTED event is sent by THNDR to notify the Operator when the player's score was accepted and used for the match settlement.

{
    "event": "PLAYER_SCORE_ACCEPTED",
    "userId": "{USER_ID}",
    "roomId": "{ROOM_ID}",
    "roundId": "{ROUND_ID}",
    "score": 1234,
    "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 Operator’s player round.

  • score - The player's score.

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

Signature Verification

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

PreviousBalanceNextErrors

Last updated