feed.show

Resource information

URL	https://api.statscore.com/v2/feed/{event_id}
Method	GET
Description	Returns all incidents from a single event.
Cache	0 seconds
Authorization required	Yes

Method parameters

Name	Type	Description
event_id	xsd:int	REQUIRED. The requested event identifier

Query parameters

Name	Type	Description
token	xsd:string	REQUIRED. More information concerning authorization in API introduction section
page	xsd:int	Determines offset of paginated data. Default value is 1 which means first page.
limit	xsd:int	Determines maximum number of returned records on page. Used in paginated data. Default value is 500. Possible values: 5, 10, 25, 50, 100, 250, 500
important	xsd:string	Determines if incident is important e.g. goals, cards, substitution. By default all types are included. Allowed values: yes - returns only important incidents no - returns all incident types
important_for_trader	xsd:string	Determines the type of incidents (if they are important for the trader). By default all types are included. Allowed values: yes - returns only incidents important for the trader no - returns only incidents not important for the trader
timestamp	xsd:unix_timestamp	Selection date, format UNIX_TIMESTAMP. Only incidents that occurred after this timestamp will be returned.
timestamp_to	xsd:unix_timestamp	Selection date, format UNIX_TIMESTAMP. Only incidents that occurred before this timestamp will be returned.
type	xsd:string	Determines type of message incident event
incident_ids	xsd:string	List of incidents type identifiers separated by a comma (e.g. 123,234,321) for which you want to get the incident details.
status_id	xsd:int	Determines the event status identifier.

Method calling examples

Link	Description
https://api.statscore.com/v2/feed/6367?token={{YOUR_TOKEN}}	Returns all incidents from the last 24 hours for the selected event in JSON format

Output elements

.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: incident event
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_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 for participants name (player, team or coach) related to incident
participant_name	Participants name (player, team or coach) related to incident.
subparticipant_id	Team id for which the player or coach is part of
subparticipant_name	Team name for which the player or coach is part of
info	Internal attribute, please dont use this attribute
important_for_trader	Possible values: yes no
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
show_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: down up
time	Time in sync with the game clock
x_pos	Ball position on X axis (percents)
y_pos	Ball position on Y axis (percents)
additional_info	Contains additional information: goalkeeper_id, assistant_id (eg. "assistant_id": 178565) assistant_name (eg. "assistant_name": "Marco Reus")
...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	Name of the event
start_date	Start date for the event in format: YYYY-MM-DD hh:mm
ft_only	Determines when the result/score of the event is updated. Possible values: yes - result/score is updated only when 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 events incidents (max. latency around 60 seconds)
status_id	Unique identifier of the event status
sport_id	Identifier of the sport which the event is played
round_id	Unique identifier for the round in which event is played. Possibble 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: yes no
item_status	Describes status of the item (record). Possible values: active - the record is active deleted - the record was deleted by the admin. In case when event was added by mistake
clock_time	Number of seconds passed in the current period
clock_status	Clock status. Possible value: running - the clock is in the running mode stopped - the clock is in the stopped mode
area_id	Identifier for the area in which competitions are played
competition_id	Unique identifier for the competition
season_id	Unique identifier for the season.
stage_id	Unique identifier for the stage
tour_id	Unique identifier for the tour in which competition is played
gender	Competition gender. Possible values: male female mixed
bet_status	Bet status. Possible values: active suspended
bet_cards	Changed when there is a possibility of a card. Possible value: active suspended
bet_corners	Changed when there is a possibility of a corner. Possible value: active suspended
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. Possible values: null (for the event with scoutsfeed=no parameter) 1-2s 3-6s 7-15s
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 participans in the event. Participant with counter="1" is the home team, "2" is the away team
id	Unique identifier of the participant
......stats
.......stat
id	Unique identifier for the statistic. Possible values are different depending on the sport
value	Value related to the statistic
......results
.......result
id	Unique identifier for the result. Possible values are different depending on the sport
value	Value related to the results
event_status_stats	Sending only with incidents ending the previous part of the game. Contains statistics from previous part of the game.
.........betting
.........bet_statuses
name	Internal information, please do not use this node
value	Internal information, please do not use this node
......subparticipants
.......subparticipant
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