Output elements
...
Possible value:
- incident
- event
...
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)
...
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.
...
Possible values:
- yes
- no
...
Describes type of operation for the event. Possible values:
- insert - new event generated
- update - event was updated
- delete - event was deleted
...
Determines when the result/score of the event is updated. Possible values:
- yes - result/score is updated only when event is finished
- no - result/score is updated during the event
...
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 events incidents (max. latency around 60 seconds)
...
Determines if event is played at a neutral venue. Possible values:
- yes
- no
...
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 status. Possible value:
- running - the clock is in the running mode
- stopped - the clock is in the stopped mode
...
Competition gender. Possible values:
- male
- female
- mixed
...
Bet status. Possible values:
- active
- suspended
...
Changed when there is a possibility of a card. Possible value:
- active
- suspended
...
Changed when there is a possibility of a corner. Possible value:
- active
- suspended
...
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
...
Type of the status. Possible values:
...
Resource information
...
Description
...
Method parameters
...
Query parameters
...
REQUIRED. More information concerning authorization in API introduction section
...
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
...
Determines if incident is important e.g. goals, cards, substitution. By default all types are included.
Allowed values:
- yes - returns only important incidents
- no - returns all incident types
...
Determines the type of incidents (if they are important for the trader). By default all types are included.
Allowed values:
- yes - returns only incidents important for the trader
- no - returns only incidents not important for the trader
...
Determines type of message
- incident
- event
...
Method calling examples
...
...
...
Resource information
URL | https://api.statscore.com/v2/feed/{event_id} |
---|---|
Method | GET |
Description | Returns all incidents from a single event. |
Cache | 0 seconds |
Authorization required | Yes |
Method parameters
Name | Type | Description |
---|---|---|
event_id | xsd:int | REQUIRED. The requested event identifier |
Query parameters
Name | Type | Description |
---|---|---|
token | xsd:string | REQUIRED. More information concerning authorization in API introduction section |
page | xsd:int | Determines offset of paginated data. Default value is 1 which means first page. |
limit | xsd: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 |
important | xsd:string | Determines if incident is important e.g. goals, cards, substitution. By default all types are included. Allowed values:
|
important_for_trader | xsd:string | Determines the type of incidents (if they are important for the trader). By default all types are included.
|
timestamp | xsd:unix_timestamp | Selection date, format UNIX_TIMESTAMP. Only incidents that occurred after this timestamp will be returned. |
timestamp_to | xsd:unix_timestamp | Selection date, format UNIX_TIMESTAMP. Only incidents that occurred before this timestamp will be returned. |
type | xsd:string | Determines type of message
|
incident_ids | xsd:string | List of incidents type identifiers separated by a comma (e.g. 123,234,321) for which you want to get the incident details. |
status_id | xsd:int | Determines the event status identifier. |
Method calling examples
Link | Description |
---|---|
https://api.statscore.com/v2/feed/6367?token={{YOUR_TOKEN}} | Returns all incidents from the last 24 hours for the selected event in JSON format |