Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Resource information

Package
URLhttps://api.softnetsportstatscore.com/v2/feed/{event_id}
XSDhttps://api.softnetsport.com/assets/API/docs/xsd/feed.show.xsd
MethodGET

Description

Returns all incidents from a single event.
This resource is included in the SCOUTSFEED packageCache0 seconds
Authorization requiredYes

...

NameTypeDescription
event_idxsd:intREQUIRED. The requested event identifier

 


Query parameters

NameTypeDescription
tokenxsd:string

REQUIRED. More information concerning oAuth token: oAuth 2.0 authorization authorization in API introduction section

pagexsd:intDetermines offset of paginated data. Default value is 1 which means first page.
limitxsd: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

importantxsd: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_traderxsd: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
timestampxsd:unix_timestampSelection date, format UNIX_TIMESTAMP. Only incidents that occurred after this timestamp will be returned.
timestamp_toxsd:unix_timestampSelection date, format UNIX_TIMESTAMP. Only incidents that occurred before this timestamp will be returned.

 

Method calling examples

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

Determines type of message

  • incident
  • event
incident_idsxsd:stringList of incidents type identifiers separated by a comma (e.g. 123,234,321) for which you want to get the incident details.
status_idxsd:intDetermines the event status identifier.


Method calling examples

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

Output elements

.. 
.messagesfeed 
idUnique identifier for the message
uuididUniversally Unique identifier 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_changes
sourceInternal attribute, please dont use this attribute
utInformation about the date and time of when the message was created. Format UNIX_TIMESTAMP.
...data 
....incidentnode available only if message type is incident
idUnique identifier for the incident occurred in the event. This feature will be removed in a future release. 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)
incident_idIdentifier for the incident. softnetSPORT API provides the following incidents: incidents.indexincident 
incident_nameName of the incident. e.g. goal, yellow card, red card etc.
attribute_idsAttributes 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_idUnique identifier for participants name (player, team or coach) related to incident. softnetSPORT API provides the following participants: participants.index
participant_nameParticipants name (player, team or coach) related to incident.    
subparticipant_idTeam id for which the player or coach is part of. softnetSPORT API provides the following subparticipants: participants.indexof 
subparticipant_nameTeam name for which the player or coach is part of
infoInternal attribute, please dont use this attribute
important_for_trader

Possible values:

  • yes
  • no
importantInternal attribute, please dont use this attribute
add_dataInternal attribute, please dont use this attribute
show_popupInternal attribute, please dont use this attribute
show_scoresInternal attribute, please dont use this attribute
show_actionDescribes type of scout operation for the incidentInternal attribute, please dont use this attribute
show_timeInternal attribute, please dont use this attribute
show_on_timelineInternal attribute, please dont use this attribute
event_timeInformation when the incident occurs in format MM:SS
event_status_idUnique identifier of the event status
event_status_nameName of the event status
period_timerInformations regarding game clock
direction

Contains information about timer direction. Possible values:

  • down
  • up
timeTime in sync with the game clock
x_posBall position on X axis (percents)
y_posBall 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
idIdentifier of the event
action

Describes type of operation for the event. Possible values:

  • insert - new incident event 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)event was updated
  • delete - incident event was deleted (e.g. when the scout adds an incident by mistake, he can delete it)
....event 
idIdentifier
nameName of the event
start_dateStart 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_idUnique identifier of the event status. softnetSPORT API provides the following statuses: statuses.index
sport_idIdentifier of the sport which the event is played
round_idUnique identifier for the round in which event is played. softnetSPORT API provides the following sports: sports.indexPossibble null value 
round_nameName of the round. Possible null value.
dayDay 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_timeNumber 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_idIdentifier for the area in which competitions are played
competition_idUnique identifier for the competition. softnetSPORT API provides the following competitions: competitions.indexcompetition 
season_idUnique identifier for the season.
stage_idUnique identifier for the stage
tour_idUnique identifier for the tour in which competition is played. softnetSPORT API provides the following tours: tours.indexplayed 
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
event_stats_levelInternal 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_limitedDetermines if event has limited information about players statistics
played_timeOnly for soccer. Number of seconds passed in the current period, including additional time
.....details 
......detail
idUnique identifier for the detail. Possible values are different depending on the sport. For more information please find node details in the sports.show: sports.showsport 
valueValue related to the detail
.....participants 
......participant
counterNumber of participans in the event. Participant with counter="1" is the home team, "2" is the away team
idUnique identifier of the participant. softnetSPORT API provides the following subparticipants: participants.indexparticipant 
......stats
......results .stat
idUnique identifier for the resultstatistic. Possible values are different depending on the sport. For more information please find node details in the sports.show: sports.show
valueValue related to the resultsstatistic
......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.results
.......result
idUnique identifier for the statisticresult. Possible values are different depending on the sport. For more information please find node details in the sports.show: sports.showthe sport 
valueValue related to the results
event_status_statsSending only with incidents ending the previous part of the game. Contains statistics from previous part of the game
......subparticipants

.......subparticipant

idUnique identifier of the participant
counterNumber of subparticipant in the event
nameParticipants name
short_nameParticipants abbreviated name, max length: 20 characters
acronymMax 3 characters in length mini name, e.g. BAR, REA
area_idUnique identifier for the area represented by the participant 
area_nameArea name represented by the participant
area_codeMax 3 characters in length for the abbreviated area name e.g. GER, POL, FRA
utInformation about the date and time of when the record was last updated. Format UNIX_TIMESTAMP
........results
.........result
idUnique identifier for the result
valueValue related to the result
........stats
.........stat
idUnique identifier for the statistic
valueValue related to the statistic
.........betting
.........bet_statuses
nameInternal information, please do not use this node
valueInternal information, please do not use this node