Samsung Health
Integration
Samsung Health covers steps, heart rate, sleep, workouts, and stress data from Galaxy Watch and Android devices. Open Wearables handles Android permissions, data sync, and normalization. One unified API for your backend.
What you get from Samsung Health.
Daily totals from Galaxy devices
Continuous from Galaxy Watch
Stages, duration, sleep score
Run, bike, swim, 80+ types
Stress score from Galaxy Watch
Heart rate variability
Blood oxygen saturation
Weight, BMI, body fat from scales
Estimate from Galaxy Watch
Nightly from Galaxy Watch 6+
How Samsung Health integration works.
User connects their Samsung Health account
Open Wearables handles Samsung Health permissions through a native Android SDK. Your users grant access via Samsung's standard consent screen.
Data is normalized to a unified schema
Samsung Health data types are mapped to Open Wearables' unified health data schema. Steps, heart rate, sleep, workouts, stress, and HRV all land in the same structure regardless of Galaxy device model.
Your application calls one unified API
The same endpoints work for every provider. No Samsung-specific parsing logic, no Android platform dependencies in your backend.
Samsung 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, Apple Health, Polar, Suunto, 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 Samsung Health SDK.
| Aspect | Native Samsung Health SDK | SaaS APIs | Open Wearables |
|---|---|---|---|
| Samsung Health permissions | You build and maintain the Android permission flow | Handled by provider SDK | Handled by Open Wearables SDK |
| Cloud API access | Limited cloud API — most data is on-device | Vendor-hosted REST API | Unified REST API, self-hosted |
| Data normalization | Samsung-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 |
| Samsung SDK updates | Your team tracks every Samsung update | Vendor absorbs changes | Open Wearables absorbs upstream changes |
← scroll to see all →
Why Open Wearables for Samsung Health.
Galaxy Watch data without the SDK complexity
Samsung Health's native SDK is Android-only and requires per-device permission flows. Open Wearables wraps the complexity behind a standard REST interface your backend can call without any Samsung-specific code.
The most widely used Android health platform
Samsung Health is installed on hundreds of millions of Android devices. Galaxy Watch tracks steps, heart rate, sleep, stress, SpO2, and body composition. Open Wearables exposes all of it through one unified API.
No Samsung-specific logic in your backend
Samsung has its own data types, units, and permission model. Open Wearables normalizes everything before it reaches your server. Your backend sees the same schema it uses for Garmin or Oura.
Combine with other providers
Pair Samsung Health activity data with Oura sleep or Whoop recovery in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/workouts
{
"date": "2026-01-15",
"source": { "provider": "samsung_health", "device": "Galaxy Watch 7" },
"type": "run",
"distance_m": 9300,
"steps": 11204,
"heart_rate_avg_bpm": 155,
"stress_score": 32
}
Open Wearables is open-source and self-hosted. The Samsung Health integration uses a mobile SDK to sync data from Samsung Health on-device.
Samsung Health data in your app,
without the Android integration overhead.
Open Wearables handles Samsung permissions, on-device sync, and normalization. MIT licensed. $0 per user.
Common questions.
Does Open Wearables support Samsung Health?
Yes. Open Wearables includes a native Android SDK that integrates with Samsung Health. The SDK reads data on the user's device and syncs it to your Open Wearables backend over a standard REST interface.
Do I need a Samsung Developer account?
Yes. You need a Samsung Developer account and an Android app to request Samsung Health permissions. Open Wearables provides the SDK that handles the permission flow, but the app submission and developer credentials are yours to manage.
What data does Open Wearables expose from Samsung Health?
Steps, heart rate, sleep, workouts, stress, HRV, SpO2, body composition, VO2 max, and skin temperature from Galaxy Watch 6 and newer. Full schema is in the docs.
Which other providers can I connect alongside Samsung Health?
Open Wearables currently integrates with Garmin, Polar, Whoop, Strava, Apple 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.
