Recommended integration architecture for a web-based cycling coaching platform

Hello Garmin Developers,

I am developing a web-based cycling coaching platform that analyzes completed cycling activities to generate personalized ride recommendations.

Unlike applications that only use activity summaries, our recommendation engine depends on the original FIT activity files because we derive additional physiological and performance metrics from second-by-second telemetry such as power, cadence, heart rate, GPS, elevation and speed.

Before implementing the platform, I would like to understand Garmin's recommended integration architecture.

For a web-based coaching platform where users authorize access to their Garmin Connect accounts, is the Garmin Connect Activity API the recommended approach for automatically receiving completed FIT activity files?

Or is there another supported integration that Garmin recommends for platforms performing post-ride analytics and coaching?

The platform is currently under development and will initially be evaluated with a small community of cyclists before a broader public release.

Any guidance would be greatly appreciated.

Thank you.

  • Hello,                                                                                      UniPass login


    For your use case, Garmin’s recommended path is to integrate through the Garmin Connect API (specifically the Activity API), which is designed for partner platforms to receive completed activity data—including FIT files—once users authorize access. This is the supported approach for post‑ride analytics and coaching platforms, as it ensures secure, automatic delivery of the original activity files rather than relying on summaries. If you’re planning a pilot with a small cycling community, you’ll need to apply for Garmin’s developer program and request access to the Connect API, since direct FIT file delivery is only available through that channel.