Table API
Endpoints
| URL | Access | |
|---|---|---|
/api/calendars |
documentation | public |
/api/clubs |
documentation | public |
/api/cups |
documentation | public |
/api/games |
documentation | public |
/api/game_events |
documentation | public |
/api/groups |
documentation | public |
/api/leagues |
documentation | public |
/api/national_players |
documentation | public |
/api/players |
documentation | public |
/api/rankings |
documentation | public |
/api/teams |
documentation | public |
/api/topscorers |
documentation | public |
/api/seasons |
documentation | public |
/api/sessions |
documentation | private |
/api/ui/players |
documentation | private |
Localisation (L10N / I18N)
All texts returned in objects are localized to either the default locale or the locale specified with the parameter locale. This parameter applies to all API calls. To specify the locale, use the ISO 639-1 code. The following locales are currently supported:
| Code | Variant |
|---|---|
| en | English |
| de-CH | German (Switzerland) |
| fr-CH | French (Switzerland) |
| it-CH | Italian (Switzerland) |
Dates and numbers are formatted as would be expected for the given locale, except where
- A number is used as an identifier. This is indicated by the data type 'string'.
- A number is special for other reasons, such as the number of goals a team makes. Whereever possible, we apply rules inherent in the domain first.
NOTE the current version of the API defaults to de-CH and only has texts for this locale.
Return Types
Answers from the API are in JSON format. These answer types exist:
Informal conventions used in these JSON format specifications are described in this document.