Stream Tanita data. No Tanita API needed.
Tanita’s MyTANITA app writes each body-composition measurement — weight, BMI, body fat, muscle mass, which arrives as lean mass, and the scale’s BMR estimate, which arrives as basal energy burned — from a Bluetooth-connected Tanita scale to Apple Health, and Sahha’s SDK reads it 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
- Weight
- 72.4 kg
- Body fat
- 18.6 %
- Lean mass
- 58.9 kg
- Basal energy
- 1,540 kcal
Identical schema across 500+ sources
Your users connect Tanita. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Tanita 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
Tanita 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 — Tanita today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Tanita 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
Tanita, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Weight, BMI, body fat, muscle mass as lean mass, and BMR as basal energy burned pass through Apple Health; some app-exclusive metrics may not.
Body
5
HealthKitSahha- bodyMassweightkg
- bodyMassIndexbody_mass_index
- bodyFatPercentagebody_fat%
- leanBodyMasslean_masskg
- basalEnergyBurnedbasal_energy_burnedkcal
See a real payload
{
"type": "HKQuantityTypeIdentifierBodyMass",
"value": 72.4,
"unit": "kg",
"startDate": "2026-06-03T06:40:00Z",
"sourceRevision": { "source": { "name": "MyTANITA" } }
// …BMI, body fat, lean mass & basal energy samples
} [
{
"category": "body",
"type": "weight",
"value": 72.4,
"unit": "kilogram",
"periodicity": "manual",
"aggregation": "none",
"startDateTime": "2026-06-03T06:40:00Z",
"endDateTime": "2026-06-03T06:40:00Z"
}
// …4 more normalized logs
] Scope this to MyTANITA — Tanita ships two apps, and MyTANITA is the Apple Health writer. (Health Planet is the older, separate app with only a thin Health link; don’t plan around it.) MyTANITA needs a Bluetooth-connected Tanita scale to produce readings at all, so data arrives when the user steps on the scale, not on a schedule. The scale’s BMR estimate does cross, as basal energy burned — Apple Health’s resting-energy field. Tanita’s segmental readings — muscle mass broken out per limb — stay in MyTANITA; only the whole-body figure crosses, and it arrives as lean mass.
Missing a metric you need? Talk to us in the Sahha Slack — if Tanita 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 Tanita developer account needed — Sahha reads what Tanita 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.
- 02
Prompt 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 Tanita 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 Tanita data the same day they add the SDK. The only per-source prerequisite: your user has Tanita’s Apple Health sync switched on — most source apps enable it by default.
Tanita integration questions
How does Sahha get Tanita data?
The MyTANITA app writes each measurement to Apple Health, and Sahha reads it from there with its mobile SDK — no Tanita API to integrate.
Which Tanita app does this integration use?
MyTANITA. Tanita ships two apps and they are not interchangeable: MyTANITA is the one that writes body-composition measurements to Apple Health, while Health Planet is an older, separate app with only a thin Health link. Tell your users to pair their scale with MyTANITA.
What Tanita data does Sahha receive?
Weight, BMI, body fat percentage, muscle mass, which arrives as lean mass, and the scale’s BMR estimate, which arrives as basal energy burned — Apple Health’s resting-energy field. Tanita’s segmental readings, muscle mass broken out per limb, stay in MyTANITA; only the whole-body figure crosses. A reading only exists when the user steps on a Bluetooth-connected Tanita scale, so cadence follows their weigh-ins.
Does the Tanita integration work on Android?
Not today. MyTANITA’s verified write path is Apple Health, so this is an iOS-only integration and the page claims nothing more. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Tanita integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Tanita 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 Tanita data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Tanita and every other source.
Free for 30 days · No credit card
- One API for Tanita 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



