events.index
Resource information
URL | https://api.statscore.com/v2/events |
---|---|
Method | GET |
Description | Returns the events related with competitions, seasons, stages and groups |
Cache | 30 seconds |
Authorization required | Yes |
Method parameters
Name | Type | Description |
---|---|---|
There are no method parameters in this resource |
Query parameters
Name | Type | Description |
---|---|---|
token | xsd:string | REQUIRED. There is more information concerning authorization in the API introduction section |
lang | xsd:string | Determines the language for the output data. The complete list of possible languages can be retrieved using the API resource: languages.index |
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 50. Possible values: 5, 10, 25, 50, 100 |
date_from | xsd:string | REQUIRED. If not used, the date will be automatically set for the current day. Selection datetime, format 'yyyy-mm-dd hh:mm:ss'. Date from which events should be returned. If you use a single date_from parameter you will receive all events that start in the 24 hours from the requested date |
date_to | xsd:string | REQUIRED. If not used, the date will be automatically set for the current day. Selection datetime, format 'yyyy-mm-dd hh:mm:ss'. End date of returned events. The maximum period between date_from and date_to parameters is 30 days. This rule is not valid when you use the following query parameter in your request: season_id, stage_id, group_id, participant_id. If you use a single date_to parameter you will receive all events that start in the 24 hours from the requested date |
sport_id | xsd:int | Determines the sport identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible sports can be retrieved using the API resource: sports.index |
area_id | xsd:int | Determines the area identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible areas can be retrieved using the API resource: areas.index |
competition_id | xsd:int | Determines the competition identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible competitions can be retrieved using the API resource: competitions.index |
season_id | xsd:int | Determines the season identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible seasons can be retrieved using the API resource: seasons.index |
stage_id | xsd:int | Determines the stage identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible stages can be retrieved using the API resource: stages.index |
group_id | xsd:int | Determines the group identifier in which the events are played. Possibility to input multiple identifiers, separated by comma. The complete list of possible groups can be retrieved using the API resource: groups.index |
participant_id | xsd:int | Determines the identifier of the participant. The complete list of possible participants can be retrieved using the API resource: participants.index |
multi_ids | xsd:string | List of events identifiers separated by a comma (e.g. 123,234,321) for which you want to get the events details. (Up to 100 ids) |
venue_type | xsd:string | Additional parameter for participant filter. Works only when participant_id query is used. Determines if the provided participant plays as the home or away team.
|
venue_id | xsd:string | Determines the identifier of the venue. The complete list of possible participants can be retrieved using the API resource: venues.index |
sort_type | xsd:string | Determines sort order of data. Possible values:
|
sort_order | xsd:string | Additional parameter for sort_type which determines the direction of sorting (ascending, descending)
|
relation_status | xsd:string | Determines the status of the relation. Possible values:
|
status_id | xsd:string | Determines the identifier of the event status. The complete list of possible statuses can be retrieved using the API resource: statuses.index |
status_type | xsd:string | Determines the identifier of the status type. Can be comma separated string. Possible values: Possible values:
|
coverage_type | xsd:string | Determines coverage type. Possible values:
Possible to determine multiple coverages (e.g. from_venue,from_tv) |
scoutsfeed | xsd:string | Possible values:
Required with booked of the 'ScoutsFeed' product |
events_details | xsd:string | Determines if subnodes of events will be visible. Possible values:
|
competitions_details | xsd:string | Determines if parent nodes of events will be visible. Possible values:
|
item_status | xsd:string | Describes the status for the item (record). Possible values:
|
min_range | xsd:string | Determines the minimum range for displayed events (e.g. min_range=2). |
max_range | xsd:string | Determines the maximum range for displayed events (e.g. max_range=10). |
verified_result | xsd:string | Possible value:
|
product | xsd:string | Possible values:
Required with booked (in the case of 'ScoutSfeed' product with the 'scoutsfeed' parameter) |
booked | xsd:string | Possible value:
Required with product. |
any_scout_id | xsd:int | Used for internal purposes. Determines scout identifier. Only events related to provided scout will be returned. |
tz | xsd:string | Determines timezone for the output data. The complete list of possible time zones is included in the API introduction section |
timestamp | xsd:unix_timestamp | Selection date, format UNIX_TIMESTAMP. Only changes in events that occurred or were updated after this timestamp will be returned. |
Method calling examples
Link | Description |
---|---|
https://api.statscore.com/v2/events?token={{YOUR_TOKEN}} | Returns a list of all events in JSON format |