> 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/system-communication/xml-messages-sent-from-the-betradar-system/lineups.md).

# Lineups

If the XML configuration option *Send lineups for matches where this is available* is activated, the lineups XML will be sent over\
the feed automatically. The XML contains the player lineups for both teams, and is currently available for:

* American Football
* Baseball
* Basketball
* CS:GO
* Dota2
* Handball
* Ice hockey
* League of Legends
* Rugby
* Soccer

The lineups XML is sent immediately after subscribing to a match, and it’s also sent automatically every time the lineup changes.

{% hint style="info" %}
**Note**

The initial message can be incomplete. Team lineups may arrive separately from the source.
{% endhint %}

{% hint style="info" %}
**Note**

Lineups will be only available for DC (Deeper Coverage) matches.
{% endhint %}

{% hint style="info" %}
**Note**

The player id element in the lineup message will match the player id element in the case of an event such as a goal. The following XML example illustrates how this looks in the feed after a goal in a soccer game:
{% endhint %}

{% hint style="info" %}
**Note**:

Lineups will be only available for DC (Deeper Coverage) matches.
{% endhint %}

{% hint style="info" %}
**Note**:

The player id element in the lineup message will match the player id element in the case of an event such as a goal. The following XML example illustrates how this looks in the feed after a goal in a soccer game:
{% endhint %}

**XML example**

```xml
Update with player info:
<match betstatus="BETSTOP" connectionstatus="1" dc="1" feedtype="deltaupdate" matchid="12813841">
<score t1="2" t2="0" type="period1"/>
<score t1="2" t2="0" type="current"/>
<shotsontarget t1="2" t2="0"/>
<events>
<event extrainfo="-100" id="879292323" info="Goal [T1] (shot) - M.Upson" matchscore="2:0" mtime="03:56" player1="569" posx="50" posy="
50" side="home" stime="1510558801855" type="30"/>
</events>
</match>
Lineup element:
<lineups matchid="12188488">
<player id="569" name="Upson, M" position="D" shirtnumber="99" substitute="false" team="1"/>
<player id="49038" name="Andelkovic, Sinisa" position="D" shirtnumber="4" substitute="false" team="1"/>

```


---

# 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/live-data/introduction/system-communication/xml-messages-sent-from-the-betradar-system/lineups.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.
