Casino Sessions Request

Source
Destination

Client

→

MTS

This request contains information about online gaming events and their outcomes. The information includes elements such as: end customer identification, channel, game type, game provider, game progress, stake, payout, timestamps, etc. The data collected helps MTS maintain a profile of the end customer, which in turn enables MTS's clients to conduct automated marketing campaigns, analyse their services, manage end customer churn and more.

Envelope and Content table:

The Envelope provides the content's (Casino sessions request) context and contains the following fields (besides Content):

  • operatorId

  • correlationId

  • timestampUtc

  • operation

  • version

Example
Field Name
Field Description
Mandatory/ Optional
Data Type

operatorId

ID to uniquely identify the client from which the ticket originated, ID is provided to the client by Sportradar, The client is obliged to include it in every ticket

M

Integer

content

See Content object description below

M

Object

correlationId

Client defined string to facilitate the request-response pairing, Sportradar is obliged to return the same string in the corresponding response

M

String

timestampUtc

Timestamp of ticket placement as submitted by the client (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000

M

Integer

operation

Declaration of operation type, should be "casino-sessions-inform" in the case of a Casino sessions request

M

String

version

Indicates the ticket format version

M

String

}

Content object (Casino sessions request)

This object constitutes the ticket itself and contains the following fields:

  • type

  • reportId

  • sessions (array)

  • context

Content object table:

Example
Field Name
Field Description
Mandatory/ Optional
Data Type

Object

type

Declaration of content type, should be "casino-sessions-inform" in the case of a Casino sessions request

M

String

reportId

Client defined string to identify the report (unique in the client's system), minimal string length = 1, maximum string length = 128

O

String

sessions

See description of the sessions array below, minimal number of sessions (array elements) per content (request) = 1, maximum number = 50

M

Array

context

Additional information related to the request

M

Object

  • channel

Specifies the means of delivery of service to client's end customers (bettors), also called distribution channel

M

Object

    • type

Declaration of channel type, enumerator:

  • agent

  • call-centre

  • internet

  • mobile

  • mobile-app

  • phone (used for USSD betting - USSD is a communication protocol in mobile networks)

  • retail

  • sms

  • terminal

  • tv-app

M

String

    • ip

IP address of the end customer's device

May be present only if "type": "internet" or "type": "mobile" or "type": "mobile-app" or "type":" tv-app"

M

if "type": "internet" , "type": "mobile" , "type": "mobile-app" , "type":" tv-app"

String

    • deviceId

ID of the end customer's device

May be present only if "type": "mobile" or "type": "tv-app" or "type": "internet" or "type": "retail" or "type": "sms"

Minimal string length = 1, maximum length = 36, allowed characters : uppercase and lowercase letters, numerals, #, :, -, _, \ Java regex: ^[0-9A-Za-z#:\\-_]{1,36}$

O

String

    • shopId

ID of the shop

May be present only if "type": "retail" or "type": "terminal"

Minimal string length = 1, maximum length = 36, allowed characters : uppercase and lowercase letters, numerals, #, :, -, _, \

M if "type": "retail" or "type": "terminal"

String

    • terminalId

May be present only if "type": "terminal"

Minimal string length = 1, maximum length = 36, allowed characters : uppercase and lowercase letters, numerals, #, :, -, _, \

M if "type": "terminal"

String

    • lang

End customer's user interface language code according to ISO 639-1 (string length = 2)

May be present only if "type": "internet" or "type": "mobile" or "type": "mobile-app" or "type": "terminal" or "type": "tv-app"

M

if "type": "internet" , "type": "mobile" , "type": "mobile-app" , "type": "terminal" , "type": "tv-app"

String

  • endCustomer

Data about client's end customer (bettor), it can only be omitted if the bet is placed by an unregistered bettor in retail or on a terminal

M

Object

    • id

End customer's unique ID (in client's system). It should be an anonymous value which cannot be used to identify a physical person. minimal string length = 1, maximum length = 36, allowed characters are : uppercase and lowercase letters, numerals, #, :, -, _, \ Java regex: ^[0-9A-Za-z#:\\-_]{1,36}$

M

String

    • confidence

End customer's suggested CCF Java regex: ^\\d{1,8}(\\.\\d{1,8})?$

O

String

  • walletId

Client defined string to identify the wallet (ID or type), minimal string length = 1, maximum string length = 128

O

String

Sessions array

The sessions array elements convey information about the actual casino sessions. They consist of the following fields:

  • id

  • game

  • startUtc

  • endUtc

  • spins

  • stake

  • payout

Sessions array table:

Example
Field Name
Field Description
Mandatory/ Optional
Data Type

Array of casino sessions, minimal number of elements per content (request) = 1, maximum number = 50

M

Array

id

Unique casino session id (in the client's system), minimal string length = 1, maximum length = 128

O

String

game

M

Object

  • id

Unique casino game id (in the client's system), minimal string length = 1, maximum length = 128

M

String

  • provider

Casino game provider identifier (in the client's system), minimal string length = 1, maximum length = 128

M

String

startUtc

Timestamp of start of the game (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000

O

Integer

endUtc

Timestamp of end of the game (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000

O

Integer

spins

Array of casino game spins, minimal number of spins per session =1, maximum number = 5

O

Array

  • type

Spin type, enumerator:

  • ordinary

  • bonus

M

String

  • count

M

Integer

  • winningCount

O

Integer

stake

Array of session stakes, minimal number of stakes per session =1, maximum number = 5

M

Array

  • type

Stake type, enumerator:

  • cash (used for stake and payout)

  • bonus (amount added on top of end customer's winnings in case a bet is won )

M

String

  • currency

Currently MTS does not support multiple sessions with stakes in different currencies,

See description

M

String

  • amount

See description

M

String

  • mode

Stake mode enumerator (default = total):

  • unit - stake amount relates to each sub-bet (a sub-bet is one combination (in case of system bets))

  • total - stake amount relates to all sub-bets (each sub-bet receives a portion of the amount)

O

String

  • traceId

A string to help identify the source of operation/action/state

Minimal string length = 1, maximum length = 128,

O

String

payout

Session payout array, minimal number of payouts per session =1, maximum number = 5

M

Array

  • type

Enumerator:

  • cash

  • withheld

M

String

  • currency

3 or 4 letter currency code, BTC and mBTC are also supported (4 letters only apply to mBTC). For more details please check https://www.iso.org/iso-4217-currency-codes.html

M

String

  • amount

String pattern: 1 up to 8 digits, optionally followed by a decimal point and 1 up to 8 digits, Java regex: ^\\d{1,8}(\\.\\d{1,8})?$

M

String

  • traceId

A string to help identify the source of operation/action/state

Minimal string length = 1, maximum length = 128,

O

String

Last updated

Was this helpful?