Stream Juggluco data. Straight from the phone.
Juggluco is an Android app that reads Libre and Dexcom sensors directly and can send data to Health Connect — where Sahha’s SDK reads blood glucose 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
- 6.1 mmol/L
- Source
- CGM sensor
Identical schema across 500+ sources
Your users connect Juggluco. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Juggluco 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
Juggluco 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 — Juggluco today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Juggluco 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
Juggluco, 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": 6.1 },
"time": "2026-06-03T09:20:00Z",
"metadata": { "dataOrigin": "tk.glucodata" }
}[
{
"category": "vitals",
"type": "blood_glucose",
"value": 6.1,
"unit": "mmol/L",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T09:20:00Z",
"endDateTime": "2026-06-03T09:20:00Z"
}
]Blood glucose is the only thing that crosses — that’s the one Health Connect record Juggluco writes. It’s an Android app, so this is a Health-Connect-only integration; it ships on the Google Play Store as well as GitHub, which makes onboarding simpler than a side-loaded alternative. One thing to expect: Juggluco reads the sensor directly, so if the user also runs another CGM app you may see the same glucose arrive from two sources — Sahha deduplicates.
Missing a metric you need? Talk to us in the Sahha Slack — if Juggluco 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 Juggluco developer account needed — Sahha reads what Juggluco 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 Juggluco 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 Juggluco data the same day they add the SDK. The only per-source prerequisite: your user has Juggluco’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.
Juggluco integration questions
How does Sahha get Juggluco data?
Juggluco reads the Libre or Dexcom sensor directly and inserts a blood glucose record into Health Connect, and Sahha reads it from there with its mobile SDK — no Juggluco API to integrate.
What Juggluco data does Sahha receive?
Blood glucose, and nothing else. That’s the single Health Connect record Juggluco writes, and it arrives normalized in mmol/L alongside every other vitals log.
Where do users get Juggluco?
It’s on the Google Play Store as tk.glucodata, and also available from GitHub. Either way, the user enables the Health Connect send from inside Juggluco.
Does the Juggluco integration work on iOS?
No. Juggluco is an Android app writing to Health Connect, so this is an Android-only integration. Because it reads the sensor directly, a user also running another CGM 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 Juggluco integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Juggluco 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 Juggluco data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Juggluco and every other source.
Free for 30 days · No credit card
- One API for Juggluco 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