CorrConnectPlatform
Data sources and coverage
Today every activity your app reads was added by the athlete: a file from their device or a summary they typed in. Device connections come next, one maker at a time.
Available now
| Source | `source` value | Sports | Duration | Distance | Detail |
|---|---|---|---|---|---|
| FIT activity file | fit | run, ride, swim, walk, strength, other | Recorded session time | When recorded | Laps |
| TCX v2 file | tcx | run, ride, other | Sum of laps | Sum of laps | Laps and track point counts |
| GPX 1.1 file | gpx | other | Sum of timed segments | Not provided | Segments and point counts |
| JSON summary | manual_json | run, ride, swim, walk, strength, other | As entered | As entered, optional | Optional title |
Most watches, bike computers and training apps can export at least one of these formats, so athletes can bring workouts from almost any device today. The workout files guide has the exact limits, and the data model every field.
Device connections
When a connection goes live, its records arrive through the same endpoints and webhooks, with a new source value. Your code needs no change if it already accepts source values it doesn't recognize.
Data types
| Data | Status |
|---|---|
| Activity summaries | Available: activities:read |
| A stable athlete ID for your app | Available: profile:read |
| Sleep, recovery and body measurements | Coming soon, once connected devices can supply them |
| GPS routes and sensor streams | Not offered |
| Writing activities or planned workouts from your app | Not offered |
Ask for a source
Athletes can ask for the devices and platforms they use from inside their CorrConnect account; we use those requests to decide what to connect next. If your users need a source we don't cover, email [email protected] with the source and how many of your users it affects.