Handicaps Network Africa · via the DotGolf ISV API
The HNA status, told straight
This page exists because handicaps are the one integration a South African club cannot do without, and because we expect it to be read by people whose job is to check it. So it is written to be checked.
What is built
Golf Club Hub includes a complete connector to the DotGolf ISV API, the platform HNA runs on: per-club credentials stored encrypted, a typed client for the published endpoints, a replayable job queue with backoff, a webhook receiver, and a nightly reconciliation. Golf Club Hub computes no handicaps itself: HNA is the authority, and this module reads and reports.
What it is proved against
167 of the product's automated tests run this module against a mock of the DotGolf API built from its published documentation, including its failure modes: rate limits, outages, duplicate members and refused score cards. Proved end to end against that mock:
- Linking a member: created at HNA, duplicates surfaced for a person to decide, linked to an existing record, or run dry with the exact payload shown and nothing sent
- Keeping a member in step: changes to the register queued and synced, with resigned members handled
- Reading handicap indexes into snapshots staff can see but never edit
- Opening a round at check-in: the score intent queued with the tee time, skipped for visitors, silent when the module is off
- Score batches from a field: submitted, completion webhooks applied, one refused card never holding up the rest
- Webhooks: signature-verified, retried, deduplicated; unverified deliveries stored but never acted on
- A nightly reconciliation that reports differences and deliberately fixes nothing on its own
What has not happened yet
No club has issued us credentials, so this connector has never run against live HNA data. Everything above is proved against the mock, and the mock is our best reading of DotGolf's published documentation. Lumanaire has prepared its request to HNA for ISV credentials; South Africa publishes no formal ISV accreditation programme, so the terms are settled with HNA directly, and a club may equally nominate its chosen supplier to HNA itself. Unless and until credentials are issued, the module ships switched off: a club that opens the HNA screen sees exactly what to ask HNA for, and a dry-run button that prints the request it would send without sending anything.
A club running Golf Club Hub in parallel keeps its existing HNA process untouched. Nothing about a parallel run puts a club's handicaps at risk.
To HNA, GolfRSA and DotGolf, should you be reading this: we would welcome the conversation. Write to hello@lumanaire.co.za.