The Client system can request meta-information about upcoming and current matches. It is possible to receive all matches in a certain timespan, or to specify the matches for which the meta information is desired. The response message includes teams playing, match date and time, TV channel names, streaming information and sport/category/tournament for the match. Best practice
To make sure that the client system has the most recent match meta information, it is recommended to send meta requests periodically, and update possible changes in the client system. The following guidelines apply: - Send a request once an hour to get matches for the next 24 hours;
- Send a request once per day to get matches for the next week;
- Send a request after the client system reconnects after a disconnection.
XML examples | Code Block |
|---|
| <BookmakerStatus bookmakerid="24" type="meta" /> |
| Code Block |
|---|
| <BookmakerStatus bookmakerid="24" type="meta">
<Match matchid="588101" />
<Match matchid="524577" />
<Match matchid="516557" />
<Match matchid="568263" />
</BookmakerStatus> |
| Code Block |
|---|
| <BookmakerStatus bookmakerid="24" metafrom="1190370195000" metato="1190391831000" includeavailable="true" type="meta" /> |
XML attributes definition | Element | Attributes |
|---|
| Attribute | Description | Possible values | BookmakerStatus
| type | Keyword which describes what kind of request is sent. | String
"meta" (for meta information requests) | | bookmakerid | The id of the bookmaker | Integer | | metafrom | Optional. Start of the interval for matches of which the meta information is desired. Maximum interval is 10 days. | UTC timestamp | | metato | Optional. End of the interval for matches of which the meta information is desired. Maximum interval is 10 days. | UTC timestamp | | includeavailable | Optional. Usually the meta message will only include the matches that are booked or included in the purchased package. By enabling either this attribute or the corresponding XML configuration, the response will also include matches that are available for booking but not booked (yet). Enabling this attribute will override the XML configuration, for this request only. The match element in the metaresponse will then include an extra attribute booked with the value 1 if the match is already booked, or 0 if it is not booked yet. | String
"true" = Include nonbooked matches | | matchid | The id of the match for which the meta is requested. If no Match elements were specified, all matches which apply to the other attributes are returned. | Integer |
| Info |
|---|
Note
If matchids are specified through match elements, only meta-information for these matches is returned. By default, if no matchids are indicated and no metafrom/metato is specified, all matches started 24 hours in the past, and 7 days in the future are returned. |
|