# Match List

Client systems can request a list of available scout matches for a specific time frame.

**XML example**

```xml
<matchlist hoursback="6" hoursforward="24" includeavailable="yes"/>
```

***XML attributes definition***

| Element   | Attributes         | Description                                                                                                                                                           | Possible Values                                     |
| --------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| matchlist | <p><br></p>        |                                                                                                                                                                       |                                                     |
|           | *hoursback*        | The amount of hours ago the timeframe for the request starts.                                                                                                         | Integer                                             |
|           | *hoursforward*     | The amount of hours in the future the timeframe for the requests ends.                                                                                                | Integer                                             |
|           | *includeavailable* | Optional attribute. If this attribute is passed and the value is "yes", the match list reply will also include matches that are not booked yet, but open for booking. | <p>String</p><p>yes = Include available matches</p> |

{% hint style="info" %}
**Note**\
The maximum timespan one can request matches for is 300 hours. If the timespan is greater than 300 hours it will automatically be adjusted down to 300 hours. If the optional attribute includeavailable="yes" is set, the maximum values of "hoursback" and "hoursforward" are 48 hours and 240 hours respectively.
{% endhint %}

{% hint style="info" %}
**Note**\
The maximum timespan one can request matches for is 300 hours. If the timespan is greater than 300 hours it will automatically be adjusted down to 300 hours. If the optional attribute includeavailable="yes" is set, the maximum values of "hoursback" and "hoursforward" are 48 hours and 240 hours respectively.
{% endhint %}

**Match list reply**\
After the client system sends the match list request, a list of matches within the specified timeframe gets sent back.

**XML example**

```xml
<matchlist>
<match booked="1" distance="10" matchid="798175" start="1244822400000" t1id="560764" t1name="BRØNDBY IF II" t2id="560743" t2name
="KØBENHAVNS BK">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0" t2="0" type="current"/>
<tournament id="3422" name="2nd Division East"/>
<category id="8" name="Denmark"/>
<sport id="1" name="Soccer"/>
</match>
<match booked="0" coveredfrom="venue" distance="2577" extrainfo="0" matchid="4973320" st1id="4412" st2id="4393" start="1244966000000
" t1abbr="ARI" t1id="35276" t1name="ARIZONA CARDINALS" t2abbr="ATL" t2id="33132" t2name="ATLANTA FALCONS">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0" t2="0" type="current"/>
<tournament id="47" name="NFL"/>
<category id="43" name="USA"/>
<sport id="16" name="Football"/>
</match>
<match coveragestatusid="0" coveredfrom="venue" device="3" extrainfo="0" matchid="11361408" st1id="152332" st2id="249567" start="
1495531320000" t1id="1223041" t1name ="DELHI DAREDEVILS" t2id="8511090" t2name="GUJARAT LIONS">
<status id="502" name="FIRST_INNINGS_AWAY_TEAM" start="1495531234237"/>
<score t1="0" t2="0" type="match"/>
<innings dismissals="0" runs="0" statusid="502" statusname="FIRST_INNINGS_AWAY_TEAM"/>
<tournament id="7824" name="Premier League"/>
<category id="497" name="India"/>
<sport id="21" name="Cricket"/>
</match>
</matchlist>
```

***XML attributes definition***

<table><thead><tr><th width="88.7012939453125">Element</th><th width="153.2274169921875">Attributes</th><th>Description</th><th>Possible values</th></tr></thead><tbody><tr><td>match</td><td><em>booked</em></td><td>Optional attribute indicating whether a match is booked or not. Only added if includeavailable=" yes" was added to the match list request.</td><td>Integer<br>1 = Match is booked<br>0 = Match is not booked yet, but open<br>for booking.</td></tr><tr><td><br></td><td><em>vbpclassifcation</em></td><td>Attribute to define Value Based pricing classification for customer packages.</td><td>String<br>Values:<br>star<br>mvp</td></tr><tr><td><br></td><td><em>division</em></td><td>Division name associated with the team for US leagues/competition.<br>List of tournaments in scope attached.<br><br></td><td>String</td></tr></tbody></table>

**Match list filtering**

To filter by sport id you can send for example:

```xml
<matchlist hoursback="15" hoursforward="10">
	<sport sportid="1" />
	<sport sportid="2" />
</matchlist>
```

```xml
```


---

# 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-list.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.
