Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

This type of message is sent when changes are made in the event e.g. stats were edited/corrected or event start date was changed etc.

This message type is included in feed.index and feed.show methods available in API service, so at any time you can retrieve all changes from selected event

Message structure

.message 
idUnique identifier for the message
type

incident

sourceInternal attribute, please dont use this attribute
utInformation about the date and time of when the message was created. Format UNIX_TIMESTAMP.
...data 
....event 
idIdentifier of the event
start_dateStart date for the event in format: YYYY-MM-DD hh:mm
nameName of the event
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
round_name Unique identifier for the round in which event is played. Possible null value. softnetSPORT API provides the following rounds: rounds.index
round_idName 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 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 event details f.e: 1st quarter start time, length of the period. Possible values are different depending on the sport.  
valueValue related to the event 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
......stats 
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
....incidentIn case of event message type the incident attribute is null.

 

Feed examples

  • No labels