> 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/mts/api-sandbox-fast-track-to-mts-integration.md).

# API Sandbox - Fast Track to MTS Integration

✅ Check how easy it is to integrate with the MTS API using the [Transaction 3.0 Sandbox](/transaction30api/sandbox/using-transaction-3.0-sandbox.md).

✅ Polish your integration against the Sandbox before you continue integrating with MTS in the integration environment — same Java SDK, same WebSocket flow, same transaction structure.

✅ Start in minutes with OAuth + WebSocket connectivity, then iterate safely until your placement, cancellation, and settlement paths behave exactly as you expect in production.

✅ Build requests with the official MBS SDK and receive responses, then quickly focus on ticket content and error handling.

✅ Explore 30+ documented scenarios—promo stakes, alt odds, reoffer flows, liability and market rejects with Java examples, wire JSON, and expected responses.

<a href="https://portal.mts-nonprod.sportradar.dev/" class="button primary">Try Transaction 3.0 Sandbox now</a>


---

# 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/mts/api-sandbox-fast-track-to-mts-integration.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.