Strava API Changes
Due to a recent update to Strava's API terms, Cronometer will unfortunately not be able to support Strava integrations.
We recognize that this change may be disappointing for many of our users. While this change was not our decision, we'd like to assure you that we remain committed to providing other great tools and integrations to support our user's health. Users who currently have their Cronometer account connected with Strava will be disconnected on December 9th. Any data already synced with Cronometer will remain in the account.
We value the connection between fitness and nutrition tracking and remain dedicated to offering a variety of excellent tools and integrations to support your health. For a list of integrations that we currently support, please visit our user manual for web or for mobile.
We’re here to help with any questions or concerns and appreciate your understanding.
Comments
-
well this kills the usefulness of Cronometer for me as almost all of my fitness data comes via strava for now.. bummer. I wish you would build a connection to zwift...
-
Hey there @cdrom1028 that is a great integration suggestion and I have passed it along to the team. Thank you!
-
David, who runs intervals.icu, initially announced something similar in response to strava's api tos changed but backtracked after a call with strava.
https://forum.intervals.icu/t/strava-visibility-update-coaching-is-ok/80331
-
I rely on this, also. My strava data was integrating as of yesterday morning; but last evening's commute and this morning's did not register. From the sounds of this post, I will never have automatic integration again.
Is there any chance this will be reinstated? I use it every day (twice daily, in fact). -
Any possibility of integrating with RideWithGPS?
-
This is not good! Cronometer should approach Strava to sort this out immediately.
If not you are loosing a Gold customer. -
-
Hi all @MarvinFreeman @erisenhoover & @Heimavatn
Through our communications with Strava regarding their API changes, we have been informed that we no longer meet their requirements. As a result, we have had to close the integration.
We have ensured that the code remains intact, allowing us the flexibility to reactivate the integration should Strava revise its data usage policies in the future. We understand this news is disappointing for you all and many other users. While this decision was beyond our control, we want to assure you that we remain committed to delivering great tools and integrations to support users’ health.
-
Hey @John_Vance that is another great integration suggestion, thank you! I will pass it along to the team.
-
Both Rouvy and Hammerhead upload directly to RideWithGPS. I've been using RideWithGPS since Strava looked like it was going to fold before the last round of funding. RideWithGPS is in the black and doesn't depend on investment capital to stay afloat.
-
so what is the reason for the non-compatibility with the new API for STrava. It seems they're tightening up their AI terms - disallowing use of our/their data for the training of AI models. Is cronometer using AI and our data to train its models? Can you show us the reference to this in your privacy statement and/or your terms of service?
-
I tried to get round this by linking Cronometer to Apple Health and having Apple Health upload workout data (my Whaoo updates Apple Health). A recent bike ride was uploaded to Cronometer with the correct calorie figure, however it then started to upload and duplicate rides for the previous month which I definitely did not want. This despite the fact that I did select the “backfill” option in Apple Health. I have now removed the connection between the two which is a shame.
