Stream Life Fitness data. Straight from the phone.
Life Fitness makes commercial and home gym equipment, and its companion app pairs with treadmills, bikes, and ellipticals — its own permission copy reads “Allow Life Fitness to Write Data”. Sahha’s SDK reads those workouts into your app as normalized exercise sessions, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Treadmill session
- 38 min
- Distance
- 5.6 km
- Active energy
- 404 kcal
Identical schema across 500+ sources
Your users connect Life Fitness. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Life Fitness 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
Life Fitness 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 — Life Fitness today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Life Fitness 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
Life Fitness, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Workouts, active energy, distance, and heart rate pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
3
HealthKitSahha- workoutActivityTypeexercise_session_*min
- activeEnergyBurnedactive_energy_burnedkcal
- distanceWalkingRunningdistance_walkingkm
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeRunning",
"duration": 2280,
"totalEnergyBurned": { "value": 404, "unit": "kcal" },
"totalDistance": { "value": 5.6, "unit": "km" },
"sourceRevision": { "source": { "name": "Life Fitness" } }
}[
{
"category": "activity",
"type": "exercise_session_running",
"value": 38,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T07:10:00Z",
"endDateTime": "2026-06-02T07:48:00Z"
},
{
"category": "activity",
"type": "distance_walking",
"value": 5.6,
"unit": "km",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T07:10:00Z",
"endDateTime": "2026-06-02T07:48:00Z"
}
]The write covers workouts logged through the Life Fitness app on paired equipment — a session the user didn’t log in the app won’t appear. Machine-specific metrics such as incline, resistance, and watts stay in the app; there are no Apple Health fields for them. This is an Apple-Health-only integration.
Missing a metric you need? Talk to us in the Sahha Slack — if Life Fitness 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 Life Fitness developer account needed — Sahha reads what Life Fitness 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 Life Fitness 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 Life Fitness data the same day they add the SDK. The only per-source prerequisite: your user has Life Fitness’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.
Life Fitness integration questions
How does Sahha get Life Fitness data?
The Life Fitness app writes workouts to Apple Health — its own permission prompt reads “Allow Life Fitness to Write Data” — and Sahha reads them from there with its mobile SDK, so you get equipment workouts without integrating a Life Fitness API directly.
What Life Fitness data does Sahha receive?
The workout duration, active energy, distance, and heart rate. They arrive as normalized exercise sessions and vitals, in the same fields and units as every other source.
Does Sahha get incline, resistance, or watts?
No. Machine-specific metrics — incline, resistance, watts — stay in the Life Fitness app, because Apple Health has no field for them. And the write only covers workouts logged through the app on paired equipment, so a session the user did not log won’t cross.
Does the Life Fitness integration work on Android?
No. The write path we can confirm is Apple Health, so this is an iOS-only integration and the page doesn’t claim otherwise. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Life Fitness integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Life Fitness 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 Life Fitness data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Life Fitness and every other source.
Free for 30 days · No credit card
- One API for Life Fitness 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