Introduction and Table of Contents
The "event" message is the second most important message sent by our Scouts. It can be sent either separately or along with the "incident" message. This message primarily contains general information about the match as well as match statistics - both team and personal statistics. This document outlines the key fields and information included in the "event" message. Understanding these elements will enable better integration of the product and further exploration of its capabilities.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The “Competiton”, “Stage”, “Round”, “Tour” fields
In the "event" type message there are fields that allow for assigning a specific match to the competition it is part of, as well as more detailed information such as the stage or round.
In general, we have 4 levels of depth for competition data:
(1) competition - the most general information, containing the name of the competition (and sometimes the name of the title sponsor, e.g., Ligue 1 McDonald’s),
(2) season - each competition is divided into seasons that have taken place within it. The number of seasons we have in the database depends on various factors such as the sport and stats level,
(3) stage - in other words, the phase in which the match is played. The stages played in a given competition are determined by the competition's regulations. Typically, they are divided into "Regular Season" and "Play Offs" for league competitions, and "Group Stage" and "Play Offs" for cup competitions. However, there are many other stages, depending on the sport or the specific competition,
(4) round - the lowest level of information typically indicates the round on which a given match is played (for league competitions) or the round of the play-off stage (for cup competitions).
| Info |
|---|
Information about the "Tour" is only relevant for individual sports and in the case of the ScoutsFeed produc - (so far) only for tennis. This is crucial for distinguishing between men's and women's competitions, as well as their categories (e.g. WTA Tour (W), ATP 500 etc.). |
The table below shows examples of these identifiers across different sports. They should provide a better understanding of this structure, which is crucial for both ScoutsFeed and SportsAPI clients.
Sport | Event | Competition | Season | Stage | Round | Tour |
Soccer |
|
|
|
|
| |
Basketball |
|
|
|
|
| |
Ice Hockey |
|
|
|
|
| |
Tennis |
|
|
|
|
|
|
Handball |
|
|
|
|
| |
Baseball |
|
|
|
|
|
Bet statuses for markets managing
In this message, you can also find fields related to the Scout’s management of match markets. This information is crucial for the settlement of match bets by clients in the betting industry.
...
Because of that a separate section of the documentation has been dedicated to it, which can be found HERE.
Participants and subparticipants (players) statistics
The most important (and largest) part of the message consists of match statistics - both team and personal (player props). The number of statistics sent in push messages is determined by the competition's stats level. The higher the stats level, the more statistics we send.
 |  |
statistics are always sent per team (participant), and deeper - per player
all team statistics are located in the
"stats"node which is part of the"participants"node (screen 1) , where they are then divided into individual statistics according to the following schema:"id": 8,- ID of the specific statistic (description of all available statistics per sports is HERE)"value": 1- the current value of the statistic
all persons statistics are located in the
"stats"node which is part of the"subparticipants"node (screen 2) , with the same schema
| Info |
|---|
IMPORTANT! The set of all team statistics for both teams is sent each time any of them changes (even if no statistic changes for one of the teams). In the case of individual (personal) players statistics, the message only contains changes for players whose statistics have been updated. Example:
|
Other important nodes and fields
It is also important to note other key fields and nodes that are included in the "events" message:
"latency"field - information about the delay in sending data relative to real-time"coverage_type"field - information about the coverage type of given event"relation_status"field - information about the current status of relation, sended by Scouts both - before the game (30min left/5 min left before the start) and during the game (in progress)"event_stats_lvlfield - contains information about the statistical level at which the Scout covers the specific match"details"node - contains information about match details specific to a particular sport or competition, such as the number of game periods, the duration of each period, current weather, competition format. All event details are described HERE"results"node - contains information about the current main result and partial results per participant (team)