> 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/sdk/intro.md).

# Intro

**What is the UOF SDK?**

**Unified Odds Feed SDK** is a client library that enables easier integration with the [**Betradar**](http://www.betradar.com/) XML feeds. 

The SDK is available in Java and .NET programming languages. Both SDKs are developed similarly, even though there are some differences between them. Java is developed in Java Development Kit 8 and .NET version is developed using C# 6.0.

The Java SDK is available in the Maven Central repository, and the .NET version can be obtained via NuGet.

Some notable differences between the Java and .NET versions are as follows

* Java version uses a listener pattern (where applicable), whereas the .NET version uses events.
* The .NET version exposes asynchronous methods that may require a Sports API request, whereas Java uses synchronous methods.

#### Why UOF SDK? <a href="#uofsdk-whyuofsdk" id="uofsdk-whyuofsdk"></a>

The UOF SDK is a middleware service that speeds up and simplifies UOF integration for our customers by handling protocol details, unlike integrating with Sportradar or accessing the Unified Odds without the SDK.

SDK exposes the XML feed service interface in a more user-friendly way and isolates you, our client, from having to do XML feed parsing, proper connection handling, error recovery, event queuing, data caching, and dispatching. It also makes a client solution more stable and robust when it comes to feed handling, especially with the release of new and updated XML feed versions.

However, we support our clients using older versions.

#### SDK Benefits Over Protocol/API <a href="#uofsdk-sdkbenefitsoverprotocol-api" id="uofsdk-sdkbenefitsoverprotocol-api"></a>

The UOF SDK provides a simple and efficient way for bookmakers to access Betradar's odds and sports information. It combines message subscription and API calls into a unified Java or .NET interface that hides most of the complexity, including recovery.

*See* [*UOF - Access Methods*](/uof/introduction/access-methods.md) *section for more details.*

#### Quick Links <a href="#uofsdk-quicklinks" id="uofsdk-quicklinks"></a>

| Title              | UnifiedFeed SDK Java                                                    | UnifiedFeed SDK .NET Core                                     |
| ------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------- |
| Git repository     | <https://github.com/sportradar/UnifiedOddsSdkJava>                      | <https://github.com/sportradar/UnifiedOddsSdkNetCore>         |
| Package repository | <https://central.sonatype.com/namespace/com.sportradar.unifiedodds.sdk> | <https://www.nuget.org/packages/Sportradar.OddsFeed.SDKCore/> |
| Framework          | JDK 1.8                                                                 | .NET Standard 2.0                                             |


---

# 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/sdk/intro.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.