| .feed |
|
|---|
| id | Unique identifier for the message |
| uuid | Universally Unique Identifier for the massage.
Note: for certain messages, such as updates to a previous, related message, the UUID may be the same. This intentional duplication allows clients to establish correlations between messages, aiding in tracking updates or related data across a system. |
| type | Possible value: |
| source | Internal attribute, please dont use this attribute |
| ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP. |
| ..data |
|
|---|
| ...incident | node available only if message type is incident |
|---|
| id | Unique identifier for the incident occurred in the event |
| action | Describes type of scout operation for the incident. Possible values: - insert - new incident generated by the scout
- update - incident was updated by the scout (e.g. incident "yellow card" is updated when scout fills in the name of the player (participant)
- delete - incident was deleted (e.g. when the scout adds an incident by mistake, he can delete it)
|
| incident_id | Identifier for the incident incident |
| incident_name | Name of the incident. e.g. goal, yellow card, red card etc. |
attribute_ids | Attributes identifiers related to incident, separated by a comma (e.g. [397, 398]) |
| confirmation | Describes confirmation status for the incident. Possible values: - tbd – appears as default for Goal, Penalty, Red card, Yellow card and Corner incidents.
- confirmed – appears when the following incident will be confirmed by referee.
- cancelled – appears when the following incident will be cancelled by referee. Incidents with this value have no effect on statistics.
|
| participant_id | Unique identifier of participant (player, team or coach) name related to incident incident |
| participant_name | Participants (player, team or coach) name related to incident. |
| subparticipant_id | Team id that the player or coach is part of of |
| subparticipant_name | Team name that the player or coach is part of |
| info | Internal attribute, please dont use this attribute |
| important_for_trader | Possible values: |
| important | Internal attribute, please dont use this attribute |
| add_data | Internal attribute, please dont use this attribute |
| show_popup | Internal attribute, please dont use this attribute |
| show_scores | Internal attribute, please dont use this attribute |
| action | Describes type of scout operation for the incident. Possible values: insert - new incident generated by the scoutupdate - incident was updated by the scout (e.g. incident "yellow card" is updated when scout fills in the name of the player (participant)delete - incident was deleted (e.g. when the scout adds an incident by mistake, he can delete itshow_action | Internal attribute, please dont use this attribute |
| show_time | Internal attribute, please dont use this attribute |
| show_on_timeline | Internal attribute, please dont use this attribute |
| event_time | Information when the incident occurs in format MM:SS |
| event_status_id | Unique identifier of the event status |
| event_status_name | Name of the event status |
| period_timer | Informations regarding game clock |
| direction | Contains information about timer direction. Possible values: |
| time | Time in sync with the game clock |
| x_pos | Ball position on X axis (percents) |
| y_pos | Ball position on Y axis (percents) |
| ...event | node available only if message type is event |
|---|
| id | Identifier of the event |
| action | Describes type of operation for the event. Possible values: - insert - new event generated
- update - event was updated
- delete - event was deleted
|
| name | The name of the event |
| start_date | Start date for the event in format: YYYY-MM-DD hh:mm |
| ft_only | Determines if only the full time result/score of the event is given . Possible values: - yes - result/score is updated only when the event is finished
- no - result/score is updated during the event
|
| coverage_type | Type of event coverage. Possible values: - from_venue - means the scout is relaying the event directly from the stadium (max. latency 1 second)
- from_low_latency_tv - means the scout is relaying the event from tv transmission (max. latency 3 seconds)
- from_tv - means the scout is relaying the event from tv transmission (max. latency 8 seconds)
- basic - for this type of coverage we don't provide detailed event incidents (max. latency around 60 seconds)
|
| status_id | Unique identifier of the event status status |
| sport_id | Identifier for the sport in which the event is played played |
| round_id | Unique identifier for the round in which event is played. Possible null value |
| round_name | Name of the round. Possible null value. |
| day | Day of the season |
| neutral_venue | Determines if event is played at a neutral venue. Possible values: |
| item_status | Describes status for the item (record). Possible values: - active - the record is active
- deleted - the record was deleted by the admin. In the case of when an event was added by mistake
|
| clock_time | Number of seconds that have passed in the current period |
| clock_status | Clock status. Possible value: |
| area_id | Identifier for the area in which the competitions are played |
| competition_id | Unique identifier for the competition competition |
| season_id | Unique identifier for the season. |
| stage_id | Unique identifier for the stage |
| tour_id | Unique identifier for the tour in which a competition is played |
| gender | Competition gender. Possible values: |
| bet_status | Bet status. Possible values: |
| bet_cards | Changed when there is a possibility of a card. Possible value: |
| bet_corners | Changed when there is a possibility of a corner. Possible value: |
| relation_status | Relation status. Attribute for internal purposes. Possible value: - not_started - for an event that has not started
- in_progress - for a live event
- finished - for an event that has finished
- 30_min_left - scout confirms his ability to deliver the coverage 30 min before the event
- 5_min_left - scout confirms his ability to deliver the coverage 5 min before the event
|
| status_type | Type of the status. Possible values: - live
- scheduled
- finished
- cancelled
- interrupted
- deleted
- other
|
| scoutsfeed | Information concerning scouts coverage. Possible values: - yes - means that play by play incidents will be available for the event
- no - means that play by play incidents will not be available for the event
|
| latency | Information about the expected latency. | details Possible values: - null (for the event with scoutsfeed=no parameter)
- 1-2s
- 3-6s
- 7-15s
|
| event_stats_level | Internal information, please do not use this field |
| verified_result | Possible value: - yes - result is verified with an official source
- no - result is not verified with an official source
|
| is_coverage_limited | Determines if event has limited information about players statistics |
| played_time | Only for soccer. Number of seconds passed in the current period, including additional time |
| ....details |
|
|---|
| .....detail |
|
|---|
| id | Unique identifier for the detail. Possible values are different depending on the sport |
| value | Value related to the detail |
| .....participants |
|
|---|
| .....participant |
|
|---|
| counter | Number of participants participant in the event. Participant with counter="1" is the home team, "2" is the away team |
| id | Unique identifier of the participant participant |
| name | Participants name |
| short_name | Participants abbreviated name, max length: 20 characters |
| acronym | Max 3 characters in length mini name, e.g. BAR, REA |
| area_id | Unique identifier for the area represented by the participant |
| area_name | Area name represented by the participant |
| area_code | Max 3 characters in length for the abbreviated area name e.g. GER, POL, FRA |
| ut | Information about the date and time of when the record was last updated. Format UNIX_TIMESTAMP |
| ......results |
|
|---|
| .......result |
|
|---|
| id | Unique identifier for the result. Possible values are different depending on the sport |
| value | Value related to the results |
| ......statsThe stats node |
|
|---|
| is filled only at the moment when some changes were made in this node. This nodes are always returned, but sometimes can include an empty array........stat |
|
|---|
| id | Unique identifier for the statistic. Possible values are different depending on the sport |
| value | Value related to the statistic |
| event_status_stats | Sending only with incidents ending the previous part of the game. Contains statistics from previous part of the game |
|
|
|---|
|
|
|---|
| id | Unique identifier of the participant |
| counter | Number of subparticipant in the event |
| name | Participants name |
| short_name | Participants abbreviated name, max length: 20 characters |
| acronym | Max 3 characters in length mini name, e.g. BAR, REA |
| area_id | Unique identifier for the area represented by the participant |
| area_name | Area name represented by the participant |
| area_code | Max 3 characters in length for the abbreviated area name e.g. GER, POL, FRA |
| ut | Information about the date and time of when the record was last updated. Format UNIX_TIMESTAMP |
| ........results |
|
|---|
| .........result |
|
|---|
| id | Unique identifier for the result |
| value | Value related to the result |
| ........stats |
|
|---|
| .........stat |
|
|---|
| id | Unique identifier for the statistic |
| value | Value related to the statistic |
| .........betting |
|
|---|
| .........bet_statuses |
|
|---|
| name | Internal information, please do not use this node |
| value | Internal information, please do not use this node |