Apple Health
Integration
Apple Health covers heart rate, sleep, steps, workouts, HRV, SpO2, and more. Open Wearables handles on-device sync, data normalization, and the iOS permission flow. One unified API for your backend.
What you get from Apple Health.
Continuous from Apple Watch
Stages, duration, quality score
Daily totals, floors climbed
Heart rate variability per reading
Blood oxygen saturation
All Apple Watch workout types
Periodic estimates from Apple Watch
During sleep and activity
From paired scales
From CGM or paired devices
How Apple Health integration works.
User connects Apple Health
Open Wearables handles HealthKit permission requests through a native mobile SDK. Your users grant access via Apple's standard consent screen.
Data is normalized to a unified schema
HealthKit data types are mapped to Open Wearables' unified health data schema. Heart rate, sleep, steps, workouts, HRV, and SpO2 all land in the same structure regardless of source.
Your application calls one unified API
The same endpoints work for every provider. No HealthKit-specific parsing logic, no iOS platform dependencies in your backend.
Apple Health is just the start.
One unified health data API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, Whoop, Oura, Strava, Polar, Suunto, Samsung Health, Google Health Connect. Same endpoints, same data format.
See all providers →Open health scores
Sleep, recovery, strain, stress, HRV, VO2 max. Open algorithms you can audit and tune for your population.
Explore scores →AI reasoning engine
MCP server for any LLM. Detect trends, flag anomalies, build coaching profiles for wellness, performance, or clinical use cases.
Learn more →Open Wearables vs SaaS vs native HealthKit.
| Aspect | Native HealthKit | SaaS APIs | Open Wearables |
|---|---|---|---|
| HealthKit permission flow | You build and maintain the iOS permission flow | Handled by provider SDK | Handled by Open Wearables SDK |
| Cloud API access | No native cloud API — data lives on-device only | Vendor-hosted REST API | Unified REST API, self-hosted |
| Data normalization | HealthKit-specific data types | Provider-defined schema | Unified schema across all providers |
| Multi-provider support | Separate integration per provider | Depends on vendor tier | One unified API for all providers |
| Per-user pricing | No platform fee | Charged per connected user | $0 per user |
| Data ownership | You own all data | Vendor stores your users' data | You own all data |
| iOS version changes | Your team tracks every iOS update | Vendor absorbs changes | Open Wearables absorbs upstream changes |
| Maintenance burden | Ongoing per iOS release | Vendor-managed | Minimal |
← scroll to see all →
Why Open Wearables for Apple Health.
HealthKit without the iOS-only constraint
Apple Health has no cloud API. Open Wearables bridges the gap with a mobile SDK that reads HealthKit data on-device and syncs it to your backend over a standard REST interface.
The broadest health data set on iOS
Apple Health aggregates data from Apple Watch, paired accessories, and third-party apps. Steps, heart rate, sleep, HRV, SpO2, blood glucose, workouts. Open Wearables exposes all of it.
No HealthKit-specific logic in your backend
HealthKit has its own data types, units, and query patterns. Open Wearables normalizes everything before it reaches your server. Your backend sees the same schema it uses for Garmin or Oura.
Combine Apple Health with other providers
Pair Apple Watch activity data with Oura sleep or Whoop recovery in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/sleep-sessions
{
"date": "2026-01-15",
"source": { "provider": "apple_health", "device": "Apple Watch Ultra 2" },
"duration_min": 467,
"deep_min": 82,
"rem_min": 94,
"hrv_rmssd_ms": 48.3,
"spo2_avg": 97.1
}
Open Wearables is open-source and self-hosted. The Apple Health integration uses a mobile SDK to sync data from HealthKit on-device.
Apple Health data in your app,
without the iOS integration overhead.
Open Wearables handles the HealthKit permission flow, on-device sync, and normalization. MIT licensed. $0 per user.
Common questions.
Does Open Wearables support Apple Health?
Yes. Open Wearables includes a mobile SDK that integrates with Apple HealthKit. Because HealthKit is on-device only with no cloud API, the SDK reads data on the user's device and syncs it to your Open Wearables backend.
Do I need an Apple Developer account?
Yes. You need an Apple Developer account and an iOS app to request HealthKit permissions. Open Wearables provides the SDK that handles the permission flow, but the app submission and developer credentials are yours to manage.
What health data does Open Wearables expose from Apple Health?
Heart rate, HRV, sleep stages, steps, distance, workouts, SpO2, respiratory rate, VO2 max, body weight, and blood glucose from paired CGM devices. Full schema is in the docs.
Which other providers can I connect alongside Apple Health?
Open Wearables currently integrates with Garmin, Polar, Whoop, Strava, Samsung Health, Google Health Connect, Suunto, and Oura. All providers share the same unified API schema.
Is Open Wearables production-ready?
Yes. Open Wearables is actively maintained and used in production. Check the GitHub releases for the current status of each provider integration.
Open Wearables is built and maintained by Momentum, a digital health agency reshaping healthcare through technology. Since 2016, they have been turning medical discoveries into compliant, scalable digital solutions. Momentum offers commercial services on top of Open Wearables for teams that need custom integrations, enterprise deployment, or SLA-backed support.
themomentum.ai →Other integrations
One API. Every provider. Zero per-user fees.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.
