Versions Compared

Old Version 21

changes.mady.by.user Matthew Francis

Saved on

compared with

New Version 22

changes.mady.by.user Matthew Francis

Saved on

Key

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

...

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

Description

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

...

NameTypeDescription
tokenxsd:stringREQUIRED. More information concerning oAuth token: oAuth 2.0 authorization
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 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 to be filtered. softnetSPORT API provides the following sports: sports.index

...

Link
Description
https://api.softnetsport.com/v2/feed.xml?token={{YOUR_TOKEN}}Returns all event 's incidents from the last 24 hours in XML format
https://api.softnetsport.com/v2/feed?token={{YOUR_TOKEN}}Returns all event 's incidents from the last 24 hours in JSON format

https://api.softnetsport.com/v2/feed.xml?token={{YOUR_TOKEN}}&sport_id=1

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

...

.messages 
..message 
idUnique identifier of the a incident occured that occurred in the event
type

Possible value:

  • incident
  • event_changes
sourceInternal attribute, please dont use this attribute for your service
utInformation about the date and time of when the message was created. Format UNIX_TIMESTAMP.
...data 
....incidentnode available only if message type
idUnique identifier of for the incident occured occurred in the event
incident_idIdentifier of for the incident. softnetSPORT API provides the following incidents: incidents.index
incident_nameName of the incident. Ie.e g goal, yellow card, red card etc.
participant_idUnique identifier of participant (player, team or coach) name related to incident. softnetSPORT API provides the following participants: participants.index
participant_nameParticipant (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
subparticipant_nameTeam name which that the player or coach is part of
infoInternal attribute, please dont use this attribute
add_dataInternal attribute, please dont use this attribute
action

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

  • insert - new incident generated by the scout
  • update - incident was updated by the scout (fe.eg. incident "yellow card" is updated when scout fill fills in the name of the player (participant)
  • delete - incident was deleted (fe.eg. when the scout add some adds an incident by mistake, he can delete it)
....event 
idIdentifier of the event
start_dateStart date for the event in format: YYYY-MM-DD hh:mm
ft_only

Determines when the result of the event is updated. Possible values:

  • yes - result updated only when event is finished 
  • no - result updated during the event
coverage_type

Type of event coverage. Possible values:

  • from_venue - means the scout is relating the event directly from the stadium (max. latency 1 second)
  • from_low_latency_tv - means the scout is relating the event from tv transmission (max. latency 3 seconds)
  • from_tv - means the scout is relating 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. softnetSPORT API provides the following sports: sports.index
dayDay in the season
neutral_venue

Determines if event is played on 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
  • stopped
area_idIdentifier of  the area in which competitions are played
competition_idUnique identifier for the competition. softnetSPORT API provides the following competitions: competitions.index
season_idUnique identifier for the season.
stage_idUnique identifier for the stage
tour_idUnique identifier of the tour in which competition is played. softnetSPORT API provides the following tours: tours.index
gender

Competition gender. Possible values:

  • male
  • female
  • mixed
bet_status

Bet status. Possible values:

  • active
  • suspended
.....details 
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 
counterNumber of participant in the event. Participant with counter="1" is home team, "2" is away team
idUnique identifier of the participant. softnetSPORT API provides the following subparticipants: participants.index
......results 
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
......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.
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