> 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/ads/tracking-specifications/odds-feed-integration-requirements.md).

# Odds Feed - Integration Requirements

Sportradar provides operators with marketing products to offer their audience more relevant & engaging betting experiences. Our ads can be used across programmatic (SR DSP included), social, and affiliate channels. We offer support for 23 sports, all major betting markets, and out-the-box content that provides relevant messaging for all customer types.&#x20;

#### **Requirements**

To allow us to integrate your XML/JSON odds feed, please share the following:

* Feed documentation
* Technical contact for any troubleshooting queries
* Deep-linking documentation for the feed
* Username and password if needed for access
* If whitelisting of our IPs  is needed, please do so for the following:
  * 35.240.70.112
  * 35.234.151.134<br>

In case you don't yet have a feed available, and are looking for a recommendation on how to build one, we offer a swagger specification of a rest API attached to this page below. It can be loaded via <https://editor-next.swagger.io/> to preview the endpoint requests and API responses.

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

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/77127327127/original/6Rh7SBIsvE93BiZY833dhB3tOiuwc12Q2g.png?1687173114)


---

# 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/ads/tracking-specifications/odds-feed-integration-requirements.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.
