Sport event status
The sport_event_status is the element which provides information related to the status of the match and can be retrieved mainly in the summary and timeline end points.
Before providing the description of its attributes, it is important to make a distinction between the sport event status provided in the AMQP feed and the one provided in the end points.
In case of AMQP feed 4 status can be provided and they are sent in the odds_change message:
not_started
live
ended
closed
In the API many other status can be provided to identify the status of the match.
As the API can be slightly delayed compared to the odds_change message, therefore, it is recommended that the client gives priority to the status provided in the odds_change message.
Also in case of live matches, in general the odds_change message contains the sport_event_status element: due to caching and timing differences the API and the odds_change message can temporarily report a different status.
Priority should be always given to the odds_change message.
Another important difference between the odds_change message and the API is that the odds_change message represents statuses using an integer code as shown below:
The following table shows all the possible attributes of the sport_event_status element in the API
status
provides information related to the status of the match
not_started, match_about_to_start, postponed, delayed, cancelled, interrupted, suspended, abandoned, retired, ended, aet, match_after_penalties
home_score
provides score of the home team
numeric value
away_score
provides score of the away team
numeric value
winner_id
provides info about who the winner is
string
example: "sr:competitor: 6237"
status_code
0, 22, 60, 61, 70, 80, 81, 90, 92, 100, 110, 120 (correspondence between status and status_code is reported in table below inthe section dedicated to the status)
numeric value
match_status_code
see dedicated paragraph below
Status
Going more into the detail of the status possible values:
not_started
match not started yet
match_about_to_start
match about to start
postponed
The sport event has been postponed and will be played at a later date. Tipically, if the later date is more than 3 days away, this sport event will be cancelled and replaced by a new id. If the match is postponed to just one or 2 days from now, the same sport id will change its state just before the match starts.
delayed
The sport event has been delayed from scheduled start (most often seen for tennis)
cancelled
The sport event (either the actual match, or sportradar representation ) has been cancelled.
interrupted
The sport event has been temporarily interrupted. Interruption is expected to be just a few minutes. Longer interruptions may lead to a match being suspended or possibly postponed.
suspended
The sport event looks to be interrupted for a longer period than just a few minutes.
abandoned
Used to indicate that Betradar has no live coverage ut match is still likely ongoing.
retired
ended
Match is over
aet
Match has ended after extra time
match_after_penalties
Match has ended with penalties
closed
The match is over, results are confirmed, no more changes are expected to the results.
Sometimes live-only matches will never get the status element set to status "closed", they will just stay in "ended" in the API. This is because matches are put in "Closed" when production has prematch-resulted these matches therefore, if the matches are only live covered, then they will never be "closed", only "ended".
Correspondence between status and status_code
not_started
0
match_about_to_start
22
postponed
60
delayed
61
cancelled
70
interrupted
80
suspended
81
abandoned
90
retired
92
ended
100
aet
110
match_after_penalties
120
closed
Match_Status_Code
The match_status_code is an attribute which describes the phase the match is into and is different according to the sport taken into consideration.
The attached excel provides all possible values and meaning for the match_status_code:
match_status_codes.ods
Was this helpful?