POST /transaction/rollback
Common causes includes
Server failure
Bet processed after the round started
Internal server errors
Invalid or incorrect data
A unique identifier associated with operator calling API.
A SHA256 HMAC signature generated using the request body and timestamp.
Format: HMAC_SHA256(JSON.stringify(data) + ’|’ + timestamp), signed using the
provided secret key.
An Unix timestamp (milliseconds) when the request was sent. Ensure the same
value is used in signature generation.
Must be set to application/json
Request Body The unique transaction identifier. An action with same transactionId shouldn’t be processed more than once.
An identifier of the transaction that this transaction is referencing. this field will contain transactionId of the transaction which needs to be rolled back, it can be any transaction like bet, payout etc.
An identifier for the player session in which this transaction happened.
Unique identifier for the player.
Unique identifier for the game.
Response Code indicates status of the request weather it is succeed or failed. We have listed error codes here Status of the individual transaction.
The unique transaction identifier.
curl --request POST \ --url 'https://partner-platform-url/transaction/rollback' \ --header 'content-type: application/json' \ --header 'x-api-key: <x-api-key>' \ --header 'x-signature: <x-signature>' \ --header 'x-timestamp: <x-timestamp>' \ --data '{ "transactions": [ { "transactionId": "21848853-1198-4dde-9a21-bb9598398a8c", "refTransactionId": "dd96bda3-9990-4aed-9679-f451a4b82ac4", "sessionId": "9f9ea8fd09face7f2b44c819665d09a32250e150c6e95c7d0ba9af774740c98w30041199695697d324efbe3ffc1e0a79", "playerId": "18865671", "gameId": "G1720761376617" } ] }'
{ "status" : "RS_OK" , "data" : [ { "status" : "RS_OK" , "transactionId" : "21848853-1198-4dde-9a21-bb9598398a8c" } ] }
