Page History

A fixture_change message is sent when a Betradar system has made a fixture change it deems as important.

These are typically changes that affect events in the near-term (e.g. a match was added that starts in the next few minutes, a match was delayed and starts in a couple of minutes, etc.).

The message is short and includes a bare minimum of relevant details about the addition/change. The recommended practice is to always to do a follow-up API call to lookup the updated fixture information.

We might cancel the coverage of a match before it starts, or in the middle of the match. This might cause the sport_event_status status=”3” (match is ended) to not occur. However, a fixture_change message will be sent instead if this happens.

The fixture_change element in the message is made up of three attributes which are shown in the table below.

event_id

change_type

product

Examples of actual fixture_change messages are shown below: 

<!-- Unspecified type of change -->

<fixture_change event_id="sr:match:1234" product="3"/>

<!-- New -->

<fixture_change event_id="sr:match:1234" change_type="1" product="1"/>

<!-- Coverage change -->

<fixture_change event_id="sr:match:1234" change_type="5" product="3"/>

<!-- Start time change -->

<fixture_change event_id="sr:match:1234 " change_type="2" product="1"/>

The change_type attribute (if present), describes what type of change that caused the message to be sent. In general, best practices are to always re-fetch the updated fixture from the API and

not solely rely on the change_type and the message content. This is because multiple different changes could have been made. 

Lately a new change type was added, the change type number 6, which informs if the starting pitcher has been  changed  before the start of a baseball match.

Therefore, at present, the list of all the change types which trigger a fixture_change message are listed  in table below where you can see  the addition of the  PITCHER change type.

Though fixture changes for a particular event are provided in the XML feed, still, it is possible to request a list of all the fixture changes happened during the last 24 hours by means of the Fixture_change API end point  (API) or by using the SDK.

In this case the event_id is provided and the time of the change as well. Once you get such info, you can use the fixture end point in order to retrieve more detailed info related to the change.

An example follows of the response of the fixture_change API end point call. 

<?xml version="1.0" encoding="UTF-8"?>
<fixture_changes>
<fixture_change sport_event_id="sr:match:16132080" update_time="2018-11-27T06:48:40+00:00"/>
<fixture_change sport_event_id="sr:match:16330880" update_time="2018-11-27T06:48:40+00:00"/>
<fixture_change sport_event_id="sr:match:16330872" update_time="2018-11-27T06:48:38+00:00"/>
<fixture_change sport_event_id="sr:match:16330876" update_time="2018-11-27T06:48:29+00:00"/>
<fixture_change sport_event_id="sr:match:16343962" update_time="2018-11-27T06:48:29+00:00"/>
<fixture_change sport_event_id="sr:match:16330236" update_time="2018-11-27T06:48:27+00:00"/>
<fixture_change sport_event_id="sr:match:16343964" update_time="2018-11-27T06:48:25+00:00"/>
</fixture_changes>

References

Unified feed uses multiple types of references. A reference in Unified Feed displays what producer reference a particular fixture is using. This is displayed inside the reference_id element.