# 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="/pages/Jdhfo32nsanmEpeC0UKB">/pages/Jdhfo32nsanmEpeC0UKB</a></td><td><a href="/files/JmF62jM07Fqe8UXbUHhB">/files/JmF62jM07Fqe8UXbUHhB</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="/pages/53qLXe1o2zNYur5pFq57">/pages/53qLXe1o2zNYur5pFq57</a></td><td><a href="/files/Fa4kVQspZrHPgWFm6ur3">/files/Fa4kVQspZrHPgWFm6ur3</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="/pages/ymx8AVWcDwTKSps7wisL">/pages/ymx8AVWcDwTKSps7wisL</a></td><td><a href="/files/07d2qGjuZAuZJQCmJQZg">/files/07d2qGjuZAuZJQCmJQZg</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/transaction30api/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.