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.
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.
Language-agnostic data keeps application logic predictable. Translation catalogues turn that data into clear human-facing language.
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.
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.
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.
{
"public_access": true,
"independent_players_allowed": true,
"dogs_allowed": null
}dogs_allowed: null = Unknown is better than wrong.
English and German are supported first. More catalogues can be added without changing endpoints, records or application logic.
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.
Explore the translation endpoint and the normalized data model in the documentation.
View the documentation