Connection directory · updated August 22, 2026

Bring the data you already use.

Wearables tell you what changed. EnduraX helps the athlete and the right people decide what to do next.

Create account →See how the data is read

Every connection, without the fine-print hunt.

No wearable is required. Connected data can add context, but it never becomes an automatic decision or a substitute for what the athlete reports.

ŌURA

Connected

Data brought in: HRV, resting heart rate, sleep, SpO₂, and supported recovery context.
Direction: Oura → EnduraX
Current limit: Availability depends on the data Oura exposes for the connected account and day.

Athlete authorizes the connection and can disconnect it.

Connected

Data brought in: Recovery, HRV, resting heart rate, sleep, strain, and supported workout context.
Direction: WHOOP → EnduraX
Current limit: EnduraX reads supported context; it does not replace WHOOP’s own interpretation.

Athlete authorizes the connection and can disconnect it.

Connected

Data brought in: Supported training activities and activity context.
Direction: Strava → EnduraX
Current limit: Activity availability and fields depend on Strava and the athlete’s permissions.

Athlete authorizes the connection and can disconnect it.

WITHINGSConnected

Data brought in: Supported weight and body-composition measurements imported into the athlete profile.
Direction: Withings → EnduraX
Current limit: Latest supported readings can update profile fields used by fueling and readiness calculations; this sensitive connection is optional.

Athlete opts in separately and can disconnect it.

Apple Health

In certification

Data brought in: In the iOS app: selected sleep, resting heart rate, HRV-SDNN, workout, active-energy, and distance context. A separate Shortcut bridge can bring supported nutrition data.
Direction: Apple Health → EnduraX iOS app; optional nutrition Shortcut → EnduraX
Current limit: Native reads are iPhone-only, read-only, foreground-only, and limited to data the athlete shares. Raw samples stay on device.

After physical-device certification, the athlete will choose each Apple Health permission and can change access in iOS Settings or Health.

Institutional systemsInstitution-scoped

Data brought in: Roster, calendar, training-plan, and other agreed program context.
Direction: Defined during evaluation
Current limit: No universal institutional connector is promised; scope depends on the system and pilot.

Data flow, access, and retention are documented with the institution before activation.

Connection does not mean disclosure.

An athlete can connect a provider to improve their own read without automatically sharing every raw value with a coach, provider, or institution.

Authorize

The athlete starts the provider connection.

Use

EnduraX reads only the supported data needed for the enabled product paths.

Share separately

Relationship permissions decide what another person can see.

Disconnect

The athlete can remove the connection without leaving EnduraX.

Review the full data flow →

Evaluating a team connection?

Institutional data flows are scoped before activation. Bring the current system, intended purpose, roles, and retention needs to the first conversation.

Start a data-practices conversation →Open the evaluation guide