Why IntervalCoach uses Intervals.icu, not Strava directly

IntervalCoach connects through Intervals.icu rather than connecting to Strava directly. There are two reasons for this.

Strava limits how apps can use your data

Strava's API terms restrict how third-party apps can access and analyze your activity data, especially for AI-based coaching. Intervals.icu holds your own data and gives IntervalCoach reliable, complete access to it.

Strava doesn't expose the metrics a coach needs

IntervalCoach is built on structured training data: power and pace curves, estimated FTP, training load (Fitness, Fatigue, Form), and wellness data like HRV, resting heart rate, and sleep. Strava does not provide these in a usable form, while Intervals.icu calculates and stores all of them.

Getting your activities into IntervalCoach

IntervalCoach reads whatever is in your Intervals.icu account, so the only goal is to get your activities into Intervals.icu. The best way is to connect the source that records your rides and runs (Garmin, Wahoo, Zwift, Polar, and similar) directly to Intervals.icu. The original device sends the full data, including power, heart rate, and GPS.

You can connect Strava to Intervals.icu as well, but Strava passes along less detail than the original device, so connecting the device directly is the more reliable route.

Once a source is connected, new activities show up in Intervals.icu (and therefore in IntervalCoach) automatically. Intervals.icu can also backfill your existing history from that source, so your past training comes through too.