# Match Subscription

By subscribing for a match, the client system tells the server that they want to receive data for the specified match. If the match subscription went through successfully, the client system receives a *full match message* for the match they just subscribed to. Additionally, you will receive *delta messages* and *delta update messages* during the match.

**XML example - single match**

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

**XML example - multiple matches**

```xml
<matchsubscription>
	<match matchid="1101335"/>
	<match matchid="1062714"/>
</matchsubscription>
```

***XML attributes definition***

| Element | Attribute | Description                                                  | Possible values |
| ------- | --------- | ------------------------------------------------------------ | --------------- |
| match   | *matchid* | The id of the match the client system wants to subscribe to. | Integer         |

{% hint style="info" %}
**Note**\
It is possible to subscribe to multiple matches at the same time. Doing this requires the client system to create a separate \<match> element for each match they want to subscribe to, and encapsulate them with \<matchsubscription> elements.
{% endhint %}

{% hint style="info" %}
**Note**\
It is possible to subscribe to multiple matches at the same time. Doing this requires the client system to create a separate \<match> element for each match they want to subscribe to, and encapsulate them with \<matchsubscription> elements.
{% endhint %}

### **Match subscription failed**

If the client system tries to subscribe to a match they does not have access to they will not receive a full match message, but a match subscription failed message instead. This can occur if the customer in question already has 2 open subscriptions for the match.

**XML example**

```xml
<matchstop matchid="944423" reason="Bookmaker already has maximum number of subscriptions for this match"/>
```

***XML attributes definition***

| Element   | Attributes | Description                                                         | Possible values |
| --------- | ---------- | ------------------------------------------------------------------- | --------------- |
| matchstop | *matchid*  | The id of the match for which the match subscription failed.        | Integer         |
|           | *reason*   | A textual description explaining why the match subscription failed. | String          |

<br>


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/live-data/introduction/system-communication/xml-messages-sent-from-the-client-system/match-subscription.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.