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

# Integration Review

The UOF Integration Program concludes with a technical review of your integration to ensure your usage of the UOF is suitable for connecting to the production environment. 

The purpose of the Integration review is to check if the basic logic for the processing of information is implemented, if the client has the knowledge needed to use our backend tools, and if the recovery logic is correctly implemented.

### Review Agenda <a href="#uofintegrationreview-reviewagenda" id="uofintegrationreview-reviewagenda"></a>

The following are checked during the review

* Review of client’s sports and markets coverage
* Review of client’s knowledge about Betradar interfaces (CTRL)
* Processing and performance of client’s service
  * Fixtures, odds, bet stop, settlements, rollbacks
* Disconnection handling and recovery
  * Blocking the connection from the Betradar side and observing the reaction of the client’s service

### Pre-requisites for the Review <a href="#uofintegrationreview-pre-requisitesforthereview" id="uofintegrationreview-pre-requisitesforthereview"></a>

* The client shall be provided with the integration review checklist, and make sure the process and the pre-requisites are understood
* The client should be able to present a proof-of-concept of their service
  * Data in the database (or the data storage that they use)
  * Client's front-end (if ready – preferred)\
    &#x20; SDK logs are not sufficient
* The client should be able to connect to integration and replay environments
  * &#x20;Integration of Live Odds: The client should book live matches
  * &#x20;Certification: The client should be able to connect to the replay environment and manipulate the Replay API

### **Review Checklist / Report** <a href="#uofintegrationreview-reviewchecklist-report" id="uofintegrationreview-reviewchecklist-report"></a>

The Client is asked to fill out the report PDF below with their comments and status.

{% file src="/files/gov4pHmqXK7YwShuydwP" %}

Screenshots, schemas, and other attachments can also be added.\
The checks that cannot be commented on and should be reviewed on live examples (e.g., disconnection handling) are reviewed in a screen-sharing session with the client, where the client presents their service.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/uof/introduction/integration-process/integration-review.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.