Casino: Bet / Win Events

Casino events are ideally sent on the FT CRM Integration API when Operator works with a casino product.

♣️ Real-Time Events You Can Send

FT CRM will process the raw data feed of events and construct game rounds, game sessions and relevant segmentation data based on this.

RabbitMQ Connector

RabbitMQ Message Properties

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 Connector

Kafka Message Headers

type	CASINO

REST API

⬆️ POST /v1/integration/casino

Send each Bet and Win event separately.

If you are planning on sending "Rollback" as "status", please inform your integration manager.

Example Payload - Bet

{
  "activity_id": "2019020103308257480",
  "amount": 20,
  "balance_after": 174.03,
  "balance_before": 194.03,
  "bonus_wager_amount": 0.0,
  "currency": "EUR",
  "exchange_rate": 1,
  "game_id": "10911",
  "game_name": "Dead or Alive",
  "game_type": "Slots",
  "is_round_end": false,
  "locked_wager_amount": 0.00,
  "origin": "sub.example.com",
  "round_id": "2019020103308257480",
  "status": "Approved",
  "timestamp": "2015-03-02T8:27:58.721607Z",
  "type": "Bet",
  "user_id": "52530",
  "vendor_id": "1",
  "vendor_name": "Netent",
  "wager_amount": 20,
  "meta":{
		"key1": 10.00,
		"key2": "some string",
		"key3": false
	}
}	

Example Payload - Win

{
  "activity_id": "2019020103308257481",
  "amount": 5,
  "balance_after": 195.83,
  "balance_before": 190.83,
  "bonus_wager_amount": 0.0,
  "currency": "EUR",
  "exchange_rate": 1,
  "game_id": "10911",
  "game_name": "Dead or Alive",
  "game_type": "Slots",
  "is_round_end": true,
  "locked_wager_amount": 0.00,
  "origin": "sub.example.com",
  "round_id": "12345",
  "status": "Approved",
  "timestamp": "2015-03-02T8:27:58.721607Z",
  "type": "Win",
  "user_id": "52530",
  "vendor_id": "1",
  "vendor_name": "Netent",
  "wager_amount": 5,
  "meta":{
		"key1": 10.00,
		"key2": "some string",
		"key3": false
	}
}

Data Type

{
  "activity_id": "string",
  "amount": float,
  "balance_after": float,
  "balance_before": float,
  "bonus_wager_amount": float,
  "currency": "string",
  "exchange_rate": float,
  "game_id": "string",
  "game_name": "string",
  "game_type": "string",
  "is_round_end": boolean,
  "locked_wager_amount": float,
  "origin": "string",
  "round_id": "string",
  "status": "string",
  "timestamp": "date", // RFC3339 format
  "type": "string",
  "user_id": "string",
  "vendor_id": "string",
  "vendor_name": "string",
  "wager_amount": float,
  "meta":{
	    "key": "value"
	}
}

amount = wager_amount + bonus_wager_amount + locked_wager_amount

Required properties are marked with *

Key	Example Value	Description
activity_id *	"2019020103308257480"	Unique ID for each event
amount *	20	The total amount (bonus_wager_amount + wager_amount + locked_wager_amount)
balance_after	174.03	Player balance after the round is finished
balance_before	194.03	Player balance before the round started
bonus_wager_amount	0	Amount (either bet or win) if the round was played using bonus money
currency *	"EUR"	Transactions currency in ISO 4217 format
exchange_rate *	1	Exchange rate
game_id *	"10911"	Game ID
game_name *	"Dead or Alive"	Game Name
game_type	"Slots"	Game Type as defined in the platform
is_round_end *	false	Is the round ended?
locked_wager_amount	0	Amount (either bet or win) if the round was played using money from a "locked" wallet (when bonus and real money is combined)
origin *	"sub.example.com""
round_id *	"2019020103308257480"	Send same for Bet & Win
status *	"Approved"	Approved, Rollback. Indicates whether the event should be reversed or not
timestamp *	"2015-03-02T8:27:58.721607Z"	Timestamp in RFC3339 format
type *	"Bet"	Either "Bet" or "Win"
user_id *	"52530"	The user id
vendor_id *	1	Vendor Id
vendor_name *	"Netent"	Vendor Name
wager_amount	20	Amount (either bet or win) if the round was played using real money.
meta	{ "key1": "value1", "key2": "value2" }	Used for misc/aux values that is brand specific