circle-info
"Additional Solutions” provide insights into our range of media offerings; originally part of IMG & now part of Sportradar
chevron-right
search
sportradar.comSportradar Support Portal

Best Practice Guide

Tips for integrating with Live Data XML Feed

hashtag
Matchlist

Matchlist is a message that contains all booked or all booked and bookable matches for a particular time period. For the message to contain all booked and bookable matches, include the attribute includeavailable in your request. For booked-only matches, you can omit that part.

<matchlist hoursback="1" hoursforward="2" includeavailable="yes"/>

or 

<matchlist hoursback="1" hoursforward="2"/>

To differentiate between booked and bookable matches, refer to the 'booked' attribute (0 indicates bookable, 1 indicates booked): 

<matchlist>
<match t2name="SK RAPID" t2id="6592" t1name="FK AUSTRIA WIEN"
t1id="6597"t1abbr="FAK" t2abbr="SCR" start="1733920680000"
matchid="124395595"extrainfo="0" distance="10" device="4"
coveredfrom="venue" booked="1" coveragestatusid="0">
<tournament name="Bundesliga" id="29"/>
<category name="Austria" id="17"/>
<sport name="Soccer" id="1"/>
<status start="1733922929294" name="ENDED" id="100"/>
<score type="current" t1="0" t2="0"/>
</match><match t2name="SK RAPID" t2id="6592" t1name="FC SALZBURG"
t1id="6593"t1abbr="SAL" t2abbr="SCR" start="1733920680000"
matchid="124395596"extrainfo="0" distance="247" device="4"
coveredfrom="venue" booked="0" coveragestatusid="0">
<tournament name="Bundesliga" id="29"/>
<category name="Austria" id="17"/>
<sport name="Soccer" id="1"/>
<status start="1733922933016" name="ENDED" id="100"/><score
type="current" t1="0" t2="0"/>
</match>

The matchlist response can be filtered to show matches for a specific sport. For instance, the following command would return a list of all booked and bookable eSoccer matches within the selected timeframe:

The maximum timespan one can request matches for is 300 hours. This will increase the response time to this request. Filtering per sport and choosing different frequencies of requests is preferred by most customers. 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.

A matchlistupdate message is triggered when a significant change occurs to a fixture, such as a change in the starting time. It is also sent automatically after a match has been booked. However, these messages must first be enabled through an XML configuration ID 18.

lightbulbTip At the start of each day, request a matchlist response for booked matches in the next 24 hours. To stay up to date, supplement this with matchlistupdate messages, which will be automatically sent whenever a significant change occurs to one of your booked matches. For added safety, you can also request the matchlist manually every hour or two.

hashtag
Match Booking

A valid match booking request and its corresponding response would appear as follows:

Sending a booking request for a match that has already been booked will result in the following response:

After a match is booked, it becomes available for subscription.

hashtag
Subscription

To subscribe to a match, use the following request:

A valid response to a match subscription request is a full match message (full feed). However, a subscription request may fail, typically because the match is not booked. In such cases, the response will be as follows:

lightbulbTip In rare occurrences a delay may happen to the service that manages bookings. To counter this, please insert a small gap between booking and subscription requests. Alternatively, monitor subscription requests that have failed and attempt to resubscribe.

Multiple matches can be subscribed to with a single request. An example of such a request is as follows:

lightbulbTip

To prevent processing issues, we recommend keeping the number of matches in a subscription request below 50

hashtag
Unsubscription

To unsubscribe and stop receiving live updates for a specific match, send the following request:

The valid response to an unsubscription request will be as follows:

hashtag
Betstatus

The two possible BetStatus values are BETSTOP and STARTED, which are toggled by the event types BETSTOP and BETSTART. BETSTOP changes the BetStatus from STARTED to BETSTOP, while BETSTART changes it from BETSTOP to STARTED. BETSTOP is triggered when a significant change occurs in an ongoing match, such as a goal being scored in soccer, or when the current situation is unknown or unpredictable, prompting the suspension of betting on the match. BETSTART indicates that the score and all data for an ongoing match are accurate and up to date, allowing betting to resume/commence

lightbulbTip When subscribing to a match, first check the value of the BetStatus attribute in the full match message (full feed). Then, track the BETSTOP and BETSTART event types to ensure that your system’s BetStatus remains in sync with the BetStatus from Sportradar at all times.

lightbulbTip You can track different BETSTOP reasons, identified by the extrainfo attribute of the Betstop event type, and choose to disregard some of them based on your own risk assessment.

hashtag
Coverage Status

The Coverage Status event type indicates whether a given match will be covered, not covered at all, or has been abandoned. If multiple Coverage Status events are sent, the most recent one is considered correct. For example, a match may transition from Covered to Not Covered and then back to Covered if the original scout is unable to perform their duties and no replacement is available at the time, but another scout is later found to take over.

  • Coverage Status: Covered means the match will be covered as expected.

  • Coverage Status: Not Covered means that the previously planned coverage for the match can no longer be performed. As a result, live data will not be provided for that match.

  • Coverage Status: Abandoned means that we can no longer guarantee accuracy or completeness of the ongoing coverage. While live data will generally continue to be sent until the end of the match, it should be treated with caution

lightbulbTip Coverage status can be included in the matchlist message by activating XML Config ID 97.

hashtag
Deltaupdate messages

Deltaupdate messages (feedtype=deltaupdate) are sent to update previous delta messages within a given coverage, modifying one or more of their attributes. These messages do not represent new events, but rather modifications or updates to events that have already occurred. The score- and time-related attributes in these messages will remain unchanged from their values in the original delta message. For example, a ‘Goal Confirmed’ event is sent as soon as we are certain that a goal has been scored and will stand. However, this event typically does not include the goal scorer, as that information usually requires additional verification. The goal scorer is then added to the previously sent goal event through a deltaupdate message:

lightbulbTip Ensure that the information in deltaupdate messages does not modify the current score or match time in your system. Since these messages are used to update events that occurred earlier in the match, the score and time related information they contain is often outdated.

hashtag
Event deletion

Events are deleted when they have been entered incorrectly, accidentally, or when certain occurrences are called off. This is done via the Event Deleted 1044 event type, which includes the event’s uuid in the refuuid attribute. When requesting the full match message after deletion, the deleted event will no longer be included. Instead, the message will only contain the 1044 event as confirmation that the deletion has occurred.

For example, the deletion of a confirmed yellow card would appear in the delta feed as follows:

And the same deletion would appear like this in the subsequent full feed:

lightbulbTip Use the uuid value in the refuuid attribute of the 1044 Deletion event type to identify the deleted event and ignore it.

hashtag
Replay Server

Connection details for the replay server: Hostname: replay.livedata.betradar.com Port: 2047 (SSL) All booked matches can be replayed indefinitely, beginning 4 hours after the match has started. The replay can be conducted at real speed or at a predetermined speed. Additionally, a replay can begin from a specific message, such as the 100th message sent within the coverage. To request a replay of a specific match at real speed, send the following request:

To request a replay that runs at a speed of 150 milliseconds between messages, starting from the 25th message, send the following request:

lightbulbTip To receive the full feed message without waiting for the replay to complete, simply request that the replay starts from a specific message and choose a very high number to skip directly to the end of the replayed match:

PreviousXML Schema Definition (XSD)NextFeature Updates

Last updated

Was this helpful?