Catalog data ships as soon as each change is approved, usually several times a week. Every Monday we publish a note on the changelog covering the previous Monday to Sunday (UTC).
Sources and review. Values come from manufacturer specifications, manufacturer press material and launch coverage. A new club is added only after a person approves it. A correction to an existing club is approved by a person, or by an automated check that confirms the value appears in its retained source.
Identifiers. A club's clb_ id and a variant's var_ id never change and are never reused. A renamed club's old slug redirects (301) to the new one. A removed club answers 410 Gone.
Detecting changes. Every document carries updated_at and an ETag. Every catalog response names its release in Golfapi-Catalog-Release, and GET /changes?after=<release> lists the clubs changed since the release you last read.
API versions. New fields, endpoints and filters ship in the current version and are listed on the changelog. Removing a field, moving it out of a document, or changing its type happens only in a new dated version. When a new version ships, the previous one keeps serving for at least 90 days, and its responses carry Deprecation and Sunset headers with the date it stops. A security or legal removal can take effect at once and is explained on the changelog. The current version is 2026-10-02; Response versions explains what a version change means for your integration.
Corrections. Report a correction with the club, the field and the page that states the value. You get a COR- reference, and one email when the correction is published or with the reason it was declined. A person decides every reported value. An accepted correction appears in that week's note.
History. The API serves the current release only.