Stream Frontier X data. No Frontier X API needed.
Fourth Frontier’s Frontier X is a continuous-ECG chest strap for athletes, and its app lets users “export your Frontier X activities into the Health app” with the heart rate recorded alongside — Sahha’s SDK reads them into your app as normalized exercise and vitals biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Run session
- 46 min
- Heart rate
- 152 bpm
Identical schema across 500+ sources
Your users connect Frontier X. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Frontier X 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
Frontier X 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 — Frontier X today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Frontier X 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
Frontier X, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Completed activities and their heart rate pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
1
HealthKitSahha- workoutActivityTypeexercise_session_*min
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeRunning",
"duration": "2760 s",
"startDate": "2026-06-03T06:00:00Z",
"endDate": "2026-06-03T06:46:00Z",
"sourceRevision": { "source": { "name": "Frontier X" } }
// …associated heart rate samples
}[
{
"category": "activity",
"type": "exercise_session_running",
"value": 46,
"unit": "minute",
"startDateTime": "2026-06-03T06:00:00Z",
"endDateTime": "2026-06-03T06:46:00Z"
},
{
"category": "vitals",
"type": "heart_rate",
"value": 152,
"unit": "bpm",
"periodicity": "daily",
"aggregation": "avg",
"startDateTime": "2026-06-03T06:00:00Z",
"endDateTime": "2026-06-03T06:46:00Z"
}
]What crosses is the activity and the heart rate recorded during it. The continuous ECG trace the strap is built for does not cross, and neither do Frontier X’s proprietary strain and cardiac-risk metrics — those stay in its own app. Treat this as a workout-and-heart-rate source, not an ECG source.
Missing a metric you need? Talk to us in the Sahha Slack — if Frontier X 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 Frontier X developer account needed — Sahha reads what Frontier X 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 Frontier X 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 Frontier X data the same day they add the SDK. The only per-source prerequisite: your user has Frontier X’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.
Frontier X integration questions
How does Sahha get Frontier X data?
The Frontier X app exports completed activities into Apple Health, and Sahha reads them from there with its mobile SDK, delivering them as normalized exercise sessions and heart rate — no Frontier X API to integrate.
What Frontier X data does Sahha receive?
The completed activity — its type and duration — and the heart rate recorded during it. Both arrive in the same fields and units as every other source, so a Frontier X run and an Apple Watch run land in one schema.
Does the continuous ECG come through?
No. Frontier X records continuous ECG during training, but the trace stays in its own app — along with the proprietary strain and cardiac-risk metrics it derives. Only the activity and its heart rate reach Apple Health, so that’s what Sahha can give you.
Does the Frontier X integration work on Android?
Not today. The verified write path is the Apple Health export, 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 Frontier X integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Frontier X 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 Frontier X data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Frontier X and every other source.
Free for 30 days · No credit card
- One API for Frontier X 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