Stream Redpoint data. Straight from the phone.
Redpoint is a bouldering and climbing session logger with a watchOS app, and it’s explicit about where sessions land: “Workouts are stored in HealthKit and therefore visible in the Health app.” 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
- Climbing session
- 76 min
- Active energy
- 498 kcal
- Heart rate
- 124 bpm
Identical schema across 500+ sources
Your users connect Redpoint. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Redpoint 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
Redpoint 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 — Redpoint today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Redpoint 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
Redpoint, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Climbing workouts, active energy, and heart rate pass through Apple Health; some app-exclusive metrics may not.
Activity & exercise
2
HealthKitSahha- workoutActivityTypeexercise_session_*min
- activeEnergyBurnedactive_energy_burnedkcal
Heart & vitals
1
HealthKitSahha- heartRateheart_ratebpm
See a real payload
{
"type": "HKWorkoutTypeIdentifier",
"workoutActivityType": "HKWorkoutActivityTypeClimbing",
"duration": 4560,
"totalEnergyBurned": { "value": 498, "unit": "kcal" },
"sourceRevision": { "source": { "name": "Redpoint" } }
}[
{
"category": "activity",
"type": "exercise_session_climbing",
"value": 76,
"unit": "minute",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T17:30:00Z",
"endDateTime": "2026-06-02T18:46:00Z"
},
{
"category": "activity",
"type": "active_energy_burned",
"value": 498,
"unit": "kcal",
"periodicity": "session",
"aggregation": "total",
"startDateTime": "2026-06-02T17:30:00Z",
"endDateTime": "2026-06-02T18:46:00Z"
}
]The climbing session crosses as a workout — grades, routes, and send logs stay in Redpoint, because Apple Health has no field for them. The physiological signals come from the watchOS app, so heart rate and active energy depend on the user wearing an Apple Watch for the session. This is an Apple-Health-only integration.
Missing a metric you need? Talk to us in the Sahha Slack — if Redpoint 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 Redpoint developer account needed — Sahha reads what Redpoint 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 Redpoint 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 Redpoint data the same day they add the SDK. The only per-source prerequisite: your user has Redpoint’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.
Redpoint integration questions
How does Sahha get Redpoint data?
Redpoint stores its workouts in HealthKit — its own words: “Workouts are stored in HealthKit and therefore visible in the Health app” — and Sahha reads them from there with its mobile SDK, so you get climbing sessions without integrating a Redpoint API directly.
What Redpoint data does Sahha receive?
The climbing session duration, active energy, and heart rate. They arrive as normalized exercise sessions and vitals, in the same fields and units as every other source.
Does Sahha get grades, routes, or send logs?
No. Grades, routes, and send logs stay in Redpoint — the session crosses as a workout and nothing finer. Note also that the physiological signals come from the watchOS app, so heart rate and active energy depend on the user wearing an Apple Watch while they climb.
Does the Redpoint integration work on Android?
No. Redpoint writes to HealthKit on iOS and watchOS, so this is an iOS-only integration and the page doesn’t claim otherwise. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Redpoint integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Redpoint 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 Redpoint data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Redpoint and every other source.
Free for 30 days · No credit card
- One API for Redpoint 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