Stream SleepWatch data. Straight from the phone.
SleepWatch writes each tracked night — sleep duration, start and end time, and sleeping heart rate — to Apple Health, and Sahha’s SDK reads it into your app as normalized sleep biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Sleep duration
- 7:12 h
- Sleeping heart rate
- 54 bpm
- Wake time
- 06:48
Identical schema across 500+ sources
Your users connect SleepWatch. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every SleepWatch 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
SleepWatch 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 — SleepWatch today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What SleepWatch 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
SleepWatch, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
The sleep session — duration, start and end time — and its heart rate pass through Apple Health; some app-exclusive metrics may not.
Sleep
4
HealthKitSahha- sleepAnalysis · asleepsleep_durationmin
- sleepAnalysis · startDatesleep_start_time
- sleepAnalysis · endDatesleep_end_time
- heartRateheart_rate_sleepbpm
See a real payload
{
"type": "HKCategoryTypeIdentifierSleepAnalysis",
"value": "HKCategoryValueSleepAnalysisAsleepUnspecified",
"startDate": "2026-06-02T23:36:00Z",
"endDate": "2026-06-03T06:48:00Z",
"sourceRevision": { "source": { "name": "SleepWatch" } }
// …heart rate samples across the session
}[
{
"category": "sleep",
"type": "sleep_duration",
"value": 432,
"unit": "minute",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T23:36:00Z",
"endDateTime": "2026-06-03T06:48:00Z"
},
{
"category": "sleep",
"type": "heart_rate_sleep",
"value": 54,
"unit": "bpm",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-02T23:36:00Z",
"endDateTime": "2026-06-03T06:48:00Z"
}
// …2 more normalized logs
]SleepWatch writes to Apple Health by default — Bodymatter’s own docs frame it as opt-out ("if you don’t want SleepWatch to write to Health app you can disable this option"), so for most users the data is already flowing before you ask. It’s also one of the few sleep trackers that works on iPhone alone as well as with an Apple Watch, so it reaches users who don’t own a watch. What crosses is the sleep session and its heart rate: SleepWatch’s proprietary derived metrics — sleep rhythm, restful-sleep ratio, sleeping heart-rate dip — stay in the app. Accuracy varies with how the user tracks, and where they also wear a device writing sleep to Apple Health, Sahha deduplicates the overlapping sessions.
Missing a metric you need? Talk to us in the Sahha Slack — if SleepWatch 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 SleepWatch developer account needed — Sahha reads what SleepWatch 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 SleepWatch 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 SleepWatch data the same day they add the SDK. The only per-source prerequisite: your user has SleepWatch’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.
SleepWatch integration questions
How does Sahha get SleepWatch data?
SleepWatch writes each tracked sleep session to Apple Health, and Sahha reads it from there with its mobile SDK, delivering it as normalized sleep biomarkers — no SleepWatch API to integrate.
Do users have to turn the Apple Health sync on?
Usually not. Writing to Apple Health is on by default — Bodymatter’s documentation is phrased as opt-out, telling users they can disable the option if they don’t want it. That makes SleepWatch one of the more reliable app sources: the data is typically already there once the user grants your app permission through the Sahha SDK.
What SleepWatch data does Sahha receive?
The sleep session — duration, start time, and end time — plus the heart rate recorded across it. SleepWatch’s proprietary derived metrics, including sleep rhythm, restful-sleep ratio, and the sleeping heart-rate dip, stay inside SleepWatch and don’t cross. It’s a consumer sleep app, so accuracy depends on how the user tracks; if they also wear a device writing sleep to Apple Health, Sahha deduplicates the overlapping sessions.
Does the SleepWatch integration work on Android?
No. SleepWatch is an iPhone and Apple Watch app and writes to Apple Health, so this is an iOS-only integration. It does track on iPhone alone as well as with an Apple Watch, so users without a watch still produce data. Your users’ other Android sources still flow through the same Sahha SDK.
Is the SleepWatch integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and SleepWatch 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 SleepWatch data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for SleepWatch and every other source.
Free for 30 days · No credit card
- One API for SleepWatch 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