Device IntegrationHealthcare Interoperability

Samsung Health API Integration Guide 2026: Data SDK

June 28, 202616 min read
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Samsung Health API Integration Guide 2026: Data SDK

The Samsung Health API route is the Samsung Health Data SDK, an Android SDK that reads data on the user's phone. There is no cloud API, so you need your own Android app and your own server. You can build and test the same day in Samsung Health developer mode, but your app only works for real users after Samsung approves your partner request. Samsung says the data is for "fitness and wellness only" and "not for the diagnosis or treatment of any medical condition". That line decides most healthcare projects. Samsung publishes no fees, no review time and no BAA.

Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery, and our remote patient monitoring software work covers RPM programs.

Samsung Health integration at a glance

QuestionShort answer
Is there an official API?Yes, an on-phone Android SDK: Samsung Health Data SDK v1.1.0. No server or cloud API found.
Cost to the developerNot published.
Does the end user need anything paid?No subscription found. The user needs an Android 10 or later phone with Samsung Health 6.30.2 or later. Samsung and non-Samsung phones both work. Samsung Health is fed by Galaxy Watch, Galaxy Ring and phone sensors, so expect wearable types such as sleep apnea to be empty for users without one. Test this.
Same-day start?Yes, in developer mode, for testing only.
Who approves scale-up?Samsung, through a partner request before you distribute. No published review time.
HIPAA and BAANot published. Data comes from the user's phone to your app, so your own HIPAA program applies.
Raw or summary data?Granularity not published for the Data SDK. Raw ECG, PPG and accelerometer streams come only from Samsung's separate Sensor SDK, inside a Galaxy Watch app.
Medical use"Fitness and wellness purposes only", per Samsung's SDK overview.
First buildAbout 3 weeks for the Android reader, upload and FHIR mapping, then Samsung partner approval with no published wait. Our estimate.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?LatencySupported dataNot supportedBest for
Samsung Health Data SDKYes, AndroidYes, to receive uploadsYes. Partner request approval to distribute. Access code to write data.Yes, v1.1.0, Java 17 or laterWhen your app reads on the phone and uploadsThe read and write types listed belowiOS, emulators, ECG, HRV, raw sensor streams, server pullAndroid-heavy programs that need Galaxy Watch or Ring data.
Legacy Samsung Health SDK for AndroidYesYesDeprecated as of July 31, 2025Old SDKn/an/aNew buildsNo one. Migrate to the Data SDK.
Cloud REST APIn/an/aNone foundn/an/aNoneAlln/a
Webhooksn/an/aNone foundn/an/aNone. The SDK has a "read changes" call on the phone.Server pushn/a
Health ConnectYes, AndroidYesSamsung terms not published for this routeHealth ConnectGalaxy Watch heart rate syncs late to save batterySamsung Health reads and writes Health Connect since version 6.22.5: steps, exercise, heart rate, SpO2, blood pressure, blood glucose, sleep and stages, nutrition, weight, body fatSamsung says the synced scope can change between versionsTeams that already read Health Connect
Apple Healthn/an/an/an/an/aSamsung Health runs on Android. No iOS route found.Alln/a
Partner or enterprise APIYesYesThe partner request is the only program found. No separate enterprise API found.Data SDKSame as Data SDKSame as Data SDKSame as Data SDKAny distributed app.
Aggregators, checked 10 November 2026Terra, Junction and Thryve list Samsung Health through their phone SDK, not a cloud API. Thryve says production needs Samsung verification. Validic lists it as restricted and not taking new applications. Spike lists it with no route stated. ROOK does not list it. Sahha coverage is not published.
File exportn/an/aNot publishedn/an/aNot in our sourcesn/aNot assessed. Do not plan on it.

For a healthcare program that needs Galaxy Watch or Galaxy Ring data, build on the Data SDK and file the partner request in week one, because your app cannot reach real users until Samsung approves. Keep the product out of diagnosis and treatment claims. For a wellness app, the Data SDK is the richest Samsung route. If you already read Health Connect, test whether it gives you enough before you add the SDK.

Build it yourself, use an aggregator, or work with a partner

QuestionBuild in-houseWearable aggregatorBuild with a partner (Nirmitee)
Whose Samsung partner approval?YoursDepends on the aggregator. Thryve says production needs Samsung verification.Yours. We build the app under your package name and signing key.
Wellness-only clause riskYour counsel reads itSame clause. Samsung's wording applies whoever reads the data.Your counsel reads it. We keep screens and alerts out of diagnosis.
Change tracking and uploadYou build readChanges, background work and uploadThe aggregator's phone SDK does itWe build them, then hand them to you or run them
Data modelSamsung's data pointsThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterOne new build per deviceMany devices through one SDKSame pattern reused across devices
Time to first real userDepends on your team, plus Samsung approvalDepends on the aggregator, plus Samsung verificationAbout 3 weeks of build in our estimate, plus Samsung approval with no published wait
Cost shapeEngineering timeAggregator fee. Pricing for Samsung Health on these platforms is not published.Project fee, scoped after a call
Every way to get Samsung Health data, and what each one needs.

What data you can get

These are the types Samsung lists on the Data SDK overview. Granularity, history window and latency are not published on the pages we read. All reads are pulls from the phone. Confirm granularity per type on a test phone before you design screens or study endpoints.

Data typeReadWriteGranularityHistory windowPush or pull
Activity summaryYesNoNot publishedNot publishedPull on phone
Active calories burned goal, active time goalYesNoNot publishedNot publishedPull
Steps, step goalYesNoNot publishedNot publishedPull
Floors climbedYesYesNot publishedNot publishedPull
Exercise, exercise locationYesYesNot publishedNot publishedPull
Heart rateYesYesNot publishedNot publishedPull
Irregular heart rhythm notificationYesNoNot publishedNot publishedPull
Blood oxygen (SpO2)YesYesNot publishedNot publishedPull
Skin temperatureYesNoNot publishedNot publishedPull
Body temperatureYesYesNot publishedNot publishedPull
Blood pressureYesYesNot publishedNot publishedPull
Blood glucoseYesYesNot publishedNot publishedPull
Body compositionYesYesNot publishedNot publishedPull
Sleep, sleep goalYesSleep yes, goal noNot publishedNot publishedPull
Sleep apneaYesNoNot publishedNot publishedPull
Energy scoreYesNoNot publishedNot publishedPull
Nutrition, nutrition goalYesNutrition yes, goal noNot publishedNot publishedPull
Water intake, water intake goalYesWater yes, goal noNot publishedNot publishedPull
User profileYesNoNot publishedn/aPull

Blood pressure, glucose and SpO2 values in Samsung Health can come from connected devices that write them. Keep the source device on every reading.

What is inside one Samsung Health sleep record

Sleep is the richest record in the Data SDK. These fields come from Samsung's programming guide and sleep code lab.

Field or callWhat it holds
DURATIONHow long the sleep lasted
SLEEP_SCORESamsung's calculated sleep quality. Read only: apps cannot insert, update or delete it.
SESSIONSA list of sessions. A long wake splits one night into several sessions. Each session has Light, REM, Deep and Awake stages.
readAssociatedData()Blood oxygen and skin temperature measured during that sleep, when the user wore a Galaxy Watch
uid and data sourceEvery data point carries an id, the app that wrote it and the device that measured it

If a user wears both a Galaxy Watch and a Galaxy Ring, Samsung Health merges them into one sleep session. Leave the device filter off to get the merged record. For totals, aggregate calls group results by minute, hour or day. Heart rate supports minimum and maximum, and steps support totals. Units per field sit in the API reference, which needs a Samsung account sign-in, so we did not check them.

Need raw signals? Samsung's Sensor SDK (v1.4.1) runs in a Wear OS app on Galaxy Watch4 and later, not on the phone. Its spec lists raw ECG at 500 Hz, raw PPG at 25 Hz continuous or 100 Hz on demand, accelerometer at 25 Hz, and heart rate with inter-beat intervals at 1 Hz. Samsung says the inter-beat intervals can be used to calculate HRV. The Sensor SDK does not share data with Samsung Health, needs its own partner request, and carries the same wellness-only note.

What you cannot get

  • ECG. Not in the read list.
  • Heart rate variability (HRV). Not in the read list.
  • Raw sensor streams through the Data SDK. Samsung's separate Sensor SDK gives raw ECG, PPG and accelerometer data, but only inside your own Galaxy Watch app.
  • Any server or cloud API. All reads happen on the phone.
  • iPhone users. Samsung Health runs on Android.
  • Data on emulators. The SDK does not support them.
  • Writing data without an access code from Samsung, issued after partner approval.
  • Activity summary, goals, energy score, skin temperature, sleep apnea and irregular rhythm notifications as write types. Read only.
  • Real users before partner approval. Without it, the app works only with developer mode on.

How to get access

  1. Download Samsung Health Data SDK v1.1.0 from Samsung Developer. Same day.
  2. Turn on developer mode in Samsung Health on your test phone. Samsung says developer mode is for testing only and must not be shared with users. Reading can be tested in developer mode without a partner request.
  3. Build your Android app with the SDK. Requirements: Samsung Health 6.30.2 or later, Android 10 (API 29) or later, Java 17 or later, a real phone.
  4. Submit the partner request before you distribute. Samsung approves. On approval, your app's package name and SHA-256 signing certificate are registered. Review time: not published. Developer forum threads describe the program as unclear or paused at times.
  5. If you write data, receive the access code Samsung issues after approval.
  6. Pass Samsung's app verification. The SDK checks your package name and SHA-256 signature against Samsung's register. A mismatch returns error 2003, "Permission not allowed due to SDK policy error".
  7. Release on Google Play. Check that the SHA-256 you registered matches the key that signs the build users install.

From zero to your first Samsung Health data in four steps

There is no server API and no webhook, so all four steps happen in your Android app on the user's phone.

  1. Get the SDK and turn on developer mode. Download the Data SDK and import samsung-health-data-api.aar. On a real phone, open Samsung Health, go to Settings, About Samsung Health, and tap the version line 10 or more times. Choose Developer mode (Samsung Health Data SDK) and turn on Developer Mode for Data Read.
  2. Ask the user for permission. Build a set of Permission.of(data type, AccessType.READ) items and call requestPermissions(). Samsung Health shows its own pop-up, and the user allows each type. Call getGrantedPermissions() first so you do not ask twice.
  3. Read data on the phone. This is Samsung's own example for heart rate in a time range:
    val healthDataStore = HealthDataService.getStore(applicationContext)
    val localTimeFilter = LocalTimeFilter.of(startTime, endTime)
    val readRequest = DataTypes.HEART_RATE.readDataRequestBuilder
        .setLocalTimeFilter(localTimeFilter)
        .setOrdering(Ordering.DESC)
        .build()
    val heartRateList = healthDataStore.readData(readRequest).dataList
    Add ReadSourceFilter.fromDeviceType(DeviceGroup.WATCH) to keep only watch readings.
  4. Sync only what changed, then file the partner request. Store the last sync time. Call readChanges() with a change time filter from that time to now. Each change is UPSERT with the data point, or DELETE with the deleted id. Upload those to your server. Before release, send Samsung your package name and the SHA-256 of the app signing key. For Google Play, that key is in Play Console under Release, Setup, App integrity.

Terms you must know

We read Samsung's SDK overview and app creation process pages. We did not read the Samsung Developer Terms or the partner agreement, so clause numbers below are not available.

  • Medical use: Samsung says the data is for "fitness and wellness only" and "not for the diagnosis or treatment of any medical condition". For a healthcare product, do not diagnose, treat or trigger clinical decisions from this data alone. Show it as context alongside clinical-grade readings. For a wellness app, this fits normal use.
  • PHI, HIPAA and BAA: not published. The data moves from the user's phone to your app. Samsung does not send it to you from a server. Once it sits on your server with patient identity, your HIPAA program applies.
  • Storage and retention: not published on the pages we read. Read the partner agreement.
  • AI training: not published on the pages we read.
  • Display and branding: not published on the pages we read.
  • Data selling: not published on the pages we read. Ask Samsung for the policy that governs data use before you sign.
  • Developer mode: for testing only. Do not ask users to turn it on to get around approval.
  • Termination and deprecation: Samsung deprecated the legacy SDK on July 31, 2025 and told partners to migrate. Plan for the same to happen again.
  • Competing products: not published.

Cost and payment terms

  • SDK and partner program fees: not published.
  • End-user subscription: none found. Users need Samsung Health on an Android 10 or later phone. Watch and ring data need that hardware.
  • Enterprise contract: not published.
  • Aggregator fees: not published in the sources we read.

Use cases

One reading from Samsung Health to the EHR.

1. Remote patient monitoring with blood pressure and glucose

The patient's connected cuff or meter writes readings into Samsung Health. Your Android RPM app reads new blood pressure and glucose records on a schedule, uploads them, and your server writes FHIR Observations to the EHR. Data used: blood pressure, blood glucose.

  • Samsung says the data is for wellness only. Fix: for billable RPM, take readings from the meter vendor's own clinical route and use Samsung data as backup, after legal review.
  • Duplicate readings when the meter app also uploads elsewhere. Fix: dedupe by time and device.
  • App killed by battery saver, so readings arrive late. Fix: scheduled background work that reads everything since the last successful upload.

2. Sleep and sleep apnea program

The member wears a Galaxy Watch or Ring. Your app reads sleep sessions, SpO2 and sleep apnea results each morning and shows the member trends. A sleep coach sees weekly summaries. Data used: sleep, blood oxygen, sleep apnea, skin temperature.

  • No watch or ring, so no SpO2 or apnea data. Fix: check device presence at sign-up.
  • Apnea results used for diagnosis. Fix: route to a clinician for proper testing. Do not diagnose.

3. Cardiac program with irregular rhythm notifications

Your app reads irregular heart rhythm notifications and heart rate. A care team sees a flag to contact the patient. Data used: irregular heart rhythm notification, heart rate.

  • ECG not available through the SDK. Fix: ask the patient for the ECG through another route.
  • Flags treated as diagnosis. Fix: wording on screen says "notification from the patient's watch".

4. Wellness and coaching app

The user grants permissions in Samsung Health. Your app reads steps, exercise, sleep and energy score and coaches on them. Data used: steps, exercise, sleep, energy score, nutrition.

  • User declines some permissions. Fix: check granted permissions and explain what each one unlocks.
  • Partner approval delayed. Fix: file in week one and run a closed beta in developer mode on staff phones only.

5. Clinical trial with Galaxy wearables

Participants get a study app on Android. It reads steps, sleep and heart rate and uploads daily. Data used: steps, sleep, heart rate.

  • Participants on iPhone. Fix: a second route for iOS or Android-only enrollment.
  • Granularity and history window not published. Fix: pilot on study phones to confirm what you get before you lock endpoints.

Samsung Health data in an EHR or remote monitoring program

Most healthcare teams want Samsung Health readings next to clinical data. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Samsung's wellness-only line still applies, so show these as patient-reported context.

Samsung Health valueFHIR ObservationCode
Heart rateHeart rate, beats per minuteLOINC 8867-4
Blood oxygenOxygen saturation by pulse oximetry, percentLOINC 59408-5
Blood pressureBlood pressure panel with systolic and diastolic componentsLOINC 85354-9, 8480-6, 8462-4
Blood glucoseGlucose in bloodLOINC 2339-0. Check the method fits the meter.
Body temperatureBody temperatureLOINC 8310-5
StepsNumber of stepsLOINC 55423-8
Body composition weightBody weightLOINC 29463-7
Sleep durationSleep durationLOINC 93832-4
Sleep score, energy score, irregular rhythm notificationDevice-specific ObservationYour own code system. These are Samsung's own scores and flags, so no standard code fits exactly.

Keep the Samsung data uid and the source device on each Observation. When readChanges() returns a DELETE with that uid, you can find the Observation and retract it.

Known blockers and gotchas

  • Partner approval gates release. Without it, the app only works with developer mode on. File early.
  • Unclear partner program. Developer forum threads describe it as unclear or paused at times. Escalate through Samsung Developer Support.
  • Legacy SDK deprecated. Apps on the old Samsung Health SDK must move to the Data SDK. Thryve reports that apps approved under the old SDK need a new approval.
  • Wellness-only wording. Blocks diagnostic claims built on this data.
  • No emulator support. Budget real test phones.
  • Java 17 and Android 10 minimums. Check your build toolchain and your users' phones.
  • Signing key must match. Check that the SHA-256 registered with Samsung matches the key that signs the build users install.
  • No ECG or HRV in the Data SDK. Plan another source if you need them. The Sensor SDK on Galaxy Watch4 and later gives raw ECG and inter-beat intervals.
  • Developer mode is not for users. Samsung says not to share its guide with app users.

Delivery timeline

Our estimate, not a measured figure.

WeekWorkDepends on Samsung?
1SDK setup, developer mode, permission flow, file the partner requestYes, the request starts Samsung's clock
1 to 2Readers for the types you need, change reads, background workNo
2 to 3Upload, dedupe, FHIR mapping, screensNo
3 onwardPartner approval, access code for writes, app verificationYes. No published wait.
After approvalPlay release with registered signatureGoogle Play review

Questions to ask Samsung before you sign

  1. How long does partner approval take today, and who is our contact?
  2. What terms govern use of the data in a healthcare product, including storage, AI and sharing with clinicians?
  3. Does the "fitness and wellness only" line stop us from showing readings to a care team?
  4. Are there any fees for the SDK or partnership?
  5. What granularity and history window does each data type return?
  6. Which Samsung Health data is also written to Health Connect?
  7. Is ECG or HRV on the roadmap for the Data SDK?
  8. What does app verification check?

Other device integration guides

Samsung Health is often one source among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.

Ready to build your Samsung Health integration?

Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. Book a call about your device integration.

For whoever builds this

Auth and permissions

  • No OAuth or server token. The user grants per-type permissions inside Samsung Health through the SDK's permission request.
  • Writes need the access code issued after partner approval.
  • Release builds must match the registered package name and SHA-256 signature.

SDK

  • Samsung Health Data SDK v1.1.0. It reads, and after approval writes, the types listed above. The main calls, from Samsung's programming guide (read 11 Nov 2026), are HealthDataService.getStore(), requestPermissions(), readData(), aggregateData(), readChanges() and readAssociatedData().
  • Requirements: Samsung Health 6.30.2+, Android 10 (API 29)+, Java 17+. No emulator.
  • Rate limits: not published. Webhooks: none, so there is nothing to sign.

FHIR mapping

DataLOINCStatus
Heart rate8867-4Checked in LOINC 11 Nov 2026. Confirm against your IG.
SpO259408-5Checked in LOINC 11 Nov 2026
Blood pressure panel, systolic, diastolic85354-9, 8480-6, 8462-4Checked in LOINC 11 Nov 2026
Blood glucose2339-0Checked in LOINC 11 Nov 2026 (glucose in blood). Check the method fits the meter.
Body temperature8310-5Checked in LOINC 11 Nov 2026
Steps55423-8Checked in LOINC 11 Nov 2026
Body weight29463-7Checked in LOINC 11 Nov 2026
Sleep duration93832-4Checked in LOINC 11 Nov 2026

Version notes

  • Data SDK v1.1.0 is the current download. Legacy Samsung Health SDK for Android deprecated July 31, 2025.

Sources

  • Samsung Health Connect FAQ, https://developer.samsung.com/health/health-connect-faq.html, read 10 November 2026.
  • Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
  • Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
  • Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
  • ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
  • Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
  • Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
  • Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
  • Samsung Health Data SDK overview, https://developer.samsung.com/health/data/overview.html, read November 10, 2026
  • Samsung Health Data SDK app creation process, https://developer.samsung.com/health/data/process.html, read November 10, 2026
  • Samsung Health SDK for Android (legacy), https://developer.samsung.com/health/android, read November 10, 2026
  • Samsung Health Data SDK migration guide, https://developer.samsung.com/health/data/migration-guide/overview.html, read November 10, 2026
  • Thryve docs, Samsung Health (third party), https://docs.thryve.health/thryve-data-sources/samsung-health, read November 10, 2026
  • Samsung Developer forum thread (developer report), https://forum.developer.samsung.com/t/unclear-partnership-program/17277, read November 10, 2026
  • Samsung Health Data SDK programming guide: data types, data access, filter and group, device manager, https://developer.samsung.com/health/data/guide/features/data-types.html, read November 11, 2026
  • Data SDK guide: permission request, read data, read changes, aggregate data, associated data, https://developer.samsung.com/health/data/guide/hello-sdk/read-data.html, read November 11, 2026
  • Data SDK developer mode and app verification, https://developer.samsung.com/health/data/guide/app-verification.html, read November 11, 2026
  • Data SDK FAQ, https://developer.samsung.com/health/data/faq.html, read November 11, 2026
  • Data SDK release note, https://developer.samsung.com/health/data/release-note.html, read November 11, 2026
  • Samsung sleep data code lab, https://developer.samsung.com/codelab/health/sleep-data.html, read November 11, 2026
  • Samsung Health Sensor SDK overview, data specifications, FAQ and process, https://developer.samsung.com/health/sensor/guide/data-specifications.html, read November 11, 2026
  • Samsung blog, Accessing Samsung Health data through Health Connect, https://developer.samsung.com/health/blog/en/accessing-samsung-health-data-through-health-connect, read November 11, 2026

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does Samsung Health have an API?

Samsung offers the Samsung Health Data SDK, an Android SDK that reads data on the user's phone. We found no cloud or server API. Your Android app reads the data and sends it to your server.

Can I use the old Samsung Health SDK?

No. Samsung deprecated the legacy Samsung Health SDK for Android as of July 31, 2025 and told partners to migrate to the Data SDK. Thryve reports that apps approved under the old SDK need a new approval.

Do I need Samsung's approval?

Yes, to distribute. Without partner approval your app works only with Samsung Health developer mode on, which is for testing. Writing data also needs an access code issued after approval.

How long does Samsung Health partner approval take?

Samsung does not publish a review time. Developer forum threads describe the program as unclear or paused at times, so file the request in the first week.

What data can I read from Samsung Health?

Samsung lists activity summary, steps, exercise and location, floors, heart rate, irregular heart rhythm notifications, blood oxygen, skin and body temperature, blood pressure, blood glucose, body composition, sleep, sleep apnea, energy score, nutrition, water, goals and user profile.

Can I get ECG or HRV from Samsung Health?

Not through the Data SDK. ECG and HRV are not in Samsung's list of read data types.

Can I get Samsung Health data through Health Connect?

Yes. Samsung Health syncs with Health Connect since version 6.22.5 (October 2022), once the user links them. Samsung's list covers steps, exercise, heart rate, blood oxygen, blood pressure, blood glucose, sleep sessions and stages, nutrition, weight, body fat, basal metabolic rate and height. Samsung notes the synced scope can change between versions, activity tracker data is not synced, and continuous watch heart rate reaches the phone late to save battery. For energy score, sleep apnea, skin temperature or irregular rhythm notifications, use the Data SDK.

Can Samsung Health data be used for medical diagnosis?

Samsung says the data is for "fitness and wellness only" and "not for the diagnosis or treatment of any medical condition". Do not build diagnosis or treatment decisions on it alone. Use it as context next to clinical-grade readings, after your own legal review.

Does Samsung Health work on iPhone or non-Samsung phones?

Samsung says the SDK works on Samsung and non-Samsung Android phones with Android 10 or later and Samsung Health 6.30.2 or later. Samsung Health runs on Android, so there is no iPhone route.

Is there a cost for the Samsung Health Data SDK?

Samsung does not publish fees for the SDK or the partner program. We found no end-user subscription requirement.

How long does a Samsung Health integration take?

Our estimate is about 3 weeks for the Android reader, upload and FHIR mapping. Partner approval comes on top and has no published wait.

Does Samsung sign a BAA for Samsung Health data?

Samsung does not publish a BAA, HIPAA or FDA position for the Data SDK. The data moves from the user's phone to your app, so once it sits on your server with patient identity, your own HIPAA program applies.

Which permissions does the Samsung Health Data SDK ask for?

One per data type and access type, such as heart rate with read access or blood glucose with write access. Your app calls requestPermissions() and Samsung Health shows a pop-up where the user allows each one. Samsung also registers a data type scope for your app at approval. A type outside that scope returns ERROR_ACCESS_CONTROL.

Does Samsung Health send webhooks when data changes?

No. There is no server push. Your app calls readChanges() for each data type with a time filter since the last sync. Each change comes back as UPSERT with the new data point or DELETE with the deleted id, plus the change time.

How much history can my app read when a user first connects?

Samsung does not publish a history limit. Reads take a time filter, so you can request any range on first connect. Test the real depth on your own phones before you promise a number to users.

What does Samsung Health error 2003 mean?

"Permission not allowed due to SDK policy error" means your package name or SHA-256 signature does not match what Samsung registered. For Google Play, register the app signing key from Play Console, not your upload key. During development, developer mode skips this check.

Can I get raw ECG, PPG or HRV from a Galaxy Watch?

Yes, through the Samsung Health Sensor SDK in a Wear OS app on Galaxy Watch4 or later. It gives raw ECG at 500 Hz, raw PPG and heart rate with inter-beat intervals, which Samsung says can be used to calculate HRV. It needs its own partner request, does not share data with Samsung Health, and is for wellness only.

Can I tell which device recorded a Samsung Health reading?

Yes. Every data point carries a source device id. DeviceManager returns the device group, such as watch or accessory, the manufacturer, the model and the name the user gave it. You can also filter reads to watch data or to the phone itself.
Share