...
Introduction and Table of Contents
The "incident" message is the primary message that our Scout sends during match coverage as part of the ScoutsFeed product. This part of document contains a description of the most important fields and information included in it. Understanding these elements will enable better integration of the product and further exploration of its capabilities.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The “Action” field
The key to understanding the differences between single incidents (match events) is the “action” field, which provides clear information about the type of action taken in relation to a specific match incident.
...
The table below will provide a better understanding of the differences between the 3 "actions" within an "incident" type message.
Sport | Insert | Update | Delete |
---|---|---|---|
Soccer | “Shot on target” for FC Barcelona “Goal” for Spain |
| “Shot on target” for FC Barcelona is deleted (for example it was blocked shot) Key incidents are not deleting. We are using the “confirmation/cancelltion” rules (description HERE). Goal might be cancelled in the case of using the VAR system |
Basketball | “2pts shot made” for Boston Celtics |
| “2pts shot made” for Boston Celtics is deleted (for example, when there was a foul before - shot is not counted) |
Ice Hockey | “Suspension” for Colorado Avalanche |
| “Suspension” for Colorado Avalanche is deleted (for example after video review the referee' call is overturned) |
American Football | “Touchdown” for Kansas City Chiefs |
| “Touchdown” for Kansas City Chiefs is deleted (for example there was a yellow flag) |
Handball | “Throw saved” for France |
| “Throw saved” for France is deleted (for example, where there was a foul before - shot is not counted) |
Baseball | “Out” for Los Angeles Dodgers |
| “Out”for Los Angeles Dodgers is deleted |
Fields related to the incident and its level of detail
...
Each incident generated by Scout may have additional information, which is usually sent in an “update” of the specific incident (see the table above). The most important fields describing a specific incident include:
...
incident_id - ID of the sended incident (the list of specific incidents for all ScoutsFeed sports is available HERE)
incident_name - name of the incident
category - possible values:
standard - for all incidents related to a specific sport
emergency -for special set of incidents sent to clients, which inform about an extraordinary situation before/during/after the match (description HERE)
attribute_ids - contains information about the attributes that have been added to a specific incident. Attributes refer to additional, more detailed information regarding the sent incident (for example goal with left foot, outside of the penalty area, after fast attack)
...
Sport | Event (match) | Participants | Subparticipants (players) |
---|---|---|---|
Soccer | FC Barcelona - Real Madrid |
|
|
Basketball | Boston Celtics - Los Angeles Lakers |
|
|
Tennis | Carlos Alcaraz - Jannik Sinner (single) Max Purcell/Jordan Thompson - Kevin Kravietz/Tim Puetz (double) |
| Not applicable Not applicable |
Table Tennis | Fan Zhendong - Wang Chuqin Manyu Wang/Yuling Zhu - Honami Nakamori/Satsuki Odo |
| Not applicable |
Ski jumping | Zakopane Men’s HS 140 (individual) Zakopane Men’s Team HS 140 (team) |
| Not applicable
|
...
Info |
---|
In the case of sports competitions that can be either individual or team-based (e.g., winter sports, speedway, athletics), the participants are either individual athletes (for individual competitions) or sports clubs/national teams (for team competitions). In the second case, athletes belonging to a specific sports club or national team are considered subparticipants (example of ski jumping is presented above, in the table) |
The
...
“Confirmation” field
This field contains information about whether the given incident has been confirmed by Skaut or not. It can take 3 values:
...
Since this field is crucial for clients who wish to use our data to settle match markets, a separate section of the documentation has been dedicated to it, which can be found HERE.