Stream NoiseFit data. No NoiseFit API needed.
Noise watches write sleep, heart rate, steps, and calories to Apple Health through the NoiseFit app — and Sahha’s SDK reads them into your app as normalized biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Sleep duration
- 6:52 h
- Resting heart rate
- 66 bpm
- Steps
- 7,860
Identical schema across 500+ sources
Your users connect NoiseFit. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every NoiseFit 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
NoiseFit 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 — NoiseFit today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What NoiseFit syncs through Apple Health.
Works with
NoiseFit ColorFit ProColorFit UltraNoiseFit HaloRequest 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
NoiseFit, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Sleep, heart rate, steps, and calories pass through Apple Health; some app-exclusive metrics may not.
Sleep
1
HealthKitSahha- sleepAnalysis · asleepsleep_durationmin
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
Activity & exercise
2
HealthKitSahha- stepCountstepscount
- activeEnergyBurnedactive_energy_burnedkcal
See a real payload
{
"sampleType": "HKCategoryTypeIdentifierSleepAnalysis",
"value": "asleep",
"startDate": "2026-06-02T23:50:00Z",
"endDate": "2026-06-03T06:42:00Z",
"sourceRevision": { "source": { "name": "NoiseFit" } }
} [
{
"category": "sleep",
"type": "sleep_duration",
"value": 412,
"unit": "minute",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T23:50:00Z",
"endDateTime": "2026-06-03T06:42:00Z"
}
] NoiseFit writes to Apple Health on iOS — its Android path syncs to Google Fit rather than Health Connect, so Sahha reads it on iOS. Sleep arrives as total duration; some NoiseFit models sync steps only.
Missing a metric you need? Talk to us in the Sahha Slack — if NoiseFit 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 NoiseFit developer account needed — Sahha reads what NoiseFit 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.
- 02
Prompt 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 NoiseFit 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 NoiseFit data the same day they add the SDK. The only per-source prerequisite: your user has NoiseFit’s Apple Health sync switched on — most source apps enable it by default.
NoiseFit integration questions
How does Sahha get NoiseFit data?
Noise watches write to Apple Health through the NoiseFit app, and Sahha reads them from there with its mobile SDK — no NoiseFit API to integrate.
Which NoiseFit metrics does Sahha provide?
Sleep duration, heart rate, steps, and active energy — normalized into Sahha’s schema. Coverage depends on the model; some NoiseFit watches write steps only.
Does the NoiseFit integration work on Android?
NoiseFit writes to Apple Health on iOS, which is where Sahha reads it. On Android the app syncs to Google Fit rather than Health Connect. The same Sahha SDK reads Health Connect on Android for your other sources.
Is the NoiseFit integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and NoiseFit 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 NoiseFit data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for NoiseFit and every other source.
Free for 30 days · No credit card
- One API for NoiseFit 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



