Strava API
Integration
The Strava API covers activities, heart rate, GPS, and webhooks. Open Wearables handles OAuth, rate limits, and normalization. One unified API for your app.
What you get from the Strava API.
Running, cycling, swimming, all types
Full traces, polylines
Avg, max, min during activity
Per activity
Gain, loss, profiles
Avg pace, max speed, splits
Cycling watts, normalized power
Per activity
Per activity, moving time
How Strava API integration works.
User connects their Strava account
Open Wearables handles the Strava OAuth flow. Your users authorize access through a standard consent screen. No custom OAuth implementation required on your end.
Data is normalized to a unified schema
Activity data from Strava is ingested and normalized alongside data from any other connected providers. Heart rate, distance, pace, elevation, and other metrics are mapped to a consistent structure regardless of the source device or app.
Your application calls one unified API
The same endpoints work for every provider. No per-provider integration logic in your codebase. No handling of Strava-specific rate limits or pagination.
Strava is just the start.
One API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, Whoop, Oura, Apple Health, Polar, Suunto, Samsung Health, Google Health Connect. Same endpoints, same data format.
See all providers →Open health scores
Sleep, recovery, strain, stress, HRV, VO2 max. Open algorithms you can audit and tune for your population.
Explore scores →AI reasoning engine
MCP server for any LLM. Detect trends, flag anomalies, build coaching profiles for wellness, performance, or clinical use cases.
Learn more →Open Wearables vs SaaS vs native Strava API.
| Aspect | Native Strava API | SaaS APIs | Open Wearables |
|---|---|---|---|
| OAuth implementation | You build and maintain it | Handled by provider | Handled by Open Wearables |
| Rate limit management | You handle 100/15min and 1,000/day limits | Handled by provider | Handled by Open Wearables |
| Webhook subscriptions | You build subscription and validation logic | Handled by provider | Handled by Open Wearables |
| Data normalization | Strava-specific response format | Provider-defined schema | Unified schema across all providers |
| Multi-provider support | Separate integration per provider | Depends on vendor tier | One unified API for all providers |
| Per-user pricing | No platform fee | Charged per connected user | $0 per user |
| Data ownership | You own all data | Vendor stores your users' data | You own all data |
| Maintenance on API changes | Your team tracks and adapts | Vendor absorbs changes | Open Wearables absorbs upstream changes |
← scroll to see all →
Why Open Wearables for Strava.
Activity-focused
Complements passive health data from other providers. Strava captures the workouts, Garmin and Whoop capture the recovery.
Works with any device syncing to Strava
Garmin, Wahoo, Apple Watch, Polar. If it syncs to Strava, Open Wearables can read it.
GPS and route data
Full trace data for mapping. Polylines, elevation profiles, and split data for every recorded activity.
Cross-provider correlation
Strava activities plus Garmin or Whoop recovery data in one query. One schema, every provider.
Up and running in minutes.
GET /v1/events/workouts
{
"date": "2026-01-15",
"source": { "provider": "strava", "device": "Garmin Forerunner 265" },
"type": "run",
"distance_m": 8540,
"pace_min_per_km": 5.12,
"elevation_gain_m": 142,
"heart_rate": { "avg_bpm": 155, "max_bpm": 178 }
}
Open Wearables is open-source and self-hosted. To use the Strava integration, register your application at developers.strava.com and configure credentials in your deployment.
Strava data in your app,
without the boilerplate.
Open Wearables handles OAuth, rate limits, and normalization. MIT licensed. $0 per user.
Common questions.
Does Open Wearables handle Strava's rate limits?
Yes. Open Wearables manages Strava's rate limits (100 requests per 15 minutes, 1,000 per day) internally. Your application queries Open Wearables without needing to track or respect Strava's upstream limits directly.
Does Open Wearables support Strava webhooks?
Yes. Open Wearables subscribes to Strava webhook events and syncs new activity data automatically when users complete a workout. Your application does not need to implement webhook handling directly.
Do I need a Strava API key?
Yes. You need to register your application at developers.strava.com and obtain API credentials. Open Wearables handles the OAuth flow and data layer, but the credentials are yours to obtain directly from Strava.
Which other providers can I connect alongside Strava?
Open Wearables currently integrates with Garmin, Polar, Whoop, Apple Health, Samsung Health, Google Health Connect, Suunto, and Oura. All providers share the same unified API schema.
Is Open Wearables production-ready?
Yes. Open Wearables is actively maintained and used in production. Check the GitHub releases for the current status of each provider integration.
Open Wearables is built and maintained by Momentum, a digital health agency reshaping healthcare through technology. Since 2016, they have been turning medical discoveries into compliant, scalable digital solutions. Momentum offers commercial services on top of Open Wearables for teams that need custom integrations, enterprise deployment, or SLA-backed support.
themomentum.ai →Other integrations
Comparing options? See how Open Wearables compares to Terra, ROOK, Sahha and others →
One API. Every provider. Zero per-user fees.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.
