Skip to main content

One API. Every language.

The API separates facts from presentation language. Club records contain stable fields, canonical values, booleans, numbers and identifiers. They do not change when the application switches language.

Language-agnostic records​

{
  "public_access": true,
  "independent_players_allowed": true,
  "dogs_allowed": null
}

Application logic should filter and decide using these values, never translated labels.

Translation catalogues​

English and German catalogues provide localized labels, descriptions and AI prompt wording separately:

GET /v1/translations/en
GET /v1/translations/de

More languages can be added without changing endpoints, records or integration logic.

Rules for applications and agents​

  • Never translate field names, identifiers or canonical enum values.
  • Treat null as unknown in every language.
  • Use the catalogue for labels and explanatory wording.
  • Ask the model to answer in the user’s requested language.
  • Do not derive access rules from translated source prose when a normalized value is available.