# Overview

This section details the most important information when working with the unified odds API.

### Self-service Documentation <a href="#uofapi-self-servicedocumentation" id="uofapi-self-servicedocumentation"></a>

All endpoints are available for testing purposes at [http://iodocs.betradar.com](http://iodocs.betradar.com/). From there you can see each of the endpoints, execute the requests, and see sample responses as long as you have an access-token (see below - authentication)

### API Authentication <a href="#uofapi-apiauthentication" id="uofapi-apiauthentication"></a>

To access the API, you must visit [Betradar.com](http://www.betradar.com/) and generate an application key associated with your [Betradar.com](http://www.betradar.com/) user details. This API key has to be sent as an HTTP header on every request towards the service on the following format:

```json
x-access-token: <access token> 
```

> If you already have a Unified Odds Feed access token, please use the same to authorize your API access

**Info**

Our endpoints are backed by Content Delivery Network (CDN) solution to ensure low latency from geographically distributed locations. The DNS names ([mq.betradar.com](http://mq.betradar.com/), [api.betradar.com](http://api.betradar.com/), [global.mq.betradar.com](http://global.mq.betradar.com/) and [global.api.betradar.com](http://global.api.betradar.com/)) will point to a set of IP addresses, and those IP addresses can change from time to time without prior notice.

*If you currently whitelist our IP for outgoing traffic, we can not supply you with a fixed set of IPs for this, as they can change from time to time and without prior notice.*

### XSD Schemas <a href="#uofapi-xsdschemas" id="uofapi-xsdschemas"></a>

{% file src="/files/C0ZyoiGFWDTUVQphSyhX" %}
XSD schema for [api responses](https://sportradar-unifiedfeed.s3.eu-central-1.amazonaws.com/UnifiedFeedResponse.xsd)&#x20;
{% endfile %}

{% file src="/files/P11MFsvPMRZTIJUMWtU7" %}
XSD schema for [sportsapi responses](https://sportradar-unifiedfeed.s3.eu-central-1.amazonaws.com/sports_api_xsds.zip)
{% endfile %}

### Token Result Codes <a href="#uofapi-tokenresultcodes" id="uofapi-tokenresultcodes"></a>

<table data-header-hidden><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Token</strong></td><td><strong>HTTP Response Code</strong></td><td><strong>Description</strong></td></tr><tr><td>Valid token provided</td><td><pre><code>200
</code></pre></td><td><pre><code>OK
</code></pre></td></tr><tr><td>No token provided</td><td><pre><code>400
</code></pre></td><td><pre><code>Bad Request
</code></pre></td></tr><tr><td>No token provided</td><td><pre><code>401
</code></pre></td><td><pre><code>Inauthorized
</code></pre></td></tr><tr><td>Unknown Token</td><td><pre><code>404
</code></pre></td><td><pre><code>Not found
</code></pre></td></tr><tr><td>Expired token</td><td><pre><code>403
</code></pre></td><td><pre><code>Forbidden: “Error: Token is not valid,
perhaps it has expired?”
</code></pre></td></tr><tr><td>UF Package Missing</td><td><pre><code>403
</code></pre></td><td><pre><code>Forbidden: “Error: Bookmaker &#x3C;id> 
does not have access to unified feed”
</code></pre></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/uof/api-and-structure/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.