Versions Compared

Old Version 17

changes.mady.by.user FormerUser1

Saved on

compared with

New Version 18

changes.mady.by.user FormerUser1

Saved on

Key

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

...

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

Possible value:

  • incident
  • event_changes
sourceInternal attribute, please dont use this attribute for you service
utInformation about date and time when message was created. Format UNIX_TIMESTAMP.
...data 
....incidentnode available only if message type
idUnique identifier of the incident occured in the event
incident_idIdentifier of the incident. softnetSPORT API provides the following incidents: incidents.index
incident_nameName of the incident. I.e 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 player or coach is part of. softnetSPORT API provides the following subparticipants: participants.index
subparticipant_nameTeam name which player or coach is part of
infoInternal 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_timeInternal attribute, please dont use this attribute
show_actionInternal 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
nameName 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)
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.index
status_nameName of the current event status
status_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.index
sport_nameName of the sport in which event is played
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 current period
clock_status

Clock status. Possible value:

  • running
  • stopped
resultResult for the event in format: "1:2". Available only for the events contains 2 participants.
area_nameName of area in which competitions are played
competition_idUnique identifier for the competition. softnetSPORT API provides the following competitions: competitions.index
competition_short_nameCompetition short name, max length: 20 characters
season_idUnique identifier for the season.
season_nameName of the season f.e: Premiership 2014/15
stage_idUnique identifier for the stage
stage_nameName of the stage
tour_nameName of the tour in which competition is played
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
  • stoppedsuspended
utInformation about date and time when record was last updated. Format UNIX_TIMESTAMP.
.....details The details 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 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
nameParticipant name
short_nameParticipant short name, max length: 20 characters
acronymMax 3 characters length mini name, f.e: BAR, REA
area_idUnique identifier of the area represented by the participant. softnetSPORT API provides the following areas: areas.index
area_nameArea name represented by the participant
area_codeMax 3 characters length of the short area name f.e: GER, POL, FRA
utInformation about date and time when the record was last updated. Format UNIX_TIMESTAMP
......results The results 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 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 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.
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