Stream Wearfit Pro data. Straight from the phone.
Wearfit Pro — also shipped as WearPro — is a white-label companion app from a Shenzhen ODM that dozens of budget wearable brands ship instead of building an app, and it writes steps, active energy, workouts, heart rate, and sleep duration to Apple Health, where Sahha’s SDK reads them into your app as normalized data logs.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Steps
- 7,860 count
- Heart rate
- 68 bpm
- Sleep duration
- 408 min
Identical schema across 500+ sources
Your users connect Wearfit Pro. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Wearfit Pro 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
Wearfit Pro 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 — Wearfit Pro today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Wearfit Pro 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
Wearfit Pro, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Steps, active energy, workouts, heart rate, and total sleep pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
3
HealthKitSahha- HKQuantityTypeIdentifierStepCountstepscount
- HKQuantityTypeIdentifierActiveEnergyBurnedactive_energy_burnedkcal
- workoutActivityTypeexercise_session_*min
Heart & vitals
1
HealthKitSahha- HKQuantityTypeIdentifierHeartRateheart_ratebpm
Sleep
1
HealthKitSahha- HKCategoryTypeIdentifierSleepAnalysissleep_durationmin
See a real payload
{
"type": "HKQuantityTypeIdentifierHeartRate",
"value": 68,
"unit": "count/min",
"startDate": "2026-06-03T08:14:00Z",
"endDate": "2026-06-03T08:14:00Z",
"sourceRevision": { "source": { "name": "Wearfit Pro" } }
// …steps, active energy, workout & sleep samples
}[
{
"category": "vitals",
"type": "heart_rate",
"value": 68,
"unit": "bpm",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
},
{
"category": "activity",
"type": "steps",
"value": 7860,
"unit": "count",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
}
// …3 more normalized logs
]Three caveats worth knowing. Brand attribution is muddy: the data arrives under the Wearfit Pro source name, not the device maker’s, so you can tell a user has a band — not necessarily which band. Feature coverage varies by model, so two devices on the same app can write different things. And apps in this family report a blood-pressure figure derived from optical estimation — that measurement is of dubious validity, so Sahha deliberately doesn’t ingest it or surface Wearfit Pro as a blood-pressure source. 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 Wearfit Pro 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 Wearfit Pro developer account needed — Sahha reads what Wearfit Pro 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 Wearfit Pro 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 Wearfit Pro data the same day they add the SDK. The only per-source prerequisite: your user has Wearfit Pro’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.
Wearfit Pro integration questions
How does Sahha get Wearfit Pro data?
Wearfit Pro writes its paired band’s data to Apple Health, and Sahha reads it from there with its mobile SDK, delivering normalized data logs — no Wearfit Pro API to integrate, and no per-device work.
Why does a Wearfit Pro integration matter?
Wearfit Pro — also shipped as WearPro — is a white-label companion app from a Shenzhen ODM, and one of the two highest-reach apps of its kind. Dozens of budget wearable brands across India, Southeast Asia, Latin America, the Middle East and Eastern Europe ship no app of their own and hand users this one instead. A single integration therefore covers a long tail of no-name devices that would otherwise be invisible in your data.
Does Sahha read blood pressure from Wearfit Pro?
No, and that’s deliberate. Apps in this family report a blood-pressure figure derived from optical estimation at the wrist, which isn’t a validated way to measure blood pressure. We don’t ingest it and we don’t list Wearfit Pro as a blood-pressure source. If you need blood pressure, it should come from a cuff-based device.
Does the Wearfit Pro integration work on Android?
No. Health Connect is nearly absent from this category — Wearfit Pro’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 Wearfit Pro integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Wearfit Pro 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 Wearfit Pro data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Wearfit Pro and every other source.
Free for 30 days · No credit card
- One API for Wearfit Pro 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