Stream Sleep Number data. No Sleep Number API needed.
The Sleep Number smart bed writes your sleep sessions to Apple Health through SleepIQ — and Sahha’s SDK reads them into your app as normalized biomarkers and sleep scores, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Sleep duration
- 7:02 h
- Time in bed
- 7:36 h
Identical schema across 500+ sources
Your users connect Sleep Number. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Sleep Number 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
Sleep Number 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 — Sleep Number today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Sleep Number syncs through Apple Health.
Works with
Smart BedClimateCoolClimate360Request 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
Sleep Number, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Sleep session times pass through Apple Health; some app-exclusive metrics may not.
Sleep
2
HealthKitSahha- sleepAnalysis · asleepsleep_durationmin
- sleepAnalysis · inBedsleep_stage_in_bedmin
See a real payload
{
"type": "HKCategoryTypeIdentifierSleepAnalysis",
"value": "HKCategoryValueSleepAnalysisAsleepUnspecified",
"startDate": "2026-06-02T23:36:00Z",
"endDate": "2026-06-03T06:38:00Z",
"sourceRevision": { "source": { "name": "Sleep Number" } }
// …in-bed samples
} [
{
"category": "sleep",
"type": "sleep_duration",
"value": 422,
"unit": "minute",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T23:36:00Z",
"endDateTime": "2026-06-03T06:38:00Z"
}
// …time-in-bed log
] The Sleep Number bed writes sleep session start and end times to Apple Health via SleepIQ. Its SleepIQ score, heart rate, and breathing detail stay in the SleepIQ app. It’s an iOS integration, so its data lands in Apple Health — not Health Connect.
Missing a metric you need? Talk to us in the Sahha Slack — if Sleep Number 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 Sleep Number developer account needed — Sahha reads what Sleep Number 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 Sleep Number 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 Sleep Number data the same day they add the SDK. The only per-source prerequisite: your user has Sleep Number’s Apple Health sync switched on — most source apps enable it by default.
Sleep Number integration questions
How does Sahha get Sleep Number data?
The SleepIQ app writes your sleep sessions to Apple Health, and Sahha reads them from there with its mobile SDK — no Sleep Number API to integrate.
Does Sahha get the SleepIQ score, heart rate, and breathing?
No. Apple Health receives the sleep session times; SleepIQ’s proprietary score, heart rate, and breath-rate detail stay in the SleepIQ app. Sahha computes its own sleep scores from the session data.
Do I need a mobile app to use the Sleep Number integration?
Yes. Because Sleep Number data lands in Apple Health on the user’s device, you embed the Sahha mobile SDK to read it. Cloud-only sources like Oura don’t need the SDK, but on-device sources like Sleep Number do.
Is the Sleep Number integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Sleep Number 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 Sleep Number data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Sleep Number and every other source.
Free for 30 days · No credit card
- One API for Sleep Number 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



