Skip to main content
curl --request POST \
  --url 'https://partner-platform-url/transaction/bet' \
   --header 'content-type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-signature: <x-signature>' \
  --header 'x-timestamp: <x-timestamp>' \
  --data '{
    "transactionId": "1db4fac5-34b2-4b81-a101-c105979633e0",
    "sessionId": "f1dfc865-584c-4cba-a175-06172b2a41141731504451691",
    "playerId": "18865671",
    "gameId": "G1720767064793",
    "currency": "EUR",
    "amount": 50000000,
}

{
  "status": "RS_OK",
  "transactionId": "1db4fac5-34b2-4b81-a101-c105979633e0",
  "balance": 500000000
}

  POST  /transaction/bet

​
Functionality

This API updates the player’s balance by:
  • The Operator is expected to debit the player’s balance by the given betAmount.
  • Each bet must include a unique transactionId, which the Operator must check before processing. If a transaction with the same ID has already been handled, no changes should be made and the cached result should be returned to avoid duplicates.
Finally, it returns the updated balance.

​
Headers

​
x-api-key
string
required
A unique identifier associated with operator calling API.
​
x-signature
string
required
A SHA256 HMAC signature generated using the request body and timestamp. Format: HMAC_SHA256(JSON.stringify(data) + ’|’ + timestamp), signed using the provided secret key.
​
x-timestamp
string
required
An Unix timestamp (milliseconds) when the request was sent. Ensure the same value is used in signature generation.
​
content-type
string
required
Must be set to application/json

​
Request Body

​
transactionId
string
required
The unique transaction identifier. An action with same transactionId shouldn’t be processed more than once.
​
sessionId
string
required
A unique identifier for the session.
​
playerId
string
required
The unique identifier for the player.
​
gameId
string
required
The unique identifier for the game.
​
currency
string
required
Player’s current session currency code.
​
amount
number
required
The amount the player bets.
To maintain precision and avoid floating-point errors, the amount field is processed as an integer value by multiplying the actual amount by 100000.For example, a amount of 12.34567 will be represented as 1234567 in the API.

​
Response

​
status
string
required
Code indicates status of the request weather it is succeed or failed. We have listed error codes here
​
transactionId
string
required
An ID of an action that is generated for each of our calls to the Operator, used to sync OppiGame and Operator sides for debugging purposes. The Operator has to respond with the same transactionId as the one received in request.
​
balance
number
required
The updated balance of the player.
To maintain precision and avoid floating-point errors, the balance field is processed as an integer value by multiplying the actual amount by 100000.For example, a balance of 12.34567 will be represented as 1234567 in the API.
curl --request POST \
  --url 'https://partner-platform-url/transaction/bet' \
   --header 'content-type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-signature: <x-signature>' \
  --header 'x-timestamp: <x-timestamp>' \
  --data '{
    "transactionId": "1db4fac5-34b2-4b81-a101-c105979633e0",
    "sessionId": "f1dfc865-584c-4cba-a175-06172b2a41141731504451691",
    "playerId": "18865671",
    "gameId": "G1720767064793",
    "currency": "EUR",
    "amount": 50000000,
}

{
  "status": "RS_OK",
  "transactionId": "1db4fac5-34b2-4b81-a101-c105979633e0",
  "balance": 500000000
}