Skip to end of metadata
Go to start of metadata
| URL | https://api.statscore.com/v2/mapped-events |
|---|
| Method | GET |
|---|
Description | Returns a list of events booked and mapped by the client for the selected product.
Please note: the list will only contain events with the status: "finished", "live" and "scheduled" including events for the next 5 days.
The default order for returned data is: start date - ascending. |
|---|
| Cache | 300 seconds (5 min.) |
|---|
| Authorization required | - IP whitelisting (preferred)
OR - Auth Token
|
|---|
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 |
| product | xsd:string | REQUIRED. Determines the product in which given events were booked. Possible values: - livescorepro
- scoutsfeed
- scoreframe
- prematchcenter
|
| client_id | xsd:int | Assigned by the API administrator |
| mapped_status | xsd:string | Determines if events are mapped with client_event_id. Possible values: - mapped - display events mapped with customer
- unmapped - display events unmapped with the customer
- all - display all events (mapped and unmapped)
|
| booked | xsd:string | Determines if events are booked for you. Possible values: |
| page | xsd:int | Determines offset of paginated data. The default value is 1 which means the first page |
| limit | xsd:int | Determines the maximum number of returned records on the page. Used in paginated data. Default value is 500. Possible values: 5, 10, 25, 50, 100, 250, 500 |
Method calling examples
Output elements
| mapped_events |
|---|
| mapped_events > events |
|---|
| id | Unique identifier for the event | | client_event_id | Unique event identifier for the client. | | name | Name of the event e.g. Spain - Italy | | start_date | Date when the event starts in the format DATE_TIME (2015-03-01 11:02) | | ft_only | Determines when the result/score of the event is updated. 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_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)
| | scoutsfeed | Information concerning scouts coverage. Possible values: - yes - means that play by play incidents will be available for the event
- no - means that play by play incidents will not be available for the event
| | sport_id | Unique identifier for the sport in which event is played. The complete list of possible sports can be retrieved using the API resource: sports.index | | sport_name | Name of the sport in which event is played | | area_id | Unique identifier for area in which competitions are played. The complete list of possible areas can be retrieved using the API resource: areas.index | | area_name | Name of area in which competitions are played. Possible translation of the attribute | | competition_id | Unique identifier for the competition | | competition_short_name | Abbreviated name of the competition | | inverted_participants | Information about inverted order of participants (e.g. Team B - Team A instead of Team A - Team B). Possible values: | | event_stats_lvl | Information about the statistics level. Possible values: | | event_stats_lvl_live | Information about expected statistics level when the match is LIVE. Possible values: | | event_stats_lvl_after | Information about expected statistics level after the end of the match. Possible values: | | latency | Information about the expected latency. Possible values: - null (for the event with scoutsfeed=no parameter)
- 1-2s
- 3-6s
- 7-15s
|
|