> 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/table-tennis/domain-url-changes.md).

# Domain URL Changes

This page covers the API/Websocket modifications as part of the enforced decommission of the imgarena.com and imgarena.dev domain urls by 30th September 2026. The new domain url will be srarena.io and will be made available in May 2026. This will also affect those users of the Data Console UI product (<https://data.console.imgarena.com/> and <https://ops-ui.dde-sims.imgarena.dev/>). The existing imgarena.com and imgarena.dev domains will operate in parallel until 30 September 2026

The direction of travel for consumption of data across the listed sports beyond 2026 will be to utilise this via the Sportradar [Live Data XML](https://docs.sportradar.com/live-data) or [Unified Odds Feed](https://docs.sportradar.com/uof) Platform and further details on that will be delivered in due course per sport.

Please see further information in the document below which is available to download on this URL domain changes.

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


---

# 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/table-tennis/domain-url-changes.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.
