⬆️ POST /v1/integration/casino

RabbitMQ Message Properties

key value

key

value

type

CASINO

The type is expected as a property (but not in the payload) of the RabbitMQ Message. Any header will be ignored.

Kafka Message Headers

key value

key

value

type

CASINO

Send each Bet and Win event separately.

If you are planning on sending "RollbackBet" & "RollbackWin" as "type", please inform your integration manager.

Sample Request for initial "Bet" event

Key Type Required? Accepted Values Description

Key

Type

Required?

Accepted Values

Description

activity_id

string

Yes

N/A

amount

float

No

N/A

Amount

balance_after

float

No

N/A

Player balance after

balance_before

float

No

N/A

Player balance before

bonus_wager_amount

float

No

N/A

Bonus amount wagered

currency

string

Yes

Format: ISO 4217

e.g. EUR

Player currency

exchange_rate

float

Yes

e.g. 0.1

Exchange rate

game_id

string

Yes

N/A

Game id

game_name

string

No

e.g. Dead or Alive

Game name

game_type

string

No

Slots, Live Casino, Table

Game type

is_round_end

boolean

No

true/false

If the round is ended

locked_wager_amount

float

No

N/A

Locked amount wagered

origin

string

Yes

e.g. www.brand.com

N/A

round_id

string

No

N/A

Round id

timestamp

string

Yes

Format: RFC3339 2015-03-02T8:27:58.10Z

Timestamp

type

string

Yes

"Bet", "Win", "RollbackBet", "RollbackWin"

Type of event

user_id

string

Yes

N/A

User id

vendor_id

string

Yes

N/A

Vendor id

vendor_name

string

No

e.g. NetEnt

Vendor name

wager_amount

float

No

N/A

Amount wagered

meta

object

No

{ "key1": "value1", "key2": "value2" }

Used for misc/aux values that is brand specific