Ticket JSON Format Description

Communication between the client's system and MTS is based on exchanging JSON objects via the WebSocket protocol. To track the JSON object's lifecycle (e.g. introduction or deprecation of particular fields), MTS applies ticket versioning. The current ticket version is 3.0.

The following chapters describe the format of JSON objects or tickets in detail, including the practical meaning of particular fields, objects or arrays. Chapters are structured in a way that a request is described first and is followed by the description of its response. This is true for ticket placement, cancellation, cash-out, external settlements, and acknowledgement messages.

For better understanding, several examples are provided in Transaction Details and Examples. Examples are ordered based on the complexity of bet type: starting from simple cases and finishing with complex multi-system bets with different numbers of selections and different stakes per combination. It also provides examples of Acknowledgement messages and Acknowledgement reply messages.

Validation response (error) codes and their description are included on the Validation Codes page, whereas the response codes for cancellation, cash-out, and settlement responses are included in their respective chapters.

Additionally, to facilitate software development and integration on the client's side, formal JSON schemas are attached to the JSON Schemas page.

All examples and schemas are available as separate text files. If any of these are required, please get in touch with the MTS Client Integration team by email at [email protected] or via the MTS integration Skype/Slack channel.

The following diagram shows the operations and content types that occur in certain situations. For cash-out operations and content types, please see Cash-out Requests .