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 27 Next »

Resource information

URLhttps://api.statscore.com/v2/events/{eventId}/incidents
MethodGET

Description

Returns a list of incidents for the selected event.

CacheNot cached
Authorization requiredYes
Internal methodYes

Method parameters

NameData typeDescription
event_idxsd:intREQUIRED. The requested event identifier

Query parameters

NameTypeDescription
statusesxsd:stringDetermines incidents status identifiers, separated by a comma (e.g. 123,234,321) 
incidentsxsd:stringDetermines incidents identifiers, separated by a comma (e.g. 123,234,321)
importantxsd:string

Determines only important or not important incidents.

Possible values: yes, no.

updatedxsd:string

Determines only updated or not updated incidents.

Possible values: yes, no.

deletedxsd:string

Determines to list only deleted or not deleted incidents.

Possible values: yes, no.

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 500

Possible values: 5, 10, 25, 50, 100, 250, 500

sort_order xsd:string

Additional parameter for sort_type which determines the direction of sorting (ascending, descending).

The resource is sorted by sport-specific status then after the time in that status.

By default the value of "desc" is set. Possible values:

  • asc - sort ascending
  • desc - sort descending

Method calling examples

Output elements

.event_incidents
Data type
Description
..incident

idxsd:arrayIncident identifier. Unique for sport.
action

xsd:string

Describes type of operation. Possible values:

  • insert
  • update
  • delete
old_idxsd:intDEPRECATED. Old Id
event_idxsd:intREQUIRED. The event identifier
incident_idxsd:intIncident id in data.sports.incidents node for event. The complete list of possible incidents can be retrieved using the API resource: sports.show
attribute_idsxsd:arrayAttributes identifiers related to incident, separated by a comma (e.g. [397, 398])
participant_idxsd:intParticipant id
participant_team_idxsd:intParticipant team id
participant_namexsd:stringParticipant name.
status_idxsd:intStatus id in data.sports.statuses node for event. The complete list of possible statuses can be retrieved using the API resource: statuses.index
minutexsd:intIncident time: minute
secondxsd:intIncident time: second
home_scorexsd:intHome Score
away_scorexsd:intAway Score
home_score1xsd:intHome Score 1
away_score1xsd:intAway Score 1
home_score2xsd:intHome Score 2
away_score2xsd:intAway Score 2
x_posxsd:intBall position on X axis (percentage)
y_posxsd:intBall position on Y axis (percentage)
add_dataxsd:stringCustom information
display_infoxsd:stringLabel for incidents
counterxsd:intSubsequent number of the incydent type in the event. Example: 5th goal in the match.
ctxsd:intCreated date
utxsd:intLast update date
dtxsd:intDeleted date
old_added_idxsd:intDEPRECATED. Old Id
sort_typexsd:string

Determines sort order of data. Possible values:

  • id - Incidents are sorted by the id of the Incident
forxsd:stringDetermine what the participant includes incident
  • all
  • own
  • rival
  • none
  • No labels