> 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-program.md).

# Integration Program

The details of Our integration Program sprint-wise is available here.

<figure><img src="/files/2pzwZR4Ue0vxuyBTsCaV" alt=""><figcaption><p>Integration Program sprint wise</p></figcaption></figure>

{% stepper %}
{% step %}
**Sprint 1**

* Kick-off call
* Review documentation
* Training sessions on CTRL interface and technical aspects of UOF.
* Configure CTRL templates
* CTRL configuration of the basic sports and markets.&#x20;
* First Connection to the UOF
* [Subscribe to Ctrl Status Page](/uof/introduction/integration-process/important-notifications.md).
  {% endstep %}

{% step %}
**Sprint 2**

* Focus on the data obtained from the API and received in the feed
* Import sports, categories, tournaments
* Import markets and mappings (if required)
* Implement logic for basic feed messages: Fixture change, Odds change, Bet stop, Bet settlement
  {% endstep %}

{% step %}
**Sprint 3**

* Implement logic for Special case messages (Rollback bet settlement, Bet cancel, Rollback bet cancel)
* Transition from pre-match to live (i.e. handover of markets
* Disconnection handling
* Failure recovery handling
* Optional: initiate discussions about Betradar certification and MTS integration
  {% endstep %}

{% step %}
**Sprint 4**

* Add additional sports and markets
* Support outright markets if required
* Producer 4 integration (for MTS clients)
* Check corner cases
* Debug, fine tune the configurations and preferences
* Prepare for integration review and optionally for certification
  {% endstep %}
  {% endstepper %}

[**Integration Review**](/uof/introduction/integration-process/integration-review.md)


---

# 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-program.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.