> 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/live-data/introduction/replay-server.md).

# Replay Server

In order to facilitate testing and integration of the scout XML feed, we have set up a replay server which can be used to replay real matches from the past.

Connection details for the replay server:\
Hostname: [replay.livedata.betradar.com](http://replay.livedata.betradar.com/)\
Port: 2047 (SSL)

Communication with the replay server is identical to communication with the live server, except for two extra optional attributes for match subscription. In order to start replay of a match, simply subscribe to it as you would on the live server:

**XML example**

```xml
<match matchid="944423" />
```

This will send out a full feed for the match, and then update messages will follow in the same pace as they were sent out live. On the replay server you can also include the optional attributes messagedelay and startmessage in the match subscription XML.

**XML example**

```xml
<match matchid="944423" messagedelay="150" startmessage="25" />
```

***XML attributes and definition***

| Element        | Attributes                                                                                                                                                                                                                       |                                                        |                 |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | --------------- |
| <p><br></p>    | Attribute                                                                                                                                                                                                                        | Description                                            | Possible values |
| match          | *matchid*                                                                                                                                                                                                                        | The id of the match for which the replay should start. | Integer         |
| *startmessage* | Optional attribute. Start at this message number. If startmessage is greater than or equal to the number of messages for the match, a full feed for the finished match is sent out, and no more messages will follow after this. | Integer                                                |                 |
| *messagedelay* | Optional attribute. The amount of milliseconds between messages. This can be used to speed up the replay of a match.                                                                                                             | Integer                                                |                 |

All matches which were booked by the client on the live server will also be available on the replay server, with the following exceptions:

\
• Matches with a starting time less than 4 hours from the current time are not available.\
• Matches can be replayed forever. \
• As per 10th of November 2021, non-booked matches not older than 60 days can be booked and replayed.


---

# 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/live-data/introduction/replay-server.md?ask=<question>&goal=<endgoal>
```

`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.