Pre-validated Ticket Placement Request

Source		Destination
Client	→	MTS

This type of ticket placement contains bets that do not require any validation on Sportradar's side. The bets have been validated on the client's side, and information about this is passed over in the Bet Validation object (see below).

To respond to it, Insight Tech / MTS sends a Pre-validated ticket placement response containing "operation": "ticket-placement-inform" and the content including "type": "ticket-inform-reply". The "status" can be either "accepted" or "rejected" according to the status reported by the client in the betValidations' code field.

With this type of request, only the validation process on the Sportradar's side is skipped. The ticket still requires a proper settlement.

Envelope and Content table:

The envelope provides the Content's (Pre-validated ticket placement request) context and contains the following fields (besides Content):

• operatorId

• correlationId

• timestampUtc

• operation

• version

Example	Field Name	Field Description	Mandatory/Optional	Data Type
{
"operatorId": 9985,	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": {	content	See Content object description below	M	Object
...........
...........
},
"correlationId": "62ka01mxre",	correlationId	Client defined string to facilitate the request-response pairing, Sportradar is obliged to return the same string in every response	M	String
"timestampUtc": 1689752903000,	timestampUtc	Timestamp of ticket placement as submitted by the client (Unix time milliseconds format), minimal: 1, maximum: 9223372036854776000	M	Integer
"operation": "ticket-placement-inform",	operation	Declaration of ticket content type, should be "ticket-placement-inform" in the case of a Pre-validated ticket placement request	M	String
"version": "3.0"	version	Indicates the ticket format version	M	String
}

Content object (Pre-validated ticket placement request)

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

• type

• ticketId

• bets

• context

• betValidations

Content object table:

Example	Field Name	Field Description	Mandatory/Optional	Data Type
"content": {				Object
"type": "ticket-inform",	type	Declaration of content type, should be "ticket-inform" in the case of a Pre-validated ticket placement request	M	String
"ticket": {	ticket	This field corresponds to the content object of the original ticket placement request, for syntax, see the content object description (of the Ticket placement request)	M	Object
"type: "ticket",
"ticketId: "Ticket_10150",
...............
...............
},
"betValidations": [	betValidations	Bet validation information as provided by the client, minimal number of bets per content (ticket) = 1, maximum number = 50	M	Array
{
"betId": "Ticket_10150_bet0",	betId	Unique bet id (in the client's system), minimal string length = 1, maximum length = 128	O	String
"code": 1100,	code	Bet validation information as provided by the client, minimum = 0, maximum = 10000	M	Integer
"message": "Prevalidated, OK",	message	Readable bet validation code as provided by the client, minimal string length = 1, maximum string length = 128	O	String
"rejected": false	rejected	Clients' indication if the bet has been rejected on the client side (missing field means not rejected)	O	Boolean
}
]
}