Stream Oxiline data. No Oxiline API needed.
Oxiline makes connected health devices including the Scale X Pro, and its app syncs with Apple Health and Android Health Connect — where Sahha’s SDK reads weight and body composition into your app as normalized biomarkers, alongside every other source.
- On-device
- Apple Health + Health Connect
- HIPAA
- GDPR
- SOC 2
Free for 30 days · No credit card
- Weight
- 74.6 kg
- Body fat
- 19.4 %
- Lean mass
- 60.1 kg
Identical schema across 500+ sources
Your users connect Oxiline. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Oxiline 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
Oxiline 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 — Oxiline today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Oxiline 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
Oxiline, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Weight, body fat, lean mass, and BMI pass through the platform; some device-exclusive metrics may not.
Body
4
HealthKit / Health ConnectSahha- bodyMassweightkg
- bodyFatPercentagebody_fat%
- leanBodyMasslean_masskg
- bodyMassIndexbody_mass_index
See a real payload
{
"type": "HKQuantityTypeIdentifierBodyMass",
"value": 74.6,
"unit": "kg",
"startDate": "2026-06-03T07:12:00Z",
"sourceRevision": { "source": { "name": "Oxiline" } }
// …body fat, lean mass & BMI samples
}[
{
"category": "body",
"type": "weight",
"value": 74.6,
"unit": "kilogram",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T07:12:00Z",
"endDateTime": "2026-06-03T07:12:00Z"
},
{
"category": "body",
"type": "body_fat",
"value": 19.4,
"unit": "percent",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T07:12:00Z",
"endDateTime": "2026-06-03T07:12:00Z"
}
// …lean mass & BMI logs
]Oxiline sells a range of connected health devices, so what you actually receive depends on which one the user owns. The confirmed writer is the smart scale — the Scale X Pro — which sends weight, body fat, lean mass, and BMI to Apple Health and Android Health Connect. Sahha reads whatever the platform holds; it can’t surface a metric a user’s device never measured.
Missing a metric you need? Talk to us in the Sahha Slack — if Oxiline 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 Oxiline developer account needed — Sahha reads what Oxiline 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 Oxiline 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 Oxiline data the same day they add the SDK. The only per-source prerequisite: your user has Oxiline’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.
Oxiline integration questions
How does Sahha get Oxiline data?
The Oxiline app syncs with Apple Health and Android Health Connect, and Sahha reads the readings from there with its mobile SDK — no Oxiline API to integrate.
What Oxiline data does Sahha receive?
From the smart scale: weight, body fat, lean mass, and BMI, normalized into Sahha’s schema with the same field names and units as every other body-composition source.
Does coverage depend on which Oxiline device I own?
Yes. Oxiline makes several connected health devices, and the scale is the confirmed writer here. A user with a different Oxiline device will produce a different — possibly narrower — set of readings, and Sahha can only read what reaches the platform.
Does the Oxiline integration work on both iOS and Android?
Yes. Oxiline syncs with both Apple Health and Android Health Connect, so the same readings reach Sahha on either platform. Your users’ other Apple Health and Health Connect sources still flow through the same Sahha SDK.
Is the Oxiline integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Oxiline 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 Oxiline data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Oxiline and every other source.
Free for 30 days · No credit card
- One API for Oxiline 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