Provider Support

Overview

Open Wearables supports multiple wearable providers through two integration methods:

Cloud-based (OAuth): Connect via provider APIs with automatic cloud syncing
SDK-based: Direct device integration using platform SDKs (iOS HealthKit, Android Health Connect)

New providers are added regularly. Check the roadmap for upcoming integrations.

Provider Categories

Cloud-Based Providers (OAuth)

These providers use OAuth for authentication and sync data from their cloud APIs:

Garmin

Status: ✅ SupportedAuth: OAuth 1.0aData Types:

Workouts & Activities
Heart Rate (24/7)
Sleep Sessions
Body Metrics
Steps & Calories

Special Features:

30-day automatic backfill
Activity summaries
Advanced running metrics

Polar

Status: ✅ SupportedAuth: OAuth 2.0 + PKCEData Types:

Workouts
Heart Rate
Sleep Analysis
Training Load

Special Features:

Training zones
Recovery metrics
Polar Flow integration

Suunto

Status: ✅ SupportedAuth: OAuth 2.0Data Types:

Workouts
Activities
Route data

Special Features:

Requires subscription key
Outdoor activity focus
GPS tracks

Strava

Status: ✅ SupportedAuth: OAuth 2.0 + PKCEData Types:

Activities (running, cycling)
Workout summaries
Athlete profile

Special Features:

Segment data
Social features
Route mapping

Whoop

Status: ✅ SupportedAuth: OAuth 2.0Data Types:

Workouts
Recovery scores
Sleep performance
Strain tracking

Special Features:

Recovery optimization
Strain coach
Sleep insights

Oura

Status: 🚧 Coming SoonAuth: OAuth 2.0Planned Data:

Sleep stages
Readiness scores
Activity metrics
Heart rate variability

SDK-Based Providers

These providers integrate via platform SDKs for direct device access:

Apple Health

Status: ✅ Supported (XML import)Integration: HealthKit SDKData Types:

All HealthKit data types
Workouts
Heart Rate
Sleep Analysis
Body Measurements
Steps, Flights, Distance

Sync Methods:

XML export upload
Background webhooks (coming soon)

Samsung Health

Status: 🔄 PlannedIntegration: Samsung Health SDKPlanned Data:

Workouts
Steps & Activity
Heart Rate
Sleep

Google Fit

Status: 🔄 PlannedIntegration: Google Fit API / Health ConnectPlanned Data:

Activities
Steps & Movement
Heart Rate
Sleep

Provider Comparison Matrix

Provider	Auth Type	Workouts	Heart Rate	Sleep	Steps	Body	Special
Garmin	OAuth 1.0a	✅	✅ 24/7	✅	✅	✅	Backfill
Polar	OAuth 2.0	✅	✅	✅	✅	❌	Training zones
Suunto	OAuth 2.0	✅	✅	❌	❌	❌	GPS routes
Strava	OAuth 2.0	✅	✅	❌	❌	❌	Segments
Whoop	OAuth 2.0	✅	✅	✅	❌	❌	Recovery
Apple	SDK	✅	✅	✅	✅	✅	All HealthKit

Provider-Specific Details

Garmin

Overview
OAuth Setup
Data Sync
Data Mapping

Garmin offers comprehensive health and fitness data through their Connect API.Device Compatibility:

Forerunner series
Fenix series
Vivoactive series
Venu series
All Garmin smartwatches

Implementation:

# backend/app/services/providers/garmin/strategy.py
class GarminStrategy(BaseProviderStrategy):
    @property
    def name(self) -> str:
        return "garmin"
    
    @property
    def api_base_url(self) -> str:
        return "https://apis.garmin.com"

Credentials Required:

GARMIN_CLIENT_ID=your-client-id
GARMIN_CLIENT_SECRET=your-client-secret
GARMIN_REDIRECT_URI=http://localhost:8000/api/v1/oauth/garmin/callback

OAuth Flow:

OAuth 1.0a (3-legged)
User authorizes on Garmin Connect
Automatic 30-day backfill triggered
Ongoing sync every 15 minutes

Scopes:

Activities (read)
Body composition (read)
Sleep (read)

Initial Sync:

Automatically fetches last 30 days on connection
Background Celery task handles backfill

# Special backfill task for Garmin
if provider == ProviderName.GARMIN:
    start_garmin_full_backfill.delay(str(oauth_state.user_id))

Ongoing Sync:

Every 15 minutes via scheduled task
Manual sync available via API

Rate Limits:

120 requests per minute
120,000 requests per day

Workout Types:

GARMIN_WORKOUT_MAPPING = {
    "running": "running",
    "cycling": "cycling",
    "swimming": "swimming",
    "strength_training": "strength_training",
    # ... more mappings
}

Activity Summary:

Distance, duration, calories
Average/max heart rate
Elevation gain
Training effect
VO2 max (if available)

Polar

Overview
OAuth Setup
Data Types
API Endpoints

Polar provides training and recovery metrics via their AccessLink API.Device Compatibility:

Polar Vantage series
Polar Grit X series
Polar Ignite series
Polar H10 heart rate sensor

Implementation:

# backend/app/services/providers/polar/strategy.py
class PolarStrategy(BaseProviderStrategy):
    @property
    def name(self) -> str:
        return "polar"
    
    @property
    def api_base_url(self) -> str:
        return "https://www.polaraccesslink.com"

Credentials Required:

POLAR_CLIENT_ID=your-client-id
POLAR_CLIENT_SECRET=your-client-secret
POLAR_REDIRECT_URI=http://localhost:8000/api/v1/oauth/polar/callback

PKCE Support:

Enhanced security with PKCE
Code challenge method: S256

User Registration:

Must register user with Polar first
Returns x_user_id in token response

class OAuthTokenResponse(BaseModel):
    access_token: str
    token_type: str
    refresh_token: str | None = None
    expires_in: int
    x_user_id: int | None = None  # Polar-specific

Available endpoints:

# Training data
GET /v3/exercises

# Physical info
GET /v3/users/{user-id}/physical-information

# Activity summary
GET /v3/users/{user-id}/activity-transactions

# Sleep data
GET /v3/users/{user-id}/sleep

Suunto

Overview
OAuth Setup
Data Types

Suunto focuses on outdoor activities and adventure sports.Device Compatibility:

Suunto 9 series
Suunto 7
Suunto 5
Suunto 3 Fitness

Special Requirements:

Subscription key needed
Configure in environment:

SUUNTO_SUBSCRIPTION_KEY=your-subscription-key

Credentials:

SUUNTO_CLIENT_ID=your-client-id
SUUNTO_CLIENT_SECRET=your-client-secret
SUUNTO_REDIRECT_URI=http://localhost:8000/api/v1/oauth/suunto/callback
SUUNTO_SUBSCRIPTION_KEY=your-subscription-key

Headers:

headers = {
    "Authorization": f"Bearer {access_token}",
    "Ocp-Apim-Subscription-Key": subscription_key
}

Strava

Overview
OAuth Setup
Data Types

Strava is a social fitness platform focused on running and cycling.Use Case:

Athletes who log activities manually
Users with multiple device sources
Social sharing and competition

Implementation:

class StravaStrategy(BaseProviderStrategy):
    @property
    def name(self) -> str:
        return "strava"
    
    @property
    def api_base_url(self) -> str:
        return "https://www.strava.com/api/v3"

Credentials:

STRAVA_CLIENT_ID=your-client-id
STRAVA_CLIENT_SECRET=your-client-secret
STRAVA_REDIRECT_URI=http://localhost:8000/api/v1/oauth/strava/callback

PKCE: Supported for enhanced securityScopes:

activity:read_all
profile:read_all

Whoop

Overview
OAuth Setup
Data Types

Whoop specializes in recovery and strain optimization.Unique Features:

Recovery score (0-100%)
Strain score (0-21)
Sleep performance
HRV tracking

Implementation:

class WhoopStrategy(BaseProviderStrategy):
    @property
    def name(self) -> str:
        return "whoop"
    
    @property
    def api_base_url(self) -> str:
        return "https://api.prod.whoop.com"

Credentials:

WHOOP_CLIENT_ID=your-client-id
WHOOP_CLIENT_SECRET=your-client-secret
WHOOP_REDIRECT_URI=http://localhost:8000/api/v1/oauth/whoop/callback

Read-Only Access:

All Whoop integrations are read-only
Cannot write data back to Whoop

Apple Health

Overview
Data Export
Supported Data Types
Future SDK Integration

Apple Health aggregates data from iPhone, Apple Watch, and third-party apps.Integration Method:

XML export upload (currently)
SDK with background sync (coming soon)

Device Sources:

Apple Watch (all models)
iPhone (motion sensors)
Third-party apps syncing to HealthKit

Manual Export:

Open Health app on iPhone
Tap profile icon (top right)
Tap “Export All Health Data”
Save export.zip
Upload to Open Wearables

API Upload:

curl -X POST http://localhost:8000/api/v1/users/{user_id}/health/apple/import \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "[email protected]"

From export.xml:

Workouts (all types)
Heart Rate
Steps and Flights Climbed
Active Energy / Resting Energy
Distance Walking/Running
Exercise Minutes
Sleep Analysis
Body Mass (Weight)
Body Fat Percentage
Height
And 70+ other HealthKit types

Mapping:

HEALTHKIT_TYPE_MAPPING = {
    "HKQuantityTypeIdentifierHeartRate": "heart_rate",
    "HKQuantityTypeIdentifierStepCount": "steps",
    "HKCategoryTypeIdentifierSleepAnalysis": "sleep",
    # ... comprehensive mapping
}

Planned Features:

Real-time background sync
HealthKit permissions UI
Automatic data updates
Flutter SDK for cross-platform

Architecture:

Mobile App (Flutter)
  ↓
HealthKit / Health Connect
  ↓
Background Sync Service
  ↓
Open Wearables API

Enabling/Disabling Providers

Configure which providers are available to your users:

Via Developer Portal

Navigate to Settings → Providers
Toggle providers on/off
Click Save Changes

Via API

# Bulk update
PUT /api/v1/oauth/providers
Content-Type: application/json

{
  "providers": {
    "garmin": true,
    "polar": true,
    "suunto": false,
    "strava": true,
    "whoop": false
  }
}

Provider Settings:

# backend/app/schemas/provider_setting.py
class ProviderSettingRead(BaseModel):
    provider: str
    display_name: str
    icon_url: str
    has_cloud_api: bool
    is_enabled: bool

Provider Icons

Provider icons are located at:

backend/app/static/provider-icons/
├── garmin.svg
├── polar.svg
├── suunto.svg
├── strava.svg
├── whoop.svg
├── apple.svg
└── ...

Access via:

GET /static/provider-icons/{provider}.svg

Adding New Providers

Want to add support for a new provider? See our comprehensive guide:

How to Add a New Provider

Step-by-step instructions for implementing new wearable integrations

Provider Priority

When multiple providers supply the same data point (e.g., both Garmin and Apple Watch recording heart rate), you can configure priority:

Set Priority Order

Go to Settings → Priorities
Drag providers to reorder
Higher position = higher priority
Save changes

How it works:

For overlapping time ranges, higher priority source wins
Non-overlapping data from all sources is retained
Priority applies per metric type

Next Steps

OAuth Flow

Learn how to connect users to providers

Unified API

Access normalized health data programmatically

Getting Started

Core Features

Guides

Deployment

Development

Overview

Provider Categories

Cloud-Based Providers (OAuth)

Garmin

Polar

Suunto

Strava

Whoop

Oura

SDK-Based Providers

Apple Health

Samsung Health

Google Fit

Provider Comparison Matrix

Provider-Specific Details

Garmin

Polar

Suunto

Strava

Whoop

Apple Health

Enabling/Disabling Providers

Via Developer Portal

Via API

Provider Icons

Adding New Providers

How to Add a New Provider

Provider Priority

Set Priority Order

Next Steps

OAuth Flow

Unified API

Build docs developers (and LLMs) love

Getting Started

Core Features

Guides

Deployment

Development

​Overview

​Provider Categories

​Cloud-Based Providers (OAuth)

Garmin

Polar

Suunto

Strava

Whoop

Oura

​SDK-Based Providers

Apple Health

Samsung Health

Google Fit

​Provider Comparison Matrix

​Provider-Specific Details

​Garmin

​Polar

​Suunto

​Strava

​Whoop

​Apple Health

​Enabling/Disabling Providers

​Via Developer Portal

​Via API

​Provider Icons

​Adding New Providers

How to Add a New Provider

​Provider Priority

​Set Priority Order

​Next Steps

OAuth Flow

Unified API

Build docs developers (and LLMs) love

Overview

Provider Categories

Cloud-Based Providers (OAuth)

SDK-Based Providers

Provider Comparison Matrix

Provider-Specific Details

Garmin

Polar

Suunto

Strava

Whoop

Apple Health

Enabling/Disabling Providers

Via Developer Portal

Via API

Provider Icons

Adding New Providers

Provider Priority

Set Priority Order

Next Steps