Stream One Drop data. No One Drop API needed.
One Drop writes blood glucose to Apple Health — and Sahha’s SDK reads it into your app as a normalized glucose biomarker, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Glucose
- 116 mg/dL
- Daily average
- 122 mg/dL
Identical schema across 500+ sources
Your users connect One Drop. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every One Drop 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
One Drop 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 — One Drop today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What One Drop 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
One Drop, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Blood glucose pass through Apple Health; some app-exclusive metrics may not.
Glucose
1
HealthKitSahha- bloodGlucoseblood_glucosemg/dL
See a real payload
{
"type": "HKQuantityTypeIdentifierBloodGlucose",
"value": 116,
"unit": "mg/dL",
"startDate": "2026-06-03T09:05:00Z",
"sourceRevision": { "source": { "name": "One Drop" } }
}[
{
"category": "vitals",
"type": "blood_glucose",
"value": 116,
"unit": "mg/dL",
"periodicity": "session",
"aggregation": "none",
"startDateTime": "2026-06-03T09:05:00Z",
"endDateTime": "2026-06-03T09:05:00Z"
}
]One Drop writes glucose entries to Apple Health when the user enables its Apple Health sync. It’s an iOS integration, so its data lands in Apple Health, not Health Connect.
Missing a metric you need? Talk to us in the Sahha Slack — if One Drop 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 One Drop developer account needed — Sahha reads what One Drop 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 One Drop 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 One Drop data the same day they add the SDK. The only per-source prerequisite: your user has One Drop’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.
One Drop integration questions
How does Sahha get One Drop data?
One Drop writes blood glucose to Apple Health, and Sahha reads it from there with its mobile SDK — no One Drop API to integrate.
Which One Drop metrics does Sahha provide?
Blood glucose, normalized into Sahha’s schema. The user enables One Drop’s Apple Health sync, and Sahha reads the glucose readings it writes from that point on.
Does the One Drop integration work on Android?
One Drop writes to Apple Health on iOS, which is where Sahha reads it. The same Sahha SDK also reads Health Connect on Android for your other sources, all normalized to one schema.
Is the One Drop integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and One Drop 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 One Drop data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for One Drop and every other source.
Free for 30 days · No credit card
- One API for One Drop 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