> 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/uof/introduction/integration-process/sportsbook-testing.md).

# Sportsbook Testing

To get an even more detailed and in-depth test of your integration, we offer a free-of-charge **Sportsbook Test** which takes roughly two days to complete.&#x20;

It is designed to guarantee the best performance of our services within your domain and that all functionalities are working as intended within optimal conditions which will let you stand out against your competitors.&#x20;

We test the front end and back end including speed and performance, sport by sport, and stress your system by simulating a peak hour scenario to ensure your integration withstands any pressure that can occur.

**We** highly recommend considering our **UOF Sportsbook Test**, which is a great opportunity to test your backend-to-frontend integration, including the overall performance and betting implementation checks.

*Please note that the Sportsbook Test is mandatory when integrating our MTS product and is recommended to all customers integrating Unified Odds Feed.*


---

# 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/uof/introduction/integration-process/sportsbook-testing.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.
