Stream Speediance data. No Speediance API needed.
Speediance builds the Gym Monster line of digital-resistance home gyms, and its app syncs each completed workout to Apple Health and Google Health Connect — where Sahha’s SDK reads it into your app as a normalized exercise session, alongside every other source.
- On-device
- Apple Health + Health Connect
- HIPAA
- GDPR
- SOC 2
Free for 30 days · No credit card
- Strength session
- 42 min
- Active energy
- 318 kcal
Identical schema across 500+ sources
Your users connect Speediance. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Speediance 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
Speediance data is read on the user’s own device, only after they grant Apple Health or Health Connect permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health or Health Connect — Speediance today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Speediance syncs through Apple Health & Health Connect.
Request only what you need
You choose exactly which of these signals to request from Apple Health / Health Connect — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Speediance, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Completed strength sessions and active energy pass through the platform; some device-exclusive metrics may not.
Activity & exercise
2
HealthKit / Health ConnectSahha- workoutActivityTypeexercise_session_*min
- totalEnergyBurnedactive_energy_burnedkcal
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeTraditionalStrengthTraining",
"duration": "2520 s",
"totalEnergyBurned": "318 kcal",
"startDate": "2026-06-03T18:04:00Z",
"endDate": "2026-06-03T18:46:00Z",
"sourceRevision": { "source": { "name": "Speediance" } }
}[
{
"category": "activity",
"type": "exercise_session_strength_training",
"value": 42,
"unit": "minute",
"startDateTime": "2026-06-03T18:04:00Z",
"endDateTime": "2026-06-03T18:46:00Z"
},
{
"category": "activity",
"type": "active_energy_burned",
"value": 318,
"unit": "kcal",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-03T18:04:00Z",
"endDateTime": "2026-06-03T18:46:00Z"
}
]Speediance writes the completed workout record — the strength-training session and the energy burned — to Apple Health and Google Health Connect. That’s the envelope, not the detail: per-rep and per-set breakdowns and the machine load stay in the Speediance app and don’t cross to either platform.
Missing a metric you need? Talk to us in the Sahha Slack — if Speediance 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 and Health Connect yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain across two platforms. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Then Health Connect, separately.
- Then reconcile the two.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Write the Health Connect queries.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of platform types.
- Normalize iOS against Android.
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 or Google changes an API.
- You find out in production.
We version the SDK. You never notice.
No Speediance developer account needed — Sahha reads what Speediance already writes to Apple Health and Health Connect.
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 or Android app — or React Native or Flutter. One dependency covers both Apple Health and Health Connect.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for health permissions
Call the SDK to show the native Apple Health or Health Connect 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 Speediance data from Apple Health / Health Connect in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live Speediance data the same day they add the SDK. The only per-source prerequisite: your user has Speediance’s Apple Health / Health Connect 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.
Speediance integration questions
How does Sahha get Speediance data?
The Speediance app syncs each completed workout record to Apple Health and Google Health Connect, and Sahha reads it from there with its mobile SDK — no Speediance API to integrate.
What Speediance data does Sahha receive?
The completed strength-training session — its duration — and the active energy burned. Both arrive as normalized data logs in the same schema you get from every other source.
Do I get per-rep or per-set detail from Speediance?
No. Speediance writes the completed workout record, so reps, sets, and the resistance the machine applied stay in the Speediance app. If you need training volume at that granularity, it isn’t available through the platform write path.
Does the Speediance integration work on both iOS and Android?
Yes. Speediance supports syncing workout records to both Apple Health and Google Health Connect, so the same session data reaches Sahha on either platform. Your users’ other Apple Health and Health Connect sources still flow through the same Sahha SDK.
Is the Speediance integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Speediance 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 Speediance data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Speediance and every other source.
Free for 30 days · No credit card
- One API for Speediance 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