Stream Swim.com data. Straight from the phone.
Swim.com exports your activities into the Health app — each swim as a workout with its distance and calories — and Sahha’s SDK reads them into your app as normalized exercise sessions, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Swim session
- 42 min
- Distance
- 1,800 m
- Active energy
- 486 kcal
Identical schema across 500+ sources
Your users connect Swim.com. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Swim.com 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
Swim.com 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 — Swim.com today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Swim.com 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
Swim.com, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
The swim as a workout, with its distance and active energy pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
3
HealthKitSahha- workoutActivityTypeexercise_session_*min
- totalDistancedistance_walkingm
- activeEnergyBurnedactive_energy_burnedkcal
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeSwimming",
"duration": 2520,
"totalDistance": { "value": 1800, "unit": "m" },
"totalEnergyBurned": { "value": 486, "unit": "kcal" },
"startDate": "2026-03-09T06:30:00Z",
"endDate": "2026-03-09T07:12:00Z",
"sourceRevision": { "source": { "name": "Swim.com" } }
}[
{
"category": "activity",
"type": "exercise_session_swimming",
"value": 42,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-03-09T06:30:00Z",
"endDateTime": "2026-03-09T07:12:00Z"
},
{
"category": "activity",
"type": "distance_walking",
"value": 1800,
"unit": "m",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-03-09T06:30:00Z",
"endDateTime": "2026-03-09T07:12: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. Worth knowing where Swim.com sits: it’s largely a destination for workouts recorded on a swim watch, and where that watch also writes to Apple Health directly, the same swim can arrive twice. Sahha deduplicates overlapping records so you count the session once.
Missing a metric you need? Talk to us in the Sahha Slack — if Swim.com 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 Swim.com developer account needed — Sahha reads what Swim.com 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 Swim.com 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 Swim.com data the same day they add the SDK. The only per-source prerequisite: your user has Swim.com’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.
Swim.com integration questions
How does Sahha get Swim.com data?
Swim.com exports your activities into the Health app, and Sahha reads them from there with its mobile SDK, delivering them as normalized exercise sessions — no Swim.com API to integrate.
Which Swim.com metrics does Sahha provide?
The swim as a workout — activity type and duration — plus the distance covered and the active energy burned. Swim distance lands on Apple Health’s general distance type, so it normalizes to distance_walking with the metres Swim.com recorded.
Will the same swim show up twice?
It can. Swim.com is largely a logbook for workouts recorded on a swim watch, and many of those watches write to Apple Health themselves — so one swim can arrive from both. Sahha deduplicates overlapping records, so the session counts once toward scores and archetypes.
Does the Swim.com integration work on Android?
This page covers the Apple Health export path only, so it’s scoped to iOS. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Swim.com integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Swim.com 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 Swim.com data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Swim.com and every other source.
Free for 30 days · No credit card
- One API for Swim.com 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