Versions Compared

Key

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

This type of message is sent when an incident occurs during the event/match that is running. The message includes information concerning the last incident and ALL event details (results, statistics) are updated in real time.

...


.message
idUnique identifier for the message
type

incident

sourceInternal attribute, please don't use this attribute
utInformation about the date and time of when the message was created. Format UNIX_TIMESTAMP
..data
...incident
idUnique identifier for the incident that occurred in the event
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)
incident_idIdentifier for the incident
incident_nameName of the incident. e.g. goal, yellow card, red card etc.
attribute_idsAttributes 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 for the participant (player, team or coach) name related to incident 
participant_nameParticipant's (player, team or coach) name related to incident.  
subparticipant_idTeam id that the player or coach is part of 
subparticipant_nameTeam name that the player or coach is part of
infoInternal attribute, please don't use this attribute
important_for_trader

Possible values:

  • yes
  • no
importantInternal attribute, please don't use this attribute
add_dataInternal attribute, please don't use this attribute
show_popupInternal attribute, please don't use this attribute
show_scoresInternal attribute, please don't use this attribute
show_actionInternal attribute, please don't use this attribute
show_timeInternal attribute, please don't use this attribute
show_on_timelineInternal attribute, please don't use this attribute
event_timeInformation when the incident occurs in format MM:SS
event_status_idUnique identifier for the event status 
event_status_nameName of the event status
x_posBall position on X axis (percentage value from 0 to 100)
y_posBall position on Y axis (percentage value from 0 to 100)
...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
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 for the event status. The list of available statuses can be found in the API service method: statuses.index
sport_idIdentifier for the sport in which the event is played. The list of available sports can be found in the API service method: sports.index
round_idThe list of available rounds can be found in the API service method: rounds.index. Possible null value
round_nameName of the round. Possible null value
dayDay of the season. This attribute is deprecated and will no longer used
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. The list of available competitions can be found in the API service method: 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. The list of available competitions can be found in the API service method: tours.index
gender

Competition gender. Possible values:

  • male
  • female
  • mixed
bet_status

Bet status. Possible values:

  • active
  • suspended
bet_cards

Booking market status. Possible values:

  • active
  • suspended
bet_corners

Corners market status. Possible values:

  • 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 status. Possible values:

  • live
  • scheduled
  • finished
  • cancelled
  • interrupted
  • deleted
  • other
.....details
idUnique identifier for the event details e.g: 1st quarter start time, length of the period. Possible values are different depending on the sport. 
valueValue related to the event detail
.....participantsOnly last changed participant will be sent in the message.
counterNumber of participant in the event. Participant with counter="1" is the home team, "2" is the away team
idUnique identifier of the participant. The list of available participants can be found in the API service method: participants.index
nameParticipant name
short_nameParticipants abbreviated name, max length: 20 characters
acronymMax 3 characters in length mini name, e.g. BAR, REA
area_idDetermines the area represented by the participant. The complete list of possible areas can be retrieved using the API resource: areas.index
area_nameArea name represented by the participant
area_codeMax 3 characters in length of 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
idUnique identifier for the result. Possible values are different depending on the sport. For more information please find node details in the sports.show API method 
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 API method
valueValue related to the statistic