Find a player’s round

Start with the player and round when a support query refers to a round number shown in the game. The response lists that player’s bets in the selected round.

This endpoint only applies to games that have a notion of rounds (for example Keno-style draw games). For games without rounds, use Fetch Bet with the individual bet id.

`POST /api/v0.2/fetch-round-bets`

Resolve a round and return the specified player's bets in it.

Authentication

All requests require the following headers:

Header	Type	Required	Description
`X-Operator-Id`	string	Yes	Unique identifier for the operator
`X-Signature`	string	Yes	Base64 URL-safe encoded RSA signature of the request body

Signature Verification

For POST requests:

Sign the entire JSON request body as a string
The value is signed using RSA-SHA256 with the operator's private key
The signature is Base64 URL-safe encoded (no padding)
The server verifies the signature using the operator's registered public key

Request Body

All three fields are required. instance_id and player_id together scope the lookup to a single player, and round_no is the round number the player sees in the game.

{
  "instance_id": "string",
  "player_id": "string",
  "round_no": 12345
}

Field Descriptions

Field	Type	Required	Description
`instance_id`	`string`	Yes	ID of the game instance the round belongs to
`player_id`	`string`	Yes	ID of the player whose bets to return
`round_no`	`number`	Yes	The round number shown to the player

Response

Success Response (200 OK)

{
  "status": "OK",
  "round_id": "string",
  "round_no": 12345,
  "instance_id": "string",
  "game": "string",
  "bets": [
    {
      "status": "CLOSED",
      "reference_id": "string",
      "player_id": "string",
      "round_id": "string",
      "instance_id": "string",
      "game": "string",
      "wager": 10050,
      "won": 20000,
      "timestamp": 1234567890000
    }
  ]
}

Each entry in bets uses the same structure as the Fetch Bet response, and every entry belongs to the requested player_id. Only settled bets are returned - each status is CLOSED or ROLLED_BACK; in-flight (OPEN) bets are not included.

Top-Level Response Fields

Field	Type	Description
`status`	string	One of: `OK`, `NOT_FOUND`
`round_id`	string	The round identifier (the `round_id` Wildvolt sends in deposit / rollback webhooks)
`round_no`	number	The round number shown to the player
`instance_id`	string	ID of the game instance
`game`	string	ID of the game
`bets`	array	The player's settled bets in the round. Empty if the player placed none

Per-Bet Fields

Field	Type	Description
`status`	string	One of: `CLOSED`, `ROLLED_BACK`
`reference_id`	string	Unique identifier of the bet (the bet id)
`player_id`	string	ID of the player who placed the bet (matches the requested `player_id`)
`round_id`	string	The round identifier
`instance_id`	string	ID of the game instance
`game`	string	ID of the game
`wager`	number	Bet amount in cents (divide by 100 for actual value)
`won`	number	Payout in cents (divide by 100), present only for `CLOSED` bets
`timestamp`	number	Unix timestamp in milliseconds

Not Found

{
  "status": "NOT_FOUND"
}

Special Cases

The endpoint returns NOT_FOUND in the following cases:

No round matches the supplied instance_id + round_no
The round does not belong to the supplied instance_id
The round is older than 90 days

A round in which the player placed no bets returns status: OK with an empty bets array.

Status Codes

200 OK - Request processed successfully (including NOT_FOUND results)
400 Bad Request - Missing or invalid instance_id, player_id, or round_no, or missing headers
401 Unauthorized - Invalid operator or signature
403 Forbidden - Operator account is inactive

Use Cases

Player dispute resolution from a round number the player provides
Reconciliation of a single player's outcomes within a round
Audit trail verification for a player in draw-based games

On this page