Stream Slopes data. Straight from the phone.
Slopes reads and writes Health data — each tracked ski or snowboard session crosses to Apple Health as a workout with its GPS route, distance, calories, and uphill segments — and Sahha’s SDK reads it into your app as a normalized exercise session, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Snow sports session
- 164 min
- Distance
- 31.4 km
- Active energy
- 1,120 kcal
Identical schema across 500+ sources
Your users connect Slopes. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Slopes 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
Slopes 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 — Slopes today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Slopes 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
Slopes, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
The session as a workout, with its route distance and active energy pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
3
HealthKitSahha- workoutActivityTypeexercise_session_*min
- totalDistancedistance_walkingkm
- activeEnergyBurnedactive_energy_burnedkcal
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeSnowSports",
"duration": 9840,
"totalDistance": { "value": 31400, "unit": "m" },
"totalEnergyBurned": { "value": 1120, "unit": "kcal" },
"startDate": "2026-02-14T09:05:00Z",
"endDate": "2026-02-14T11:49:00Z",
"sourceRevision": { "source": { "name": "Slopes" } }
}[
{
"category": "activity",
"type": "exercise_session_skiing",
"value": 164,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-02-14T09:05:00Z",
"endDateTime": "2026-02-14T11:49:00Z"
},
{
"category": "activity",
"type": "distance_walking",
"value": 31.4,
"unit": "km",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-02-14T09:05:00Z",
"endDateTime": "2026-02-14T11:49:00Z"
}
// …1 more normalized log
]Slopes writes the session as a workout with its route, distance, calories, and uphill or skinning segments. The descent distance arrives on the platform’s distance type, so it normalizes to distance_walking — the field name reads as walking, the value is the distance Slopes recorded. Slopes also ships an Android app that lists Health Connect, but the write direction there isn’t confirmed, so this page covers the Apple Health path only.
Missing a metric you need? Talk to us in the Sahha Slack — if Slopes 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 Slopes developer account needed — Sahha reads what Slopes 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 Slopes 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 Slopes data the same day they add the SDK. The only per-source prerequisite: your user has Slopes’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.
Slopes integration questions
How does Sahha get Slopes data?
Slopes writes each tracked session to Apple Health, and Sahha reads it from there with its mobile SDK, delivering it as a normalized exercise session — no Slopes API to integrate.
Which Slopes metrics does Sahha provide?
The session itself — activity type and duration — plus the distance covered and the active energy burned. Uphill and skinning segments are part of what Slopes writes into the workout, so touring days come through as activity rather than being dropped.
Why does ski distance arrive as distance_walking?
Apple Health carries one general distance type for most workouts, and Slopes writes the session’s distance onto it. Sahha normalizes that to distance_walking — the same field every other distance source lands on — so the label reads as walking while the value is the distance Slopes recorded for the day.
Does the Slopes integration work on Android?
Not confirmed. Slopes ships an Android app that lists Health Connect, but we haven’t verified that it writes sessions there rather than only reading — so this page is scoped to Apple Health on iOS rather than claiming a path we can’t stand behind. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Slopes integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Slopes 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 Slopes data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Slopes and every other source.
Free for 30 days · No credit card
- One API for Slopes 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