> 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.
#### **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
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 to preview the endpoint requests and API responses.
{% file src="/files/piAM8t8YwmxTR513y9wU" %}
---
# 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/ads/tracking-specifications/odds-feed-integration-requirements.md?ask=&goal=
```
`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.