Versions Compared

Old Version 30

changes.mady.by.user FormerUser1

Saved on

compared with

New Version 31

changes.mady.by.user FormerUser1

Saved on

Key

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

...

.messages 
..message 
idUnique identifier for the message
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
incident_idIdentifier for the incident. softnetSPORT API provides the following incidents: incidents.index
incident_nameName of the incident. 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_nameParticipants (player, team or coach) name related to incident.  
subparticipant_idTeam id that the player or coach is part of. softnetSPORT API provides the following subparticipants: participants.index
subparticipant_nameTeam name 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 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 
idIdentifier of the event
nameThe name of the event
start_dateStart date for the event in format: YYYY-MM-DD hh:mm
ft_only

Determines if only the full time result/score of the event is 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 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 event incidents (max. latency around 60 seconds)
status_idUnique identifier of the event status. softnetSPORT API provides the following statuses: statuses.index
sport_idIdentifier for the sport in which the event is played. softnetSPORT API provides the following sports: sports.index
dayDay of the season
neutral_venue

Determines if event is played at a neutral venue. Possible values:

  • yes
  • no
item_status

Describes status 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
area_idIdentifier for the area in which the 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 for the tour in which a 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 participants 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
......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