Stream Zeblaze data. Straight from the phone.
Zeblaze is a budget smartwatch brand whose companion app writes to Apple Health — steps, active energy, heart rate, and sleep duration — and Sahha’s SDK reads them into your app as normalized data logs, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Steps
- 8,120 count
- Heart rate
- 71 bpm
- Sleep duration
- 415 min
Identical schema across 500+ sources
Your users connect Zeblaze. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Zeblaze 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
Zeblaze 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 — Zeblaze today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Zeblaze 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
Zeblaze, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Steps, active energy, heart rate, and total sleep pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- HKQuantityTypeIdentifierStepCountstepscount
- HKQuantityTypeIdentifierActiveEnergyBurnedactive_energy_burnedkcal
Heart & vitals
1
HealthKitSahha- HKQuantityTypeIdentifierHeartRateheart_ratebpm
Sleep
1
HealthKitSahha- HKCategoryTypeIdentifierSleepAnalysissleep_durationmin
See a real payload
{
"type": "HKQuantityTypeIdentifierStepCount",
"value": 8120,
"unit": "count",
"startDate": "2026-06-03T00:00:00Z",
"endDate": "2026-06-03T23:59:59Z",
"sourceRevision": { "source": { "name": "Zeblaze" } }
// …active energy, heart-rate & sleep samples
}[
{
"category": "activity",
"type": "steps",
"value": 8120,
"unit": "count",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
},
{
"category": "vitals",
"type": "heart_rate",
"value": 71,
"unit": "bpm",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
}
// …2 more normalized logs
]Zeblaze’s own wording is that it writes “some data” to the Health app — so coverage is model-dependent, and two watches paired to the same app can write different things. Brand attribution is muddy in this category too: data arrives under the companion app’s name rather than the device model’s, so you can tell a user has a Zeblaze watch, not which one. Total sleep duration crosses; sleep stages don’t. There’s no Health Connect path — the Android side is Google Fit or nothing — so this is an iOS-only integration.
Missing a metric you need? Talk to us in the Sahha Slack — if Zeblaze 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 Zeblaze developer account needed — Sahha reads what Zeblaze 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 Zeblaze 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 Zeblaze data the same day they add the SDK. The only per-source prerequisite: your user has Zeblaze’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.
Zeblaze integration questions
How does Sahha get Zeblaze data?
Zeblaze’s companion app writes its watch data to Apple Health, and Sahha reads it from there with its mobile SDK, delivering normalized data logs — no Zeblaze API to integrate, and no per-device work.
Why does a Zeblaze integration matter?
Zeblaze is smaller than the big white-label companion apps — roughly 100k installs — but it carries the cleanest evidence of the batch: the listing states the app integrates HealthKit to read and write data in the Health app. It’s part of the same long tail of budget wearables sold across India, Southeast Asia, Latin America, the Middle East and Eastern Europe that would otherwise be invisible in your data.
What Zeblaze data does Sahha receive?
Steps, active energy, heart rate, and total sleep duration. Be aware that the vendor’s own wording is “some data”, so coverage is model-dependent — two watches using the same app can write different things. Sleep stages don’t cross, only total duration. And because the data arrives under the app’s name, you can tell a user has a Zeblaze watch without knowing which model.
Does the Zeblaze integration work on Android?
No. Health Connect is nearly absent from this category — Zeblaze’s Android path is Google Fit or nothing — so there’s no Android write path we’ll claim today. This is an iOS-only integration. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Zeblaze integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Zeblaze 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 Zeblaze data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Zeblaze and every other source.
Free for 30 days · No credit card
- One API for Zeblaze 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