Nike Run Club Integration

Stream Nike Run Club data. No Nike API needed.

Nike Run Club writes each run to Apple Health and Health Connect — and Sahha’s SDK reads them into your app as normalized workouts, distance, calories, and heart rate, alongside every other source.

On-device
Apple Health + Health Connect
HIPAA
GDPR
SOC 2

Start building Read the SDK docs

Free for 30 days · No credit card

Normalized Auto-synced

Distance: 7.8 km
Active energy: 561 kcal
Avg heart rate: 156 bpm

Identical schema across 500+ sources

How it works

Your users connect Nike Run Club. Sahha does the rest.

This is your user’s side of the story — one screen, once. Sahha ingests every Nike Run Club signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.

Allow "your app"

Sleep

Activity

Heart rate

Connect

9:41LIVE

82READY

Sleep7h 12m

Steps5,993

Heart rate62 bpm

Your early-riser reward

20% off açaí bowls — today only.

Sahha

Permissions handled

Encrypted in transit

History backfilled

Background sync enabled

Cleaning · deduping · scoring

Raw data logs Biomarkers Scores Insights Archetypes Tags

Real-time webhooks

Always in sync

Query via API

Access controlled

Your service

Waiting for data…

On-device and permissioned

Nike Run Club data is read on the user’s own device, only after they grant Apple Health or Health Connect permission — nothing syncs without consent.

One integration, every source

Permission is per data type, not per brand. Anything that writes to Apple Health or Health Connect — Nike Run Club today, a new watch next year — flows through the same SDK with no extra prompt and no new code.

Data coverage

What Nike Run Club syncs through Apple Health & Health Connect.

Request only what you need
You choose exactly which of these signals to request from Apple Health / Health Connect — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Nike Run Club, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Workouts, distance, calories, and heart rate pass through the platform; some device-exclusive metrics may not.

Activity & exercise

HealthKit / Health ConnectSahha

workoutActivityTypeexercise_session_runningmin
distanceWalkingRunningdistance_walkingm
activeEnergyBurnedactive_energy_burnedkcal

Heart & vitals

HealthKit / Health ConnectSahha

heartRateheart_ratebpm

See a real payload

HealthKit · workout

{
  "type": "HKWorkoutTypeIdentifier",
  "workoutActivityType": "HKWorkoutActivityTypeRunning",
  "duration": 2520,
  "totalDistance": { "value": 7.8, "unit": "km" },
  "totalEnergyBurned": { "value": 561, "unit": "kcal" },
  "sourceRevision": { "source": { "name": "Nike Run Club" } }
  // …heart rate samples
}

Sahha · normalized

[
  {
    "category": "activity",
    "type": "exercise_session_running",
    "value": 42,
    "unit": "minute",
    "periodicity": "session",
    "aggregation": "total",
    "startDateTime": "2026-06-02T06:40:00Z",
    "endDateTime": "2026-06-02T07:22:00Z"
  },
  {
    "category": "activity",
    "type": "active_energy_burned",
    "value": 561,
    "unit": "kcal",
    "periodicity": "session",
    "aggregation": "total",
    "startDateTime": "2026-06-02T06:40:00Z",
    "endDateTime": "2026-06-02T07:22:00Z"
  }
  // …2 more normalized logs
]

Nike Run Club writes completed runs — active energy, heart rate, distance, and the workout — to Apple Health and Health Connect. Make sure the user grants the Workouts permission; without it, nothing syncs.

Missing a metric you need? Talk to us in the Sahha Slack — if Nike Run Club 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.

Biomarkers

Scores

Archetypes

Insights

Reading Apple Health and Health Connect yourself? Here’s the to-do list.

Everything on the left is yours to write, test, and maintain across two platforms. Everything on the right, Sahha already did.

Build it yourself

With Sahha

Every device

Build it yourself

Integrate Apple Health.
Then Health Connect, separately.
Then reconcile the two.

With Sahha

One SDK covers Apple Health, Health Connect, and every cloud source.

Getting the data

Build it yourself

Write the HealthKit queries.
Write the Health Connect queries.
Wire up background delivery.

With Sahha

The SDK handles queries, permissions, and background sync.

Keeping it clean

Build it yourself

Dedupe apps writing the same metric.
Map dozens of platform types.
Normalize iOS against Android.

With Sahha

Deduped, typed, one schema — one stream per user.

Turning it into insight

Build it yourself

Build a sleep model.
Build an activity model.
Hire a data scientist.

With Sahha

Scores, archetypes, and insights — built in.

Keeping it alive

Build it yourself

Apple or Google changes an API.
You find out in production.

With Sahha

We version the SDK. You never notice.

No Nike Run Club developer account needed — Sahha reads what Nike Run Club already writes to Apple Health and Health Connect.

Setup

Live in an afternoon, not a sprint.

# Add the Sahha SDKnpm install sahha-react-native
01
Add the Sahha SDK
Drop the Sahha SDK into your iOS or Android app — or React Native or Flutter. One dependency covers both Apple Health and Health Connect.
A
Allow “your app”
Sleep
Activity
Heart rate
Connect
02
Prompt for health permissions
Call the SDK to show the native Apple Health or Health Connect 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 LIVE
Sleep7h 12m
Readiness82
Heart rate62 bpm
03
Sahha reads and delivers
Once permission is granted, the SDK reads Nike Run Club data from Apple Health / Health Connect in the background, normalizes it to one schema, and streams it to your app by webhook or API.

Start building Read the SDK docs

Most teams read live Nike Run Club data the same day they add the SDK. The only per-source prerequisite: your user has Nike Run Club’s Apple Health / Health Connect sync switched on — most source apps enable it by default.

Destinations

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.

FAQ

Nike Run Club integration questions

How does Sahha get Nike Run Club data?

Nike Run Club writes your completed runs to Apple Health and Health Connect, and Sahha reads them from there with its mobile SDK — so you get NRC runs without integrating a Nike API directly.

Which Nike Run Club metrics does Sahha provide?

Workout type and duration, distance, active energy (calories), and heart rate during the run — normalized to Sahha’s schema and folded into the Activity score and archetypes. NRC doesn’t write sleep, body, or all-day metrics.

Why isn’t Nike Run Club data showing up?

Nike Run Club only writes to the platform when the user grants the Workouts permission in Apple Health or Health Connect — the most common cause of missing data is that permission being off or revoked.

Does it work on both iOS and Android?

Yes. The same Sahha SDK reads Apple Health on iOS and Health Connect on Android, and normalizes both to one schema.

Is the Nike Run Club integration HIPAA and GDPR compliant?

Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Nike Run Club data flows through the same compliant pipeline as every other source.