📢 The Ask AI can now translate any part of the docs to your preferred language!
Read the guide
sportradar.comSportradar Support Portal

XML Configuration

This section contains information about general XML configuration settings with XML examples, XML attributes, and element descriptions. These configurations can be for a single sport, multiple sports or for all sports we offer.

When new features are released for a sport, they will not automatically be included in the feed. Clients need to enable the features on the Live Data XML configuration page before they will start receiving them. This interface can be found online at: portal.betradar.com > Configuration > Live > Live Data > Configuration. To activate a new feature, simply check them on or off in this configuration window.

Currently, the following XML features are available:

Note Not every sport currently has sport specific XML configurations. Information about sport specific XML settings can be found in each individual sport section.

Send matchlist updates (ID 18)

If this setting is enabled, the server sends out matchlistupdate messages over the feed automatically. These updates are sent to connected sessions when access to a match is either lost or gained. Example: Booking a match triggers a matchlistupdate message. Matchlistupdate messages look very similar to normal matchlist messages. The only differences are the name of the root element (<matchlistupdate> instead of <matchlist>) and a new attribute active in the <match> element.

XML example

<matchlistupdate>
<match active="1" booked="0" coveredfrom="venue" extrainfo="0" matchid="956" st1id="14321" st2id="14329" start="1361437625000" t1id="
11403" t1name="AGASSI, ANDRE" t2id="11749" t2name="GAUDIO, GASTON">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0" t2="0" type="match"/>
<tournament id="568" name="Paris TMS, France"/>
<category id="3" name="ATP"/>
<sport id="5" name="Tennis"/>
</match>
</matchlistupdate>

XML attributes definition

Element
Attributes

Attribute

Description

Possible values

match

active

Whether the match is available (for example right after booking) or unavailable (if it was just removed).

Integer 1 = The match is available 0 = The match is unavailable

Include matchstatus in events (ID 111)

Enabling this setting will include the match status attribute in every event. For more information about match statuses see each individual "information per sport section".

Include sportid in events (ID 109)

Enabling this setting will include the "sportid" attribute in the match element. Sport ID information can be found in here:

Information per Sport

Fullfeed matchtime (ID 3)

If this setting is enabled, the full feed will contain a matchtime attribute in the <match> element.

XML example

Include super team ID in the XML (ID 13)

If this setting is enabled, all <match> elements which are inside a <matchlist> will get the attributes st1id and st2id. In Live Data feed we send two team/competitor IDs. Example of "Miami Heat" in Live Data Product: Super Team Id is a unique team id that corresponds to "sr:competitor:xxx" across all other SR products. Team Id is a context of tournament "Miami Heat" team Id in NBA has id = 19441.

XML example

Match list example with the config enabled: XML example

Send the matchtime periodically (ID 21)

Enabling this setting will periodically send the client the matches they are subscribed to, and add the matchtime attribute for those matches. Matchtime updates will be sent only during the match. TO reduce the numebr of messages the server will not send matchtime updates before the start and after the match has finished.

Use match status ABANDONED (ID 12)

Enabling this setting will allow the system to send match status ABANDONED.

XML example

Include device ID for matches in matchlist (ID 38)

Enabling this setting will add the ID of the device used for scouting to the <match> element in the matchlist. The device will also be added to the <match> element when the client subscribes to a match.

XML example

Possible values for the device attribute

ID
Device

-1

No scout allocated yet

1

Hardphone/Asterisk

3

XSA (ScouTVAdmin/Scout platform)

4

Scout mobile app - iScout/ITF Scorer/UTR Scorer

5

External data feed

6

hScout

Add team abbreviations to the matchlist response and full feed (ID 94)

Enabling this setting will add the t1abbr and t2abbr to the <match>-element for all sports. These attributes get added to the full feed and to matchlist responses.

XML example

XML elements and attributes definition

Element
Attributes

Attribute

Description

Possible values

Match

t1abbr

3 letter abbreviation of home team name.

String

t2abbr

3 letter abbreviation of away team name.

String

Please note that American Football matches always contain the t1abbr and t2abbr attributes, regardless of whether this setting is enabled or not.

Enable coverage status in matchlist (ID 97)

Enabling this setting will add the ID of the coverage status to the <match> element in the matchlist.

XML example

Possible values for coverage status

ID
Coverage status

0

Covered

1

Coverage abandoned

2

Not covered

Include matchid in bookmatch replay (ID 24)

If this setting is enabled, the attribute matchid gets added to the <bookmatch> element.

XML example

Send jersey color information (ID 105)

Enabling this setting will add will add <jerseys> element to the <match> element in the full feed containing jersey color information.

XML example

The different values for the jersey_type attribute are: 1. HOME, "Home kit" 2. AWAY, "Away kit" 3. ALTERNATE, "Alternate kit" 4. GOALKEEPER, "Goal keeper kit"

Include naturally capitalized team names (ID 108)

Enabling this setting will add naturally capitalized team names for home and away teams to the <match> element in the full feed with attributes t1namenatural and t2namenatural, respectively.

XML example

Include UUID attribute to all events (ID 140)

Enabling this setting in the configuration will include a Universally Unique Identifier (UUID) to all <event.../> messages in the feed.

XML example

Include UUID of deleted events (ID 141)

Enabling this setting in the configuration will include a reference to the Universally Unique Identifier (UUID) of the deleted event to all <event.../> messages in the feed that are of eventtype 1044 (DELETE_EVENT_ALERT). The reference is in the attribute "refuuid".

XML example

Include an attribute called teamsreversed to the matchlist message and fullfeed message (ID 170)

There can be a situation when the home/away team association cannot be confirmed in time or it is changed at the last minute. New attribute added to matchlist and fullfeed called 'teamsreversed' will be added with possible values: 1 - Order not confirmed 2 - Order reversed in the official sources If teams order (home/away) is officially confirmed there will be no change in the feed. In Live Data Client app - teams will be displayed in the correct order.

XML Full feed changed into partial/paginated feed (ID 176)

This config enables new type of feed update - "partial". When the message of the full feed is big the server will chop the message into smaller chunks. Feed will be split into pages. See atributes page, totalpages and feedtype=partial.

PreviousReplay ServerNextXML Examples

Last updated

Was this helpful?