One data model, many languages

One API. Every language.

The API separates factual golf data from the words used to display or explain it. Your integration can rely on stable values while presenting them in the language your users or agents need.

Normalization and translation solve different problems.

Language-agnostic data keeps application logic predictable. Translation catalogues turn that data into clear human-facing language.

01

Language-agnostic data

Boolean values, numbers, identifiers, currencies and canonical fields keep the same meaning in every market. A public-access rule does not become a German or English sentence inside the club record.

02

Localized presentation

English and German catalogues provide labels, descriptions, AI prompt wording and other presentation text separately. Applications choose the catalogue they need without changing the underlying data.

JSON

One fact, multiple presentations

Boolean values, numbers, identifiers, currencies and canonical fields keep the same meaning in every market. A public-access rule does not become a German or English sentence inside the club record.

API value
{
  "public_access": true,
  "independent_players_allowed": true,
  "dogs_allowed": null
}
Presentation
ENPublic accessYes
DEÖffentlich zugänglichJa

dogs_allowed: null = Unknown is better than wrong.

One data model, many languages

Available today

English and German are supported first. More catalogues can be added without changing endpoints, records or application logic.

AI

Why this matters for agents

Agents receive compact, unambiguous facts and can generate an answer in the requested language. They do not need to infer business rules from translated source prose.

  1. 01Treat null as unknown in every language.
  2. 02Use canonical values for filtering and decisions.
  3. 03Use the translation catalogue for localized labels and prompt wording.
  4. 04Never translate identifiers, enum values or API field names.

Build one integration for every supported language.

Explore the translation endpoint and the normalized data model in the documentation.

View the documentation