Stream EMAY data. No EMAY API needed.
EMAY makes budget portable ECG and pulse-oximeter devices, and its apps write heart rate and oxygen saturation to Apple Health — Sahha’s SDK reads them into your app as normalized vitals biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Heart rate
- 68 bpm
- Oxygen saturation
- 97 %
Identical schema across 500+ sources
Your users connect EMAY. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every EMAY signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.
A Allow "your app"
On-device and permissioned
EMAY data is read on the user’s own device, only after they grant Apple Health permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health — EMAY today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What EMAY syncs through Apple Health.
Request only what you need
You choose exactly which of these signals to request from Apple Health — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
EMAY, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Heart rate and oxygen saturation pass through Apple Health; some app-exclusive metrics may not.
Heart & vitals
2
HealthKitSahha- heartRateheart_ratebpm
- oxygenSaturationoxygen_saturation%
See a real payload
{
"type": "HKQuantityTypeIdentifierHeartRate",
"value": 68,
"unit": "count/min",
"startDate": "2026-06-03T09:02:00Z",
"endDate": "2026-06-03T09:02:30Z",
"sourceRevision": { "source": { "name": "EMAY" } }
// …SpO₂ sample from the pulse-oximeter app
}[
{
"category": "vitals",
"type": "heart_rate",
"value": 68,
"unit": "bpm",
"periodicity": "manual",
"aggregation": "none",
"startDateTime": "2026-06-03T09:02:00Z",
"endDateTime": "2026-06-03T09:02:30Z"
}
// …1 more normalized log
]The two-app split matters. EMAY’s portable ECG app writes heart rate only — the ECG waveform itself stays in the app and its PDF export, and never reaches Apple Health, so Sahha never sees a trace. EMAY’s separate pulse-oximeter app writes oxygen saturation and heart rate. A user with only one device gets only that device’s signals. All of it is spot readings taken by the user, so cadence follows their measurements.
Missing a metric you need? Talk to us in the Sahha Slack — if EMAY captures it, we can usually add support.
Get more than just raw data
Sahha turns these signals into biomarkers, scores, archetypes, and insights — the modeling done for you.
Reading Apple Health yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain on iOS. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Handle iOS version differences.
- Add Health Connect separately for Android.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Request the right permissions.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of HealthKit types.
- Reconcile against your Android sources.
Deduped, typed, one schema — one stream per user.
- Build a sleep model.
- Build an activity model.
- Hire a data scientist.
Scores, archetypes, and insights — built in.
- Apple changes a HealthKit API.
- You find out in production.
We version the SDK. You never notice.
No EMAY developer account needed — Sahha reads what EMAY already writes to Apple Health on iOS.
Live in an afternoon, not a sprint.
- # Add the Sahha SDKnpm install sahha-react-native01
Add the Sahha SDK
Drop the Sahha SDK into your iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for Apple Health permissions
Call the SDK to show the native Apple Health consent sheet. The user chooses what to share — under your brand. It’s one prompt, ever: permission is per data type, not per brand, so every future source is already covered.
- Your app LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads EMAY data from Apple Health in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live EMAY data the same day they add the SDK. The only per-source prerequisite: your user has EMAY’s Apple Health sync switched on — most source apps enable it by default.
Route it into your stack.
Sahha streams every update to your webhook — and a step-by-step guide takes it the rest of the way into your database, CDP, or messaging tool.
EMAY integration questions
How does Sahha get EMAY data?
EMAY’s apps write their readings to Apple Health, and Sahha reads them from there with its mobile SDK — no EMAY API to integrate.
Which EMAY app writes what?
There are two, and the split is the important part. The portable ECG app writes heart rate only. The separate pulse-oximeter app writes oxygen saturation and heart rate. A user who owns just the ECG device will only ever produce heart rate.
Does the ECG trace itself come through?
No. The ECG waveform stays inside EMAY’s app and its PDF export — only the heart rate derived from the recording is written to Apple Health. If you need the trace, the user has to share the PDF out of the app; Sahha won’t have it.
Does the EMAY integration work on Android?
Not today. The verified write path is Apple Health, so this is an iOS-only integration and the page claims nothing more. Your users’ other Android sources still flow through the same Sahha SDK.
Is the EMAY integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and EMAY data flows through the same compliant pipeline as every other source.
One API for every other source, too.
Add another wearable or app and the schema, webhooks, and scores are identical — no new pipeline to build.
Start streaming EMAY data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for EMAY and every other source.
Free for 30 days · No credit card
- One API for EMAY and every other source
- Real-time webhooks + on-demand REST, one normalized schema
- Scores, archetypes & insights — no modeling required
- HIPAA, GDPR & SOC 2 · your brand on the consent screen