Thanks David. After the change, will coaches still be able to export their athletes’ Garmin-synced activities from the web UI (FIT download, activities CSV, wellness CSV), or will those exports exclude Garmin data like they do for Strava?
Exactly, I mean… A user can exercise their GDPR access and portability rights and authorize an app to receive qualifying personal data, right? So if a user gives consent for another app to access their data it’s within their right? ex: using Oauth like some libraries are already doing ?
IF this ultimately prevents Garmin files being shared directly via the API to 3rd parties then I suspect they will not and could not prevent you from manually sharing the .fit files from their devices.
Time will tell, but preventing that would quickly see customers leaving if they can afford to change to devices from alternative providers.
Wahoo have a very friendly policy for their API and welcome new integration.
My Coros activities sync to intervals.icu via the Wahoo App, which syncs directly to and from Coros.
I hope that helps anyone considering buying Wahoo or Coros products .
I hope this doesn’t affect the sending of structured workouts as well, since that encourages the use of Garmin devices—it would be a major loss for them.
OK so we have a workaround for future garmin data but what can I do about the years of historical garmin data in my intervals.icu account? I won’t be able to analyse this with an MCP server any longer?
You can do bulk download from Garmin and do bulk import to intervals and going forward find a non-garmin api way to get your data into intervals. This is only about Garmin API data that David pulls. It’s still your data, coming through the API is the problem. Not sure if bulk import will be the primary data source and over write your current garmin data. @david might have to do an enhancement for this. But hopefully he finds a better solution when working with Garmin
If garmin can display your data on a web page, you can extract it somehow. AI knows how to write a script for this. There is no way Garmin can prevent this, other than preventing you from also seeing your data in a browser.
Another way of syncing your data from garmin => spreadsheet => intervals would be this:
Send weekly GDPR request to Garmin (this can be automated)
Make a script that parses the response
Upload the relevant fields to intervals using the intervals API
I’ve just had a good call with Garmin, and I was able to clarify that the requirements around third-party sharing through our API are not new. While I can’t share details yet, I learned the revisions to the agreement are part of the planned reopening of the Garmin Connect Developer Program. Most importantly, I learned there will be an easier path for individuals and apps to access data from Garmin devices.
These are very positive developments, and we’re continuing to work with Garmin. There’s a big overlap between the passionate, data-hungry Intervals.icu community and Garmin users, so I’m encouraged by what’s coming next.
Could you please confirm whether it will still be feasible to leverage the Intervals API for Garmin users? I am currently developing an application and was looking forward to integrating Intervals for the data, but losing compatibility with Garmin would present a critical challenge for our project
Thanks a lot for keeping us in the loop and updated on how this progresses, David.
Was really happy to read this after the first email. What I guess I’m most considered about for Type to Run is if there will be a gap between Garmin data not being available from Intervals.icu (if that will still happen) and an easier path for apps to access data.
Understand that you don’t have answers to all our questions, but really hoping Garmin considers this, as this change can be really disruptive for a lot of app out there.
.