Stream FitTrace DEXA results. No FitTrace API needed.
FitTrace lets users “upload your DEXA data to Apple Health” — weight, body fat percentage, lean mass, and BMI from a scan — and Sahha’s SDK reads them into your app as normalized body biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Body fat
- 16.2 %
- Lean mass
- 58.9 kg
- Weight
- 71.5 kg
Identical schema across 500+ sources
Your users connect FitTrace. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every FitTrace 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
FitTrace 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 — FitTrace today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What FitTrace 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
FitTrace, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
DEXA weight, body fat percentage, lean mass, and BMI pass through Apple Health; some app-exclusive metrics may not.
Body
4
HealthKitSahha- bodyMassweightkg
- bodyFatPercentagebody_fat%
- leanBodyMasslean_masskg
- bodyMassIndexbody_mass_index
See a real payload
{
"type": "HKQuantityTypeIdentifierBodyFatPercentage",
"value": 0.162,
"unit": "%",
"startDate": "2026-06-03T11:00:00Z",
"sourceRevision": { "source": { "name": "FitTrace" } }
// …weight, lean mass & BMI samples
}[
{
"category": "body",
"type": "body_fat",
"value": 16.2,
"unit": "percent",
"periodicity": "manual",
"aggregation": "none",
"startDateTime": "2026-06-03T11:00:00Z",
"endDateTime": "2026-06-03T11:00:00Z"
}
// …3 more normalized logs
]Worth understanding before you plan around it: FitTrace writes scan results, not device readings. DEXA is the clinical reference standard for body composition, so these four values arrive at far higher accuracy than a bioimpedance scale — but only as often as the user gets scanned, which is typically every few months rather than daily. Treat them as accurate anchor points between which nothing arrives. iOS only.
Missing a metric you need? Talk to us in the Sahha Slack — if FitTrace 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 FitTrace developer account needed — Sahha reads what FitTrace 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 FitTrace 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 FitTrace data the same day they add the SDK. The only per-source prerequisite: your user has FitTrace’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.
FitTrace integration questions
How does Sahha get FitTrace data?
The user uploads their DEXA results to FitTrace, FitTrace writes them to Apple Health, and Sahha reads them from there with its mobile SDK — no FitTrace API to integrate.
What FitTrace data does Sahha receive?
Four DEXA variables: weight, body fat percentage, lean mass, and BMI. They land in the same body fields and units as every other source, so a DEXA reading and a smart-scale reading sit in one schema.
How often does FitTrace data arrive?
As often as the user gets scanned — typically every few months, not daily. This is a scan-result writer rather than a wearable, so expect accurate, infrequent anchor points rather than a stream. The upside is accuracy: DEXA is the clinical reference standard for body composition, well above what a bioimpedance scale produces.
Does the FitTrace integration work on Android?
No. FitTrace is iOS only and its write path is Apple Health, so this is an iOS-only integration. Your users’ other Android sources still flow through the same Sahha SDK.
Is the FitTrace integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and FitTrace 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 FitTrace data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for FitTrace and every other source.
Free for 30 days · No credit card
- One API for FitTrace 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