> 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/streaming-integration/readme.md).

# Welcome to the IMG Arena Live Streaming Platform

## Domain Change Notification

{% hint style="warning" %}
Access to the Streaming API and all related endpoints moves to srarena.io. Existing sub-domains for Streaming API, Events API, Player API and Thumbnail API remain unchanged; only the domain “imgarena.com” will change to “srarena.io”. Please note that the URL to the Live Streaming Console will change as listed below. The existing imgarena.com domains will operate in parallel until 30 September 2026
{% endhint %}

| <https://api.livestreaming.imgarena.com>     | <https://api.livestreaming.srarena.io>     | <p>Streaming API,<br>Events API,<br>Player API,<br>Thumbnail API</p> |
| -------------------------------------------- | ------------------------------------------ | -------------------------------------------------------------------- |
| <https://console.livestreaming.imgarena.com> | <https://console.livestreaming.srarena.io> | Arena Live Streaming Console                                         |

The direction of travel for consumption of streaming across all sports beyond 2026 will be to utilize this via the Sportradar [AudioVisual Streaming](https://docs.sportradar.com/audiovisual/audiovisual-streaming.md) Platform.

## Learn how to integrate with the IMG Arena Streaming Exchange to stream thousands of live events every year.

This documentation provides an overview of the platform, how to use it, and how to get the most out of all our APIs.

If you have any questions whilst integrating, please contact the support team at <support@sportradar.com>, who will be happy to help.

### ​Key Information

{% content-ref url="/pages/2P8uwnXF6OGJGaUuTlaK" %}
[Arena Streaming Console](https://docs.sportradar.com/streaming-integration/ui-overview/arena-streaming-console.md)
{% endcontent-ref %}

{% content-ref url="/pages/7PVECa96zsbvkco5ovlX" %}
[Licenses & Event Booking Guide](https://docs.sportradar.com/streaming-integration/ui-overview/content-list/licenses-and-event-booking-guide.md)
{% endcontent-ref %}

## Key APIs

{% content-ref url="/pages/PRGrbqUCSUHQThyUxkm3" %}
[Events API](https://docs.sportradar.com/streaming-integration/apis/events-api.md)
{% endcontent-ref %}

{% content-ref url="/pages/CZTNOe9osFH6lJMLONRU" %}
[Streaming API](https://docs.sportradar.com/streaming-integration/apis/streaming-api.md)
{% endcontent-ref %}

## Key Integration Information

{% content-ref url="/pages/uLzZyp5bH3U4e2pu976N" %}
[Authentication Flow](https://docs.sportradar.com/streaming-integration/authentication/authentication-flow.md)
{% endcontent-ref %}

{% content-ref url="/pages/NdoyXchTpPTb5bUmX2x2" %}
[Common Authentication / Integration Issues](https://docs.sportradar.com/streaming-integration/faqs/common-issues.md)
{% endcontent-ref %}


---

# 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/streaming-integration/readme.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.
