> 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-integration-manual/introduction.md). # Introduction Technical integration with Managed Trading Services is performed together with one of MTS Client Integration (CI) engineers using a permanent communication channel e.g., Skype or Slack. During the integration phase, the MTS functionality and risk limit configuration will be carried out by the MTS Operational Account Management (OAM) team representatives to ensure the ideal settings are put in place. MTS integration flow in its current form is explained in the Integration flow section. MTS is a Sportradar service based on the [Unified Odds Feed](https://docs.sportradar.com/uof/) (UOF) which provides risk management for both traditional sports and e-sports. Communication between the operator’s backend and the MTS backend is based on asynchronous AMQP communication. JSON objects are used for this communication. In case you are using a Java or .NET backend, it is recommended to use the [Transaction 3.0 SDK](/transaction30api/sdk/transaction-3.0-sdk.md) (Software Development Kit): Ticket acceptance flow is mentioned in [this section](/transaction30api/api-description/ticket-acceptance-flow.md). To get introduced to the MTS ticket format, it is recommended to review the [examples](/transaction30api/api-description/transaction-details-and-examples.md). Detailed JSON format of MTS messages are mentioned in [this](/transaction30api/api-description/json-schemas.md) section. All Bet acceptance codes, examples of bets, bet cancelations, cash-out requests and JSON schemas are mentioned in the appendixes of this document and are available as separate .txt/.json files. **After launch support:** 48 hours after the *go live*, the client is handed over to Sportradar's support structure to guarantee the best possible service. Our support teams work out of a ticketing system, so all e-mails sent to will be routed through there and monitored 24/7/365. After emailing our team, the subject line will be appended with a unique ticket number. This may be helpful for future reference when following up on issues or questions. All business relevant communication regarding MTS operations will be handled by a dedicated MTS Operational Account Manager (OAM). In case of off-hours, you can address any issues to [mts-client-management@sportradar.com](mailto:MTS-Client-Management@sportradar.com). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sportradar.com/transaction30api/api-integration-manual/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.