Skip to content
OpenAthlete

Integrations

Five connections, one training calendar.

Activities come in from Garmin, COROS, Suunto, Polar and Strava. Planned workouts go out to Garmin, Suunto and COROS. Every connection is free.

Garmin

Workouts to the watch. Activities, sleep and HRV back.

  • Activities in
  • Workouts out
Setup and limits
New
COROS

Run, trail and bike workouts out. Activities, history and HRV in.

  • Activities in
  • Workouts out
Setup and limits
Suunto

Workouts as Suunto guides. Activities, sleep and HRV back.

  • Activities in
  • Workouts out
Setup and limits
Polar

Activities, sleep and nightly HRV in. No workouts out.

  • Activities in
  • No workouts out
Setup and limits
Strava

Activities and full history in. Nothing sent back.

  • Activities in
  • No workouts out
Setup and limits

At a glance

What each connection does

The limits come from each brand's API, not from your plan. Polar's API is read-only, Garmin and Suunto hand over 30 days of history, COROS takes its time.

ServiceActivitiesHistory importSleep and wellnessPlanned workouts
GarminYes30 daysYesYes
COROSYesAll, 50 a dayYesYes
SuuntoYes30 daysYesYes
PolarYesAfter connectingYesNo
StravaYesAllNoNo

Other ways in

Files, an API and a calendar feed

For the watch that isn't on the list, the app you built yourself, and the family calendar.

FIT, GPX and TCX upload

Drop files on a calendar day or upload several at once, up to 20 MB each. FIT and TCX keep their laps. A file that starts at the same time as an activity already there is refused, so uploading twice is harmless.

  • fitmorning-run.fit412 KB
  • gpxcol-de-porte.gpx1.8 MB
  • fitmorning-run (1).fit412 KB

Multisport FIT files aren't supported yet.

Activity Import API

Another app, such as a self-hosted activity tracker, can push FIT, GPX and TCX files to your calendar. It signs in with OAuth 2.1 and gets one scope, activities:import: it can send files, not read anything.

Read the API guide
# scope: activities:import
POST /activity-import/fit
POST /activity-import/gpx
POST /activity-import/tcx

Authorization: Bearer …

Calendar feed

Subscribe from Google Calendar, Apple Calendar or any app that reads iCal. Planned sessions, races and notes show up as all-day events with their full details. The link is secret, and you can regenerate it.

MTWTFSS10111213141516
5 × 4' at threshold1h05 · 13 km
10 km · A16 Sun

Self-hosting

On your own server, COROS works out of the box.

Garmin, Suunto, Polar and Strava only open their APIs to registered developers, so a self-hosted instance offers them only if its admin has signed up with each. COROS needs nothing: every connection registers itself. File upload and the Activity Import API work everywhere.

Self-hosting guide
COROSWorks out of the box
GarminNeeds a developer account
SuuntoNeeds a developer account
PolarNeeds a developer account
StravaNeeds a developer account

Questions about connections

No. Every connection works on the free plan and on self-hosted instances. Supporter adds AI on our keys and unlimited coached athletes, nothing else.

Yes. Each one has its own switches for activities, workouts and metrics in Settings > Connectors. If your watch brand has its own connection, prefer it to Strava: you also get wellness data, and workouts on the watch with Garmin, Suunto and COROS.

Their APIs don't take planned workouts: Polar's is read-only, and Strava has no workout feature to send to. Garmin, Suunto and COROS do accept them.

Not supported today. If your device or app exports FIT, GPX or TCX files, upload them, or have an app push them through the Activity Import API.

No. Each athlete connects their own account. You plan on their calendar, and the session goes out through whatever they connected: a Garmin for one, a COROS for another. Polar and Strava users follow it from the app.

Plan here. Train with the watch you have.

Create a free account, then pick your service in Settings > Connectors.

Create a free accountHow watch sync works

Free forever. No credit card.