Acknowledgement Reply Messages

Destination		Source
Client	←	MTS

Envelope and Content table:

The envelope provides the Content's (Acknowledgement reply message) 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": "623dHlyMq82",	correlationId	Client defined string to facilitate the request-response pairing, Sportradar is obliged to return the same string in every response	M	String
"timestampUtc": 1678357236000,	timestampUtc	Timestamp of ticket placement as submitted by the client (Unix time milliseconds format), minimal: 1, maximum: 9223372036854776000	M	Integer
"operation": "ticket-placement-ack",	operation	In case of Acknowledgement reply messages - enumerator: "ticket-placement-ack" "ticket-cancel-ack" "ticket-cashout-ack" "ticket-ext-settlement-ack"	M	String
"version": "3.0"	version	Indicates the ticket format version	M	String
}

Content object (Acknowledgement reply message)

This object constitutes the reply message itself and includes the following fields:

• type

• cancellationId or cashoutId or settlementId (depends on Acknowledgement reply message type)

• signature

• status

• ticketId

• 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":"*-ack-reply. For description see Error-reply Response.

Content object table

Example	Field Name	Field Description	Mandatory/Optional	Data Type
"content": {				Object
"type": "ticket-ack-reply",	type	Declaration of content type, enumerator: ticket-ack-reply cancel-ack-reply cashout-ack-reply ext-settlement-ack-reply Type relates to envelope's "operation" field Each of the above types can be replaced with "type": "error-reply" in the case of major ticket errors or internal system errors (see also Error-reply Response).	M	String
"cancellationId": "CANC8787414",	cancellationId or cashoutId or settlementId	"type": "ticket-ack-reply" → field is omitted, "type": "cancel-ack-reply" → cancellationId, "type": "cashout-ack-reply" → cashoutId, "type": "ext-settlement-ack-reply" → settlementId	M except for "type": "ticket-ack-reply"	String
"signature": "CLflbr+1eMqoks73z rNhwVimGF1Yo8CitmWYH4g5zwI=",	signature	String calculated and sent by MTS to be used as a proof that the reply has actually been provided by MTS, minimal string length = 1, maximum string length = 128	M	String
"status": "accepted",	status	Request outcome, enumerator: accepted rejected	M	String
"ticketId": "Ticket_3690",	ticketId	ID of the initial ticket (defined by client)	M	String
"code": 0,	code	Ack. reply code, see list of codes below	M	Integer
"message": "Transaction processed"	message	Readable ticket response validation code, minimal string length = 1, maximum string length = 128	O	String
}

Acknowledgement reply codes:

Code	Description
0	Transaction processed
-101	Client (bookmaker) not found
-103	Ticket not found