> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description.md).

# 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](https://docs.sportradar.com/transaction30api/api-description/transaction-details-and-examples.md). 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](https://docs.sportradar.com/transaction30api/api-description/validation-codes.md) 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](https://docs.sportradar.com/transaction30api/api-description/json-schemas.md) 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 <client-integration-team@sportradar.com> 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](https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description/cash-out-description-and-flow/cash-out-requests.md) .

<figure><img src="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FumJtTnojOYCr65NCe3Yg%2F143524060.jpg?alt=media&amp;token=c5899e8b-ffa7-406f-bfa9-4f62c9d9d62b" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
