Stream Hole19 data. Straight from the phone.
Hole19 asks for permission to write two things to Apple Health — active energy and workouts — so each tracked round crosses as a golf session with the calories burned walking it, and Sahha’s SDK reads them into your app alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Golf session
- 218 min
- Active energy
- 842 kcal
Identical schema across 500+ sources
Your users connect Hole19. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Hole19 signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.
A Allow "your app"
On-device and permissioned
Hole19 data is read on the user’s own device, only after they grant Apple Health permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health — Hole19 today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Hole19 syncs through Apple Health.
Request only what you need
You choose exactly which of these signals to request from Apple Health — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Hole19, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
The round as a workout, and its active energy pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- workoutActivityTypeexercise_session_*min
- activeEnergyBurnedactive_energy_burnedkcal
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeGolf",
"duration": 13080,
"totalEnergyBurned": { "value": 842, "unit": "kcal" },
"startDate": "2026-05-24T08:10:00Z",
"endDate": "2026-05-24T11:48:00Z",
"sourceRevision": { "source": { "name": "Hole19" } }
}[
{
"category": "activity",
"type": "exercise_session_golf",
"value": 218,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-05-24T08:10:00Z",
"endDateTime": "2026-05-24T11:48:00Z"
},
{
"category": "activity",
"type": "active_energy_burned",
"value": 842,
"unit": "kcal",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-05-24T08:10:00Z",
"endDateTime": "2026-05-24T11:48:00Z"
}
]Hole19 writes two things and only two: the round as a workout, and the active energy burned during it. Scores, shot data, and course statistics stay inside Hole19 — Apple Health has no place to put them, so they never reach Sahha. This is an Apple Health integration, so the page is scoped to iOS.
Missing a metric you need? Talk to us in the Sahha Slack — if Hole19 captures it, we can usually add support.
Get more than just raw data
Sahha turns these signals into biomarkers, scores, archetypes, and insights — the modeling done for you.
Reading Apple Health yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain on iOS. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Handle iOS version differences.
- Add Health Connect separately for Android.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Request the right permissions.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of HealthKit types.
- Reconcile against your Android sources.
Deduped, typed, one schema — one stream per user.
- Build a sleep model.
- Build an activity model.
- Hire a data scientist.
Scores, archetypes, and insights — built in.
- Apple changes a HealthKit API.
- You find out in production.
We version the SDK. You never notice.
No Hole19 developer account needed — Sahha reads what Hole19 already writes to Apple Health on iOS.
Live in an afternoon, not a sprint.
- # Add the Sahha SDKnpm install sahha-react-native01
Add the Sahha SDK
Drop the Sahha SDK into your iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for Apple Health permissions
Call the SDK to show the native Apple Health consent sheet. The user chooses what to share — under your brand. It’s one prompt, ever: permission is per data type, not per brand, so every future source is already covered.
- Your app LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads Hole19 data from Apple Health in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live Hole19 data the same day they add the SDK. The only per-source prerequisite: your user has Hole19’s Apple Health sync switched on — most source apps enable it by default.
Route it into your stack.
Sahha streams every update to your webhook — and a step-by-step guide takes it the rest of the way into your database, CDP, or messaging tool.
Hole19 integration questions
How does Sahha get Hole19 data?
Hole19 writes each tracked round to Apple Health, and Sahha reads it from there with its mobile SDK, delivering it as a normalized exercise session — no Hole19 API to integrate.
What Hole19 data does Sahha receive?
The round as a workout — activity type and duration — and the active energy burned during it. Hole19’s own instructions name exactly these two write permissions, and they’re what the page claims.
Do scores and shot data come through?
No. Scorecards, shot tracking, and course statistics stay in Hole19 — Apple Health carries workouts and energy, not golf-specific records. What you get is the round as an activity signal: when it happened, how long it lasted, and what it cost the player.
Does the Hole19 integration work on Android?
This page covers the Apple Health write path only, so it’s scoped to iOS. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Hole19 integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Hole19 data flows through the same compliant pipeline as every other source.
One API for every other source, too.
Add another wearable or app and the schema, webhooks, and scores are identical — no new pipeline to build.
Start streaming Hole19 data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Hole19 and every other source.
Free for 30 days · No credit card
- One API for Hole19 and every other source
- Real-time webhooks + on-demand REST, one normalized schema
- Scores, archetypes & insights — no modeling required
- HIPAA, GDPR & SOC 2 · your brand on the consent screen