> 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/sports-data-api/sports-data-api.md).

# Sports Data API

Our Sports Data API delivers the industry’s most comprehensive coverage, spanning 80+ sports, 500+ leagues, and more than 750,000 events every year. Built for speed and efficiency, the feeds provide real-time stats and world-leading odds in easy-to-consume JSON and XML formats. From traditional box scores to advanced player tracking, every datapoint is verified and delivered with unmatched accuracy.&#x20;

Our APIs are tailormade to help you build your next great fan app, media platform or betting product. Explore live demos and start a free 30-day trial to see how simple it is. Visit the documentation [here](https://developer.sportradar.com/getting-started/docs/get-started).&#x20;

&#x20;<a href="https://console.sportradar.com/signup" class="button primary">Sign Up For Free Trials</a>    &#x20;


---

# 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/sports-data-api/sports-data-api.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.