> 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/readme.md).

# Transaction 3.0 API

The Transaction 3.0 API, based on WebSocket technology, allows client systems to seamlessly interact with Sportradar's Managed Betting Services (MBS) suite.

It terms of trading and risk management, it enables communication with [Managed Trading Services (MTS)](https://docs.sportradar.com/mts/). Clients receive bets from their end customers, send them over to MTS, and expect a concrete and timely suggestion on whether a particular bet should be accepted. Messages involved in this interaction typically include Ticket Placement, Cash-out, Cancellation Requests and Responses, and similar.

When products aimed to elevate responsible gaming are used, such as [Bettor Sense](https://docs.sportradar.com/bettor-sense/), Responsible Gaming Requests and Responses will include information related to this type of service.

[Gaming and Casino products ](https://docs.sportradar.com/games/)require the exchange of another type of information, which is contained in Casino Sessions Requests and Responses and Payment Requests and Responses.

### Contact us

If you have any **questions or queries**, please contact:\
:envelope: <support@sportradar.com>

For any **sales related queries**, please contact your sales representative or email:\
:envelope: <sales@sportradar.com>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>API Integration Manual</h4></td><td>This section contains information on how to execute the API integration process, the role of the Client Integration and Operational Account Management teams, and more.</td><td><a href="https://docs.sportradar.com/transaction30api/api-integration-manual/introduction.md">api integration manual</a></td><td><a href="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FCaZnRRwNlLG9xnQanr4Y%2Fbox-cover-api-integration-manual.png?alt=media&amp;token=9fbcf8e4-70f2-4c13-8bb0-5d9bd9102a8e">box-cover-api-integration-manual.png</a></td></tr><tr><td><h4>API Description</h4></td><td>Here you will find a list of connectivity parameters, message flows, description of message JSON objects, schemas, and more.</td><td><a href="https://docs.sportradar.com/transaction30api/api-description/introduction.md">api description</a></td><td><a href="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2F1lgqEJMGNRTU9VVkWFpx%2Fbox-cover-api-description.png?alt=media&amp;token=dc90be83-7e94-4749-b1ab-43bc50ac3f2b">box-cover-api-description.png</a></td></tr><tr><td><h4>SDK</h4></td><td>This client library streamlines the integration of the Sportradar API into a client’s system.</td><td><a href="https://docs.sportradar.com/transaction30api/sdk/transaction-3.0-sdk.md">sdk</a></td><td><a href="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FDilgrYx87PCqq32nPEZZ%2Fbox-cover-sdk.png?alt=media&amp;token=abd4ff5a-9a80-4392-ae33-b650a5ae94ae">box-cover-sdk.png</a></td></tr></tbody></table>


---

# 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/readme.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.
