I received an email from Strava today which was very disappointing.
As of July 1, 2013, V1/V2 API endpoints have been retired. Libraries, sites, and applications using these endpoints will cease to work.
In previous blog updates, we’ve discussed status and access to V3 of our API. As mentioned then, we had to make difficult decisions this year about where to invest time and resources – feature development or a full-fledged API program. We have chosen to focus on feature development at this time and so access to V3 of our API is extremely limited.
Any developer who has been granted access to V3 of the API has been contacted. We will revisit our API program and applications from time to time, but for the time being, we have no plans to grant further access in 2013.
If you have questions or comments, please send an email to [email protected]. Given our limited resources, you should not expect an immediate response.
Thanks for your understanding,
Your Friends at Strava
The highlights (or lowlights) from this email:
- Strava have no plans to allow anyone else to access their new API for at least six months
- It seems Strava aren’t interested in dialogue with their community about this decision.
I’ve been using the Strava V1 and V2 APIs now for several years, and have written quite a few blog posts about how to use it. The V1 and V2 APIs were always fairly experimental, but that was okay. We all understood that and it was part of the fun of working with Strava.
Discontinuing the V1 and V2 APIs was in the pipeline, and again we Strava API users could understand limiting the V3 API beta program to a small number of developers. However, the abrupt announcement today that not only are the V1 and V2 APIs no longer available, but now Strava won’t be making the V3 API available to anyone else for an Internet Eternity (that is, at least 6 months) either is completely unexpected.
The only Windows Phone app that integrates with Strava no longer works. My apps no longer work. And there appears to be no future for any of these apps.
Now, I’ve been a Strava Ambassador since before they started their official Ambassador program, and have had a lot of fun promoting Strava. I’ve developed popular tools that integrate with the Strava API. It is a very big disappointment to me that they’ve decided to throw away all that good-will with their developer community. This is not the way to treat the most dedicated and enthusiastic portion of your user base, Strava!
5 thoughts on “Strava have decided to abandon their developer community”
I totally agree Marc. It’s very disappointing. I was considering going pro but there’s no chance now if I can’t script adding the weather conditions to my rides.
If Garmin Connect step up their game with their API it may result in me abandoning Strava for good.
Very poor decision on Strava’s part.
My main criticism of strava is the inability to post comments on route segments. We have people posting timings on strava for segments near here, where the speed is completely inappropriate for the terrain ) narrow off road paths in a nature reserve, frequented by elderly people and families with prams etc.
You can flag segments as dangerous — but the only problem is that someone else will create the segment, and probably name it something snarky like “Narrow Off-Road Path — Not Dangerous At All”. I’ve seen that happen a few times. It’s a difficult problem to solve, and I’m not sure comments on segments themselves will actually improve things.