Stream Phlex data. Straight from the phone.
Phlex syncs swim distance, swim time, and heart rate to Apple Health, and Sahha’s SDK reads them into your app as normalized exercise sessions and biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Swim session
- 55 min
- Distance
- 2,400 m
- Heart rate
- 132 bpm
Identical schema across 500+ sources
Your users connect Phlex. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Phlex 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
Phlex 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 — Phlex today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Phlex 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
Phlex, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Swim time, distance, and heart rate pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- workoutActivityTypeexercise_session_*min
- totalDistancedistance_walkingm
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeSwimming",
"duration": 3300,
"totalDistance": { "value": 2400, "unit": "m" },
"startDate": "2026-05-06T05:45:00Z",
"endDate": "2026-05-06T06:40:00Z",
"sourceRevision": { "source": { "name": "Phlex" } }
// …heart rate samples
}[
{
"category": "activity",
"type": "exercise_session_swimming",
"value": 55,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-05-06T05:45:00Z",
"endDateTime": "2026-05-06T06:40:00Z"
},
{
"category": "activity",
"type": "distance_walking",
"value": 2400,
"unit": "m",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-05-06T05:45:00Z",
"endDateTime": "2026-05-06T06:40:00Z"
}
// …1 more normalized log
]Swim distance arrives on the platform’s general distance type, so it normalizes to distance_walking — the field name reads as walking, the value is the metres swum. One thing to know about the source: the Phlex Edge hardware sensor has been discontinued, but the app lives on, and this integration is the app’s write path rather than the sensor’s. Stroke-level and set-level training detail stays in Phlex.
Missing a metric you need? Talk to us in the Sahha Slack — if Phlex 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 Phlex developer account needed — Sahha reads what Phlex 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 Phlex 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 Phlex data the same day they add the SDK. The only per-source prerequisite: your user has Phlex’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.
Phlex integration questions
How does Sahha get Phlex data?
Phlex syncs swims to Apple Health, and Sahha reads them from there with its mobile SDK, delivering them as normalized exercise sessions and biomarkers — no Phlex API to integrate.
Which Phlex metrics does Sahha provide?
Swim time as an exercise session, the distance covered, and heart rate. Swim distance lands on Apple Health’s general distance type, so it normalizes to distance_walking with the metres Phlex recorded.
Does the discontinued Phlex Edge sensor affect this?
The Edge hardware has been discontinued, but the Phlex app lives on and this integration is the app’s write path — so swims that reach the app still reach Apple Health. Stroke-level and set-level training detail stays inside Phlex.
Does the Phlex integration work on Android?
This page covers the Apple Health write path only, so it’s scoped to iOS. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Phlex integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Phlex 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 Phlex data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Phlex and every other source.
Free for 30 days · No credit card
- One API for Phlex 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