Stream Fitbit data. No Fitbit API needed.
Fitbit and the Google Health app write steps, sleep, weight, heart rate, and workouts to Health Connect on Android — and Sahha’s SDK reads them into your app as normalized biomarkers and scores, alongside every other source.
- On-device
- Health Connect
- Android
- HIPAA
- GDPR
Free for 30 days · No credit card
- Sleep duration
- 7:18 h
- Resting heart rate
- 59 bpm
- Steps
- 9,640
Identical schema across 500+ sources
Your users connect Google Health. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Google Health 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
Google Health data is read on the user’s own device, only after they grant Health Connect permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Health Connect — Google Health today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Fitbit syncs through Health Connect.
Works with
Charge 6Sense 2Versa 4Inspire 3LuxeAce LTEPixel WatchRequest only what you need
You choose exactly which of these signals to request from Health Connect — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Fitbit, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Sleep, steps, heart rate, weight, and workouts pass through Health Connect; some app-exclusive metrics may not.
Sleep
4
Health ConnectSahha- SleepSessionRecord · DEEPsleep_stage_deepmin
- SleepSessionRecord · LIGHTsleep_stage_lightmin
- SleepSessionRecord · REMsleep_stage_remmin
- SleepSessionRecord · AWAKEsleep_stage_awakemin
Heart
2
Health ConnectSahha- HeartRateRecordheart_ratebpm
- RestingHeartRateRecordresting_heart_ratebpm
Activity & exercise
3
Health ConnectSahha- StepsRecordstepscount
- ActiveCaloriesBurnedRecordactive_energy_burnedkcal
- DistanceRecorddistance_walkingm
Body
1
Health ConnectSahha- WeightRecordweightkg
See a real payload
{
"record": "SleepSessionRecord",
"stage": "STAGE_TYPE_DEEP",
"startTime": "2026-06-02T23:18:00Z",
"endTime": "2026-06-03T00:36:00Z",
"metadata": { "dataOrigin": "com.google.android.apps.healthdata" }
// …heart rate, steps & weight records
}[
{
"category": "sleep",
"type": "sleep_stage_deep",
"value": 81,
"unit": "minute",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T23:18:00Z",
"endDateTime": "2026-06-03T06:44:00Z"
},
{
"category": "activity",
"type": "steps",
"value": 9640,
"unit": "count",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
}
// …3 more normalized logs
]Fitbit writes to Health Connect on Android only — it does not write to Apple Health. Sahha reads sleep, steps, heart rate, weight, and workouts from Health Connect; on iOS, cover the same users through Apple Watch or another Apple Health source.
Missing a metric you need? Talk to us in the Sahha Slack — if Google Health 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 Health Connect yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain on Android. Everything on the right, Sahha already did.
- Integrate Health Connect.
- Handle Android version differences.
- Add Apple Health separately for iOS.
One SDK covers Health Connect, Apple Health, and every cloud source.
- Write the Health Connect 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 Health Connect record types.
- Reconcile against your iOS 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.
- Google changes a Health Connect API.
- You find out in production.
We version the SDK. You never notice.
No Fitbit developer account needed — Sahha reads what Fitbit already writes to Health Connect on Android.
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 Android app — or React Native or Flutter. The same SDK also covers Apple Health for your iOS sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for Health Connect permissions
Call the SDK to show the native 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 Fitbit data from Health Connect in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live Fitbit data the same day they add the SDK. The only per-source prerequisite: your user has Fitbit’s 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.
Fitbit & Google Health integration questions
How does Sahha get Fitbit data?
The Fitbit and Google Health apps write steps, sleep, heart rate, weight, and workouts to Health Connect on Android, and Sahha reads them from there with its mobile SDK — no Fitbit API to integrate.
Does Fitbit sync to Apple Health?
No. Fitbit writes to Health Connect on Android only — it does not natively write to Apple Health. Sahha reads Fitbit through Health Connect; for the same users on iOS, cover them through Apple Watch or another Apple Health source.
Is this Fitbit or Google Health?
Both — Google now runs the Fitbit ecosystem under Google Health, and either app writes the same data to Health Connect. Sahha reads whatever the app writes, so the integration works whether the user is on the Fitbit or Google Health app.
Do I need a mobile app to use the Fitbit integration?
Yes. Because Fitbit data lands in Health Connect on the user’s Android device, you embed the Sahha mobile SDK to read it. Cloud-only sources like Oura don’t need the SDK, but on-device sources like Fitbit do.
Is the Fitbit integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Fitbit 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 Google Health data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Google Health and every other source.
Free for 30 days · No credit card
- One API for Google Health 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