Mobile SDK
Samsung Health API integration
Mobile SDK · on-deviceOn-device only. This requires your own mobile app — there is no cloud API for it, from any vendor.Backend ready; Android SDK skeleton ships in Kotlin package

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.
Connect a Samsung Health user
Two calls. The first mints a hosted connect URL for your end-user; the second reads the normalised summaries once they have authorised with Samsung Health. Subscribe a webhook to receive the same objects as they land.
# 1. Create a connect session for your end-user
# The API key goes in X-WearLink-API-Key, not in Authorization.
curl -X POST https://wearlink.io/api/v1/connections/session \
-H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_id": "'"$USER_ID"'", "provider": "samsung-health", "redirect_uri": "https://yourapp.com/connected"}'
# → { "connect_url": "https://wearlink.io/widget/connect?token=...", "expires_in": 3600 }
# Redirect the user there; they authorise samsung-health and land back on your redirect_uri.
# The token is scoped to that one user — it is safe to put in a browser URL.
# 2. Pull normalised data whenever you want
curl -H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
"https://wearlink.io/api/v1/users/$USER_ID/summaries?provider=samsung-health&days=7"Samsung Health data available through WearLink
- Steps
- Heart rate
- Sleep
- Workouts
Webhook events you can subscribe to
steps.createdheart_rate.createdsleep.createdworkout.created
Normalised families this provider feeds: Sleep, Heart Rate Variability, Heart Rate, Workouts, Steps & Daily Activity, Calories & Energy, Blood Pressure, Body Composition, Body & Skin Temperature, Respiratory Rate & SpO2, Nutrition & Energy Balance, Stress.
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.
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.
FAQ
Samsung Health API — frequently asked questions
Does Samsung Health have a cloud API?
Should I integrate Samsung Health or Health Connect?
Is Samsung Health relevant for Indian users?
Related
Other on-device integrations

Apple HealthKit API
Mobile SDK · on-deviceApple Health has no cloud API and never has. Apple does not operate a server you can call — HealthKit is an on-device framework, and the only way to get the data is to run code inside an iOS app the user has installed and granted permission to.

Google Health Connect API
Mobile SDK · on-deviceHealth Connect is Android's on-device health data store and the successor to Google Fit. This matters urgently: the Google Fit APIs have been deprecated, and products still calling them are on a clock.
Start with Samsung Health — free for up to 3 users
No credit card. Your API key is issued at sign-up, and the hosted connect flow works from the first request.