Versions Compared

Key

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

Resource information

URLhttps://api.
softnetsport
statscore.com/v2/feed
XSDhttps://api.softnetsport.com/assets/API/docs/xsd/feed.index.xsd
MethodGET

Description

Returns incidents generated by the scouts for all events in the
events from
last 24 hours
PackageThis resource is included in the SCOUTSFEED package
Cache0 seconds
Authorization requiredYes

Method parameters

NameTypeDescription
There are
not
no method parameters in this
resource 
resource 

 


Query parameters

NameTypeDescription
tokenxsd:stringREQUIRED.
More
 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 50

Possible values: 5, 10, 25, 50, 100, 250, 500

timestampxsd:unix_timestamp

Selection date, format UNIX_TIMESTAMP. Only incidents

which occured

that occurred or

was

were updated after this timestamp will be returned.

By default (if no parameter given) incidents from last 24 hours.

timestamp_toxsd:unix_timestampSelection date, format UNIX_TIMESTAMP. Only incidents
occured
that occurred before this timestamp will be returned.
important_for_traderxsd:string

Determines type of incidents (if

is

it's important for trader). By default all types are included.
Allowed values:

  • yes - returns only incidents important for trader
  • no - returns only incidents not important for trader
sport_idxsd:intIdentifier of the sport. Allows
to filter
incidents for the selected sport
. softnetSPORT API provides the following sports: sports.index

 

Method calling examples

Link
Description
https://api.softnetsport.com/v2/feed.xml?token={{YOUR_TOKEN}}Returns all event's incidents from last 24 hours in XML format
to be filtered
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.
softnetsport
statscore.com/v2/feed?token={{YOUR_TOKEN}}Returns all event
's
incidents from the last 24 hours in JSON format

https://api.

softnetsport

statscore.com/v2/feed

.xml

?token={{YOUR_TOKEN}}&sport_id=1

Returns all
events's
event incidents from the last 24 hours
in
for basketball events

Output elements

.
messages
feed
 ..

idUnique identifier for the message
 idUnique identifier of the incident occured in the event
uuidUniversally 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
_changes
sourceInternal attribute, please dont use this attribute
for you service
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
of
for the incident
occured
occurred in the event
action

Describes type of scout operation for the incident. Possible values:

incident_idIdentifier of the incident. softnetSPORT API provides the following incidents: incidents.index
  • 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 
incident_nameName of the incident.
I
e.g.
e
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_idUnique identifier of participant (player, team or coach) name related to
incident. softnetSPORT API provides the following participants: participants.index
incident 
participant_name
Participant
Participants (player, team or coach) name related to incident.
  
  
subparticipant_idTeam id
which
that the player or coach is part
of. softnetSPORT API provides the following subparticipants: participants.index
of 
subparticipant_nameTeam name
which
that 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_
time
actionInternal attribute, please dont use this attribute
show_
actionnameName
timeInternal attribute, please dont use this attribute
show_on_timelineInternal attribute, please dont use this attribute
action

Describes type of scout operation on the incident. Possible values:

  • insert - new incident generated by the scout
  • update - incident was updated by the scout (f.e. incident "yellow card" is updated when scout fill the name of the player (participant)
  • delete - incident was deleted (f.e. when scout add some incident by mistake, he can delete it)
utInformation about date and time when record was last updated. Format UNIX_TIMESTAMP.....event idIdentifier of the event
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)
...eventnode available only if message type is event
idIdentifier 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
nameThe name of the event
start_dateStart date for the event in format: YYYY-MM-DD hh:mm
ft_only

Determines

when

if only the full time result/score of the event is

updated

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
relating
  • relaying the event directly from the stadium (max. latency 1 second)
  • from_low_latency_tv - means the scout is
relating
  • relaying the event from tv transmission (max. latency 3 seconds)
  • from_tv - means the scout is
relating
  • relaying the event from tv transmission (max. latency 8 seconds)
  • basic - for this type of coverage we don't provide detailed
events
  • event incidents (max. latency around 60 seconds)
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 won't be available for the event
status_idUnique identifier of the event
status. softnetSPORT API provides the following statuses: statuses.indexstatus_nameName of the current event statusstatus_type

Type of the status. Possible values:

  • live
  • scheduled
  • finished
  • cancelled
  • interrupted
  • deleted
  • other
sport_idIdentifier of the sport which the event is played. softnetSPORT API provides the following sports: sports.indexsport
status 
sport_idIdentifier for the sport in which the event is played 
round_idUnique identifier for the round in which event is played. Possible null value  
round_nameName of the
sport in which event is played
round. Possible null value.
dayDay
in
of the season
neutral_venue

Determines if event is played

on

at a neutral venue. Possible values:

  • yes
  • no
item_status

Describes status

of

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_timeNumber of seconds that have passed in the current period
clock_status

Clock status. Possible value:

  • running
  • stopped
result 
area_
name 
idIdentifier for the area in which the competitions are played
competition_id
 competition_short_name season_id season_name stage_id stage_name tour_name tour_id gender bet_status utInformation about date and time when record was last updated. Format UNIX_TIMESTAMP......details 
Unique identifier for the competition 
season_idUnique identifier for the season.
stage_idUnique identifier for the stage
tour_idUnique identifier for the tour in which a 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
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.show
valueValue related to the detail
.
....participants
 

.....participant
counterNumber of participant 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.index
participant 
name
Participant
Participants name
short_name
Participant short
Participants abbreviated name, max length: 20 characters
acronymMax 3 characters in length mini name,
f
e.g.
e:
BAR, REA
area_idUnique identifier
of
for the area represented by the
participant. softnetSPORT API provides the following areas: areas.index
participant 
area_nameArea
name represented
name represented by the participant
area_codeMax 3 characters in length
of
for the
short
abbreviated area name
f
e.g.
e:
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. 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 results
......stats
 

.......stat
idUnique identifier for the statistic. 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 statistic
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