feed.show

Resource information

URL	https://api.softnetsport.com/v2/feed/{event_id}
XSD	https://api.softnetsport.com/assets/API/docs/xsd/feed.show.xsd
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.softnetsport.com/v2/feed/6367.xml?token={{YOUR_TOKEN}}	Returns all incidents from the last 24 hours for the selected event in XML format
https://api.softnetsport.com/v2/feed/6367?token={{YOUR_TOKEN}}	Returns all incidents from the last 24 hours for the selected event in JSON format

Output elements

.messages
..message
id	Unique identifier for the message
type	Possible value: incident event_changes
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
incident_id	Identifier for the incident
incident_name	Name of the incident. e.g. goal, yellow card, red card etc.
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
add_data	Internal attribute, please dont use this attribute
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)
....event
id	Identifier of the event
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
.....details
id	Unique identifier for the detail. Possible values are different depending on the sport
value	Value related to the detail
.....participants
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
......results
id	Unique identifier for the result. Possible values are different depending on the sport
value	Value related to the results
......stats	The 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.
id	Unique identifier for the statistic. Possible values are different depending on the sport
value	Value related to the statistic