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.
<match matchid="944423"/>
<matchsubscription>
<match matchid="1101335"/>
<match matchid="1062714"/>
</matchsubscription>
XML attributes definition
| Element | Attribute |
|---|
| Attributes | Description | Possible values |
| match | matchid | The id of the match the client system wants to subscribe to. | Integer |
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.
<matchstop matchid="944423" reason="Bookmaker already has maximum number of subscriptions for this match"/>
XML attributes definition
| Element | Attributes |
|---|
| Attribute | 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 |
