Samsung Health API integration
Mobile SDKOn-device only. This requires your own mobile app — there is no cloud API for it.
Samsung Health matters in proportion to Galaxy's market share, which in India and much of Asia is substantial. Galaxy Watch users are a meaningful population that a Fitbit-and-Oura-only integration misses entirely.
Access is the awkward part. Samsung's health SDK requires partner approval, and the terms have shifted more than once. Many Galaxy Watch users also write into Health Connect, which is frequently the more practical route to the same data on modern devices.
WearLink supports the SDK push path and normalises into the shared schema. If your Android app already integrates Health Connect, check what your Samsung users actually surface there before investing in a separate Samsung SDK path.
How the Samsung Health integration works
- Authentication
- On-device permissions, Samsung partner approval for the SDK
- Sync model
- SDK push from your Android app.
- API base
- On-device (Samsung Health SDK) — no cloud API
- Integration type
- Mobile SDK
Samsung Health data available through WearLink
Everything below arrives in the shared normalised schema. The same field names and units apply whether the record came from Samsung Health or from any other provider, so your scoring, charting and storage code is written once.
- Steps
- Heart rate
- Sleep
- Workouts
Webhook events you can subscribe to
steps.createdheart_rate.createdsleep.createdworkout.createdConnect a Samsung Health user
Two calls: create a connect session for your end user, then read their normalised data. You never handle Samsung Health OAuth credentials, token refresh or webhook registration.
# 1. Create a connect session for your end-user
curl -X POST https://wearlink.io/api/v1/connections/session \
-H "Authorization: Bearer $WEARLINK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_id": "'"$USER_ID"'", "provider": "samsung-health"}'
# → { "connect_url": "https://wearlink.io/widget/connect?token=..." }
# Redirect the user there; they authorise samsung-health and land back on your redirect_uri.
# 2. Pull normalised data whenever you want
curl -H "Authorization: Bearer $WEARLINK_API_KEY" \
"https://wearlink.io/api/v1/users/$USER_ID/summaries?provider=samsung-health&days=7"What makes the Samsung Health API hard to integrate directly
These are the things that turn an estimated one-week integration into a one-month one. They are worth knowing whether you use WearLink or build it yourself.
Partner approval required
The Samsung Health SDK is not open self-service. Approval is a gate and the terms have changed historically.
Health Connect may be the better route
On recent Galaxy devices Samsung Health writes into Health Connect, which is often simpler than integrating the Samsung SDK directly.
On-device only
As with HealthKit and Health Connect, there is no server to call.
Samsung Health API — frequently asked questions
- Does Samsung Health have a cloud API?
- No public one. Integration is through the on-device SDK, which requires Samsung partner approval.
- Should I integrate Samsung Health or Health Connect?
- For most Android products, Health Connect first — Samsung Health writes into it on recent devices, and it covers non-Samsung Android users too.
- Is Samsung Health relevant for Indian users?
- Yes. Galaxy has a large share of the Indian smartphone and smartwatch market, so Samsung users are a population a US-centric integration list tends to underweight.
Other integrations
Start with Samsung Health — free for up to 3 users
No credit card. Create an account, add your provider credentials once, and your users connect through a hosted widget or our mobile SDK.