Allow Gear Assignment via Activity Upload in Strava API

Question

Hi Strava Developer Team,I’m a long-time Strava user and coach, and I use third-party tools like RunGap to sync training data from Garmin.One persistent issue is that Strava’s API does not currently allow third-party apps to assign gear (e.g. shoes or bikes) when uploading activities. As a result, this information needs to be manually updated every time, which breaks the otherwise smooth syncing workflow and diminishes the value of tracking gear-specific stats like shoe mileage.Could I request that you consider adding support for gear assignment via the Activities API — either by gear ID or name — during upload or in a subsequent PATCH call?This would benefit a lot of users who work across platforms.Thanks for considering this, and keep up the excellent work.All the best,Sean BarkesProfessional Coach

Jan_Mantau · Accepted Answer

A subsequent change of the gear_id is possible with the endpoint PUT /activities/{id}seehttps://developers.strava.com/docs/reference/#api-Activities-updateActivityById

seanbarkes · Answer

Thanks to your API docs, I now understand that gear can be updated after upload using PUT /activities/{id}. However, most third-party apps don’t do this. Would Strava consider making gear assignable during the upload process (via POST /activities) as well, or providing clearer tooling/examples so developers can use PUT more easily?

Maybe Strava could allow gear (via gear_id) to be assigned during the initial upload using POST /activities. Or alternatively, they could make it clearer and easier for third-party developers to use the existing PUT /activities/{id} endpoint to assign gear after upload?

Right now, no popular apps implement this, so users are stuck assigning gear manually on every activity.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded