Stream xDrip+ data. Straight from the phone.
xDrip+ is an open-source Android companion app for continuous glucose monitors — it reads Dexcom and Libre sensors and writes blood glucose to Health Connect, where Sahha’s SDK reads it into your app as a normalized biomarker, alongside every other source.
- On-device
- Health Connect
- Android
- HIPAA
- GDPR
Free for 30 days · No credit card
- Blood glucose
- 5.8 mmol/L
- Source
- CGM sensor
Identical schema across 500+ sources
Your users connect xDrip+. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every xDrip+ 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
xDrip+ 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 — xDrip+ today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What xDrip+ syncs through Health Connect.
Request 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
xDrip+, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Blood glucose readings pass through Health Connect; some app-exclusive metrics may not.
Heart & vitals
1
Health ConnectSahha- BloodGlucoseRecordblood_glucosemmol/L
See a real payload
{
"record": "BloodGlucoseRecord",
"level": { "millimolesPerLiter": 5.8 },
"time": "2026-06-03T09:15:00Z",
"metadata": { "dataOrigin": "com.eveningoutpost.dexdrip" }
}[
{
"category": "vitals",
"type": "blood_glucose",
"value": 5.8,
"unit": "mmol/L",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T09:15:00Z",
"endDateTime": "2026-06-03T09:15:00Z"
}
]Blood glucose is the only thing that crosses — that’s the one Health Connect record xDrip+ writes. Two practical caveats: xDrip+ is distributed as an APK on GitHub rather than through the Google Play Store, so users install it manually, and it’s Android-only. It also re-broadcasts readings that originate from a CGM sensor, so if the user also runs the sensor’s own app you may see the same glucose arrive from two sources — Sahha deduplicates, but it’s worth knowing why the duplicate exists.
Missing a metric you need? Talk to us in the Sahha Slack — if xDrip+ 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 xDrip+ developer account needed — Sahha reads what xDrip+ 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 xDrip+ 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 xDrip+ data the same day they add the SDK. The only per-source prerequisite: your user has xDrip+’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.
xDrip+ integration questions
How does Sahha get xDrip+ data?
xDrip+ inserts a blood glucose record into Health Connect for each reading it receives from the sensor, and Sahha reads it from there with its mobile SDK — no xDrip+ API to integrate.
What xDrip+ data does Sahha receive?
Blood glucose, and nothing else. That’s the single Health Connect record xDrip+ writes, and it arrives normalized in mmol/L alongside every other vitals log.
How do users install xDrip+?
Manually. xDrip+ is an open-source project distributed as an APK on GitHub — it isn’t on the Google Play Store, so users side-load it rather than installing it the usual way. Plan onboarding copy accordingly.
Does the xDrip+ integration work on iOS?
No. xDrip+ is an Android app writing to Health Connect, so this is an Android-only integration. Note too that xDrip+ re-broadcasts readings that originate from a CGM sensor, so a user also running the sensor’s own app can produce the same glucose from two sources — Sahha deduplicates. Your users’ other Apple Health sources still flow through the same Sahha SDK.
Is the xDrip+ integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and xDrip+ 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 xDrip+ data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for xDrip+ and every other source.
Free for 30 days · No credit card
- One API for xDrip+ 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