Skip to main content
The betwin callback is sent when a player’s bet and its outcome complete in a single atomic operation. Your implementation must deduct betAmount from the player’s balance and add winAmount in one transaction — both operations succeed or neither does. This endpoint is used in game types where the bet and outcome are determined simultaneously, avoiding the need for a separate withdraw followed by a deposit. No need to add “BetWin” at the end of your callback URL; you can get the request body “command” to identify which callback is coming.
  • URL: Your configured Callback URL(ex: https://mycallback.com/cb)
  • Method: POST
  • Headers: X-Request-Signature, Content-Type, Accept

​
Request parameters

​
string
required
Always "betwin" for this callback type.
​
long
required
Unique reference of the transaction created in our system. Use this to enforce idempotency.
​
string
required
Unique identifier of the player from your system.
​
long
required
Unique reference of the game round.
​
number
required
Unique identifier of the game provider in our system.
​
int
required
Unique game id of the game in our system.
​
number
required
Player currency code per ISO-4217 (e.g., EUR, USD).
​
number
required
Bet amount to deduct from the player’s balance.
​
long
required
0: no bonus, else the bonus id related
​
number
required
Unix timestamp of the request.

​
Response fields

Your server must respond with HTTP 200 and a JSON body containing the following fields:
​
number
required
The player’s updated balance after the bet is deducted.
​
string
required
Result of the operation. Must be "OK" on success. See the status codes table below for all possible values.

​
Status codes

Your response must be returned within 3 seconds. If the request times out or returns an error, we will not retry — a cancel callback will be sent instead to revert the game round. An unsuccessful bet also cancels the current round, preventing the player from proceeding further.

​
Examples