Stream VeryFitPro data. Straight from the phone.
VeryFitPro is the white-label companion app behind ID115- and Letsfit-class budget bands — roughly 19 million downloads’ worth of hardware that ships no app of its own — and it writes steps, active energy, 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
- 6,480 count
- Active energy
- 287 kcal
- Sleep duration
- 397 min
Identical schema across 500+ sources
Your users connect VeryFitPro. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every VeryFitPro 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
VeryFitPro 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 — VeryFitPro today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What VeryFitPro 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
VeryFitPro, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Steps, active energy, and total sleep pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- HKQuantityTypeIdentifierStepCountstepscount
- HKQuantityTypeIdentifierActiveEnergyBurnedactive_energy_burnedkcal
Sleep
1
HealthKitSahha- HKCategoryTypeIdentifierSleepAnalysissleep_durationmin
See a real payload
{
"type": "HKQuantityTypeIdentifierStepCount",
"value": 6480,
"unit": "count",
"startDate": "2026-06-03T00:00:00Z",
"endDate": "2026-06-03T23:59:59Z",
"sourceRevision": { "source": { "name": "VeryFitPro" } }
// …active energy & sleep samples
}[
{
"category": "activity",
"type": "steps",
"value": 6480,
"unit": "count",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
},
{
"category": "sleep",
"type": "sleep_duration",
"value": 397,
"unit": "minute",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T23:41:00Z",
"endDateTime": "2026-06-03T06:18:00Z"
}
// …1 more normalized log
]Steps, active energy, and total sleep are what we’ve verified — this app’s evidenced write list is narrower than its white-label siblings’, so we don’t claim heart rate or workouts here. Brand attribution is also muddy: the data arrives under the VeryFitPro source name, not the device maker’s, so you can tell a user has a band, not which band. Coverage varies by model, so two devices on the same app can write different things. Sleep stages don’t cross. 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 VeryFitPro 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 VeryFitPro developer account needed — Sahha reads what VeryFitPro 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 VeryFitPro 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 VeryFitPro data the same day they add the SDK. The only per-source prerequisite: your user has VeryFitPro’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.
VeryFitPro integration questions
How does Sahha get VeryFitPro data?
VeryFitPro writes its paired band’s data to Apple Health, and Sahha reads it from there with its mobile SDK, delivering normalized data logs — no VeryFitPro API to integrate, and no per-device work.
Why does a VeryFitPro integration matter?
VeryFitPro is the white-label companion app for ID115- and Letsfit-class budget bands, with roughly 19 million downloads. Hardware in this class ships no app of its own across India, Southeast Asia, Latin America, the Middle East and Eastern Europe — so one integration covers a long tail of no-name devices that would otherwise never appear in your data.
What VeryFitPro data does Sahha receive?
Steps, active energy, and total sleep duration. That’s the evidenced list and we keep the page to it — this app writes less than its white-label siblings, so we don’t claim heart rate or workouts. Coverage also varies by model, and the data arrives under the app’s name rather than the device brand’s, so you can tell a user has a band without knowing which one.
Does the VeryFitPro integration work on Android?
No. Health Connect is nearly absent from this category — VeryFitPro’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 VeryFitPro integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and VeryFitPro 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 VeryFitPro data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for VeryFitPro and every other source.
Free for 30 days · No credit card
- One API for VeryFitPro 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