Casino Sessions Response

Destination		Source
Client	←	MTS

Envelope and Content table:

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

• correlationId

• timestampUtc

• operation

• version

Example	Field Name	Field Description	Mandatory/ Optional	Data Type
{
"content": { ....... ....... },	content	See Content object description below	M	Object
"correlationId": "kL20vAyh",	correlationId	Client defined string to facilitate the request-response pairing, Sportradar is obliged to return the same string in every response	M	String
"timestampUtc":1703852996000,	timestampUtc	Timestamp of ticket placement as submitted by the client (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000	M	Integer
"operation": "casino-sessions-inform",	operation	Declaration of operation type, should be "casino-sessions-inform" in the case of a Casino sessions response	M	String
"version": "3.0"	version	Indicates the ticket format version	M	String
}

Content object (Casino sessions response)

The Content object includes the following fields:

• type

• code

• message

Please note that in the case of major ticket errors or internal system errors the content object has a different structure and contains "type": "error-reply" instead of "type": "cashout-reply. For description, see Error-reply Response.

Content object table:

Example	Field Name	Field Description	Mandatory/ Optional	Data Type
"content": {				Object
"type": "casino-sessions-inform-reply",	type	Declaration of content type, should be "casino-sessions-inform-reply" in the case of a Casino sessions response or "error-reply" in the case of major ticket errors or internal system errors (see also Error-reply Response).	M	String
"code": 0,	code	Response code	M	Integer
"message": "Transaction processed" },	message	Readable response code description, minimal string length = 1, maximum string length = 128	M	String