Skip to content

Data reference

What a given sport can actually return: which statuses its matches move through, which result ids carry the score, which statistics and incidents exist. All of it comes fromGET /v2/sports/{id}, so these tables cannot drift from the API - they can only be stale, and the build refreshes them.

SportidStatusesResultsIncidentsStatisticsDetailsClock
Alpine skiing209250102no
Am. football8301611312118yes
Athletics53124200no
Badminton29261783209no
Baseball760271468830no
Basketball1301610315221yes
Basketball 3x38013584469yes
Beach volleyball19171165395no
Biathlon129250242no
Bobsleigh257242222no
Bowls47221711229no
Boxing4340585726no
Cricket272414966416no
Cross country24925062no
Curling287242121no
Cycling1310050117no
Darts173639137617no
Figure Skating52724282no
Formula 136182994420no
Freestyle skiing497242222no
Futsal1622101096216yes
Golf3217125721826no
Handball6261210418517yes
Ice Hockey325139513717yes
Luge237242222no
Moto GP3882502110no
Multisport255004200no
Nascar37624204no
Nordic combined228242142no
Padel81201576010no
Roller hockey831884203no
Rugby152110995414yes
Rugby League792010974113yes
Short Track50724242no
Skeleton517242222no
Ski jumping11182825215no
Ski Mountaineering82724262no
Snooker1481381263440no
Snowboarding317242202no
Soccer5211012546523yes
Speed skating21824272no
Speedway266545130297no
Table tennis462821821411no
Tennis420211085613no
Volleyball22015917914no
Waterpolo3319963012yes

Why this is generated and not written

In the Confluence space the same content is five pages per sport times sixteen sports - about eighty tables kept by hand. Every one of them is derivable from a single endpoint, so keeping them by hand only creates drift that nobody notices. Here the data is the source and the pages are output.

Two things the API does not carry, and which stay hand-written: the prose explainingwhy a field behaves the way it does (see the recipes) and the per-incident notes from support. Those live in the content layer, attached to generated rows.