> 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/sandbox/using-transaction-3.0-sandbox.md).

# Using Transaction 3.0 Sandbox

### Welcome to Transaction 3.0 Sandbox

Integration with the Transaction 3.0 API is straightforward and efficient. The Transaction 3.0 Sandbox is the best environment to see the integration in action.

Please follow these steps to start using the Sandbox.

{% stepper %}
{% step %}

## Sign up for the Sandbox

Go to [MTS Integration Portal — Sandbox Provision](https://portal.mts-nonprod.sportradar.dev/).

<figure><img src="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FGg8ZBLsk9AMwBlaGFhn6%2FSandbox%20Request%20service%20account.png?alt=media&amp;token=28a231b1-0fd9-4a01-986d-ec79420e2cb3" alt=""><figcaption></figcaption></figure>

Fill in all the fields and read and accept the Privacy Notice.

You will receive a verification link to the email address you entered.&#x20;

<div align="left"><figure><img src="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FXFMV6qAVgtDRmzYKT64a%2FEmail%20confirmation.png?alt=media&amp;token=eec496d6-b7f9-4e90-a02f-e72ef2388ca0" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
Please note that the link is only valid for 30 minutes. If you miss this timeframe, you will need to visit <https://portal.mts-nonprod.sportradar.dev/> again and request your service account.
{% endhint %}
{% endstep %}

{% step %}

## Receive your credentials

Once you confirm your email address, you will receive your credentials and can start using the Sandbox.

You will receive a form similar to this one.

Store the client secret securely. It will not be displayed again in the Sandbox.

<figure><img src="https://754701251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk9SMFSuFGUx0b4iEHZ2f%2Fuploads%2FmYrgayKuWDShglSOnltm%2FSandbox%20Form%20received%20via%20email_2.png?alt=media&amp;token=09d126f3-24ad-4732-9ddb-ce04fb43fb98" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Get MBS SDK

To connect and run scenarios, you will use the MBS SDK that supports the Transaction 3.0 API.

You will download and install it from:

* [Java version](https://mvnrepository.com/artifact/com.sportradar.mbs.sdk/mbs-sdk)
* [.Net version](https://www.nuget.org/packages/Sportradar.Mbs.Sdk)
  {% endstep %}

{% step %}

## Obtaining the token and establishing a WebSocket connection

The Transaction 3.0 API uses a WebSocket connection.

Before establishing a connection, you will need to obtain the token. The [Connectivity page](https://docs.sportradar.com/transaction30api/sandbox/connectivity.md) explains how.

The SDK also supports setting up a WebSocket connection, and you will find instructions on the [User Manual page](https://docs.sportradar.com/transaction30api/sandbox/user-manual.md) for triggering it. In any case, you will need to provide the connection endpoints, which you will also find on the [Connectivity page.](https://sportradar.atlassian.net/wiki/spaces/LA/pages/373464622)
{% endstep %}

{% step %}

## Running scenarios and examining the results

Now you can run a scenario, which means composing a request using the SDK and examining the response the Sandbox returns. You will find details, along with links to specific scenarios, in the [User Manual](https://docs.sportradar.com/transaction30api/sandbox/user-manual.md)

More information about the [MTS features](https://docs.sportradar.com/mts/features/alternative-odds.md) and the [transaction structure](https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description.md) is available in the documentation.

{% hint style="warning" %}
Please note that the MTS Gate Sandbox is a simulation of MTS transaction processing. It does not connect to a real-time feed and does not return live market data. Instead, it returns deterministic, scenario-based responses: your request is matched to a documented sandbox scenario using specific routing fields, and the reply follows that scenario’s rules—not integration or production MTS behavior.
{% endhint %}
{% endstep %}

{% step %}

## Ready to move on to integration with MBS

Now that you are familiar with the MBS SDK and how Transaction 3.0 requests and responses are structured, you can continue integration with MBS in the integration environment.
{% endstep %}
{% endstepper %}


---

# 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/sandbox/using-transaction-3.0-sandbox.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.
