Ski software · 13 min read

Why wearable data reaches Apple Health in different ways

Apple Health does not mirror every connected service in full. A visible workout or an enabled connection does not prove that a route, detailed heart-rate data, sleep, HRV, or steps came across. Choose the data type first, then check each handoff.

Mechanical data station where a route card falls into a rejection tray before the shared archive while four other data types reach the receiver
On this page

Ask a narrower question than “Is Garmin, COROS, Strava, Oura, or WHOOP connected?”: “Does Apple Health contain the exact data type my next app needs?” A service may send a workout without its route. It may supply daily heart-rate values without a full activity trace. Import and export may also follow different rules.

Treat each category as its own package. Check workouts, routes, heart rate, active energy, sleep, HRV, and steps separately. You can then see whether the device never captured the measurement, the provider kept it, Apple Health received it, or the destination app lacks permission to read it.

Four handoffs determine what your destination app can see

A connection is more than one switch. The record has to pass through four separate stages, and its detail can change at any of them.

  1. Capture

    A watch, ring, or recorder creates a measurement or workout record.

    Check the original view: did it capture the category you need?
  2. Export

    The provider app chooses which categories and details it writes to Apple Health.

    Check the current official export list and write permissions.
  3. Store

    Apple Health keeps workouts, routes, heart rate, sleep, and other values as separate data types with their own sources.

    Open the specific category and check its source and time.
  4. Read

    Your destination app requests only the categories it supports and you have allowed it to access.

    Check the destination app's read permission for that exact data type.

Choose the data type before you compare providers

A brand name alone says little. Write down the outcome you expect first. These questions keep you from mistaking a visible workout for a complete data transfer.

Workout

Are the activity type, start time, and duration present?

Route

Does the workout have a GPS route, or does the map remain only in the recorder app?

Heart rate

Are there individual samples during the workout, or only daily values, a minimum, and a maximum?

Sleep

Did the service transfer only the start and end times, or sleep stages too?

HRV

Did the service export the measurement as an Apple Health category, or does it show only a proprietary score?

Steps and energy

Which source writes overlapping values, and what priority does it have?

What providers currently document

This table is not a permanent compatibility guarantee. It shows the documented path and the limit that matters most for a destination app. Open the linked provider help before relying on a data type.

What providers currently document

Service Direction Documented coverage Key limit and your check
Garmin Garmin Connect → Apple Health Workouts and selected activity, body, and health categories. Garmin's current help says it does not write the workout GPS track to Apple Health. For timed activities, Health receives only high and low heart-rate values rather than a complete chart. Open the workout, route, and heart rate separately. Let Garmin Connect update in the foreground after the device syncs.
COROS COROS → Apple Health Currently listed: cycling distance, heart rate, sleep analysis, steps, swimming distance, and walking and running distance. The current official list does not automatically include workouts, routes, or HRV. A visible COROS recording therefore does not prove that Apple Health has a matching entry. Compare the category you need with the current list, then check it directly in Apple Health.
Strava Strava ↔ Apple Health, with different rules in each direction From Strava to Health: route, activity type, distance, time, and calories. Health-to-Strava imports follow narrower rules. Routes from third-party activities, such as Garmin or Zwift, do not pass through Strava to Health. Workouts another app wrote to Health do not import into Strava like native Apple workouts. Record who originally captured the activity. Do not inspect only the last app in the chain.
Oura Oura ↔ Apple Health with different category sets For export, Oura documents workouts and routes, active energy, heart rate at one-minute intervals, sleep, steps, and weight, among other categories. Its import set differs. Oura scores and app charts are not automatically Apple Health categories. Rounding and display intervals can make charts differ, while overlapping steps depend on source priority. Check the individual category and its source instead of expecting an Oura score in a destination app.
WHOOP WHOOP ↔ Apple Health, depending on current settings WHOOP provides an official Apple Health integration. Check the exact coverage in the current WHOOP help and your Apple Health switches. On the review date, the public help page did not reliably expose its current category list. We therefore do not reproduce a list from third-party sources that may be out of date. Open the current official integration guidance and compare the enabled read and write categories with your goal.

Garmin

Direction
Garmin Connect → Apple Health
Documented coverage
Workouts and selected activity, body, and health categories.
Key limit and your check
Garmin's current help says it does not write the workout GPS track to Apple Health. For timed activities, Health receives only high and low heart-rate values rather than a complete chart. Open the workout, route, and heart rate separately. Let Garmin Connect update in the foreground after the device syncs.

COROS

Direction
COROS → Apple Health
Documented coverage
Currently listed: cycling distance, heart rate, sleep analysis, steps, swimming distance, and walking and running distance.
Key limit and your check
The current official list does not automatically include workouts, routes, or HRV. A visible COROS recording therefore does not prove that Apple Health has a matching entry. Compare the category you need with the current list, then check it directly in Apple Health.

Strava

Direction
Strava ↔ Apple Health, with different rules in each direction
Documented coverage
From Strava to Health: route, activity type, distance, time, and calories. Health-to-Strava imports follow narrower rules.
Key limit and your check
Routes from third-party activities, such as Garmin or Zwift, do not pass through Strava to Health. Workouts another app wrote to Health do not import into Strava like native Apple workouts. Record who originally captured the activity. Do not inspect only the last app in the chain.

Oura

Direction
Oura ↔ Apple Health with different category sets
Documented coverage
For export, Oura documents workouts and routes, active energy, heart rate at one-minute intervals, sleep, steps, and weight, among other categories. Its import set differs.
Key limit and your check
Oura scores and app charts are not automatically Apple Health categories. Rounding and display intervals can make charts differ, while overlapping steps depend on source priority. Check the individual category and its source instead of expecting an Oura score in a destination app.

WHOOP

Direction
WHOOP ↔ Apple Health, depending on current settings
Documented coverage
WHOOP provides an official Apple Health integration. Check the exact coverage in the current WHOOP help and your Apple Health switches.
Key limit and your check
On the review date, the public help page did not reliably expose its current category list. We therefore do not reproduce a list from third-party sources that may be out of date. Open the current official integration guidance and compare the enabled read and write categories with your goal.

Create your transfer manifest in six steps

Use a short test workout or a recent ordinary night. Check one data path and one category at a time. You can reuse the result when you contact support or choose a destination app.

  1. Set the goal

    Write one sentence: “I need the GPS route from this workout in Apple Health” or “I need sleep duration and sleep stages”.

  2. Keep the original

    Record the device, recorder app, time, and version. Check whether the expected value appears in the original app.

  3. Check the export promise

    Open the provider's current official help. Search for the specific category, not only for “Apple Health”.

  4. Inspect Apple Health

    Open the category, find the matching time, and check who wrote the entry under “Data Sources & Access”.

  5. Check details separately

    Open the workout, route, heart rate, sleep, HRV, or steps one by one. A workout card does not prove that every detail is present.

  6. Check the destination app

    Check its read permission and refresh it once with the documented method. Record the first handoff where the category disappears.

What your result means, and what it does not

An observation narrows down the data path, but it does not automatically explain the technical cause or your physical condition.

What your result means, and what it does not

Observation Next check Do not infer
The value is missing in the original app Measurement, device connection, and recorder settings Apple Health deleted the value
The original has it, but Apple Health does not Export list, write permission, and the provider's latest sync The destination app caused the issue
Health has it, but the destination app shows nothing Source, time, read permission, and the destination app's supported category The value is zero or physiologically unremarkable
Values are duplicated or differ Data sources, priority, and the definitions used by the apps involved One source is inherently more accurate

The value is missing in the original app

Next check
Measurement, device connection, and recorder settings
Do not infer
Apple Health deleted the value

The original has it, but Apple Health does not

Next check
Export list, write permission, and the provider's latest sync
Do not infer
The destination app caused the issue

Health has it, but the destination app shows nothing

Next check
Source, time, read permission, and the destination app's supported category
Do not infer
The value is zero or physiologically unremarkable

Values are duplicated or differ

Next check
Data sources, priority, and the definitions used by the apps involved
Do not infer
One source is inherently more accurate

Continue from the right point

Where SlopeReady sits in this data path

SlopeReady is a destination app after recording. With your permission, it reads the available training and recovery data from Apple Health. You do not sign in directly to Garmin, COROS, Strava, Oura, or WHOOP.

SlopeReady does not record workouts, GPS routes, or live heart rate, and it does not write to Apple Health. If a category is missing there or arrived with limited detail, the app does not reconstruct it. The AI coach can place the available data alongside your plan, but it must treat missing information as missing.

We verified product behavior on August 13, 2026 against the read-only HealthKit data path and current SlopeReady documentation. Data and privacy, Support and product boundaries

Did the data you need reach Apple Health?

With your permission, SlopeReady reads the training and recovery data available in Apple Health and places it in your preparation plan. The app does not connect directly to Garmin, COROS, Strava, Oura, or WHOOP, and it does not invent missing values.

Explore SlopeReady as a preparation app

Providers can change their supported categories, menus, and sync rules. We checked these details against current official documentation on August 13, 2026. Before an important trip, check the current help for the service you use and run a short test through your exact device and app path.