Add device_name to /athlete/activities list (to comply with Garmin attribution)
So with app devs getting caught in the Strava vs Garmin saga, can you at least swiftly add the device_name parameter to the /athlete/activities list?
This way we won’t need to make additional API calls to the /activities endpoint just to check every single activity’s device…
<sigh>
Page 1 / 1
Strictly speaking the device_name doesn’t mean anything, it could be a manual upload. The important information would be if the activity was provided by the Garmin API at some point. If I’m not mistaken this information is already provided in the activities list with the external_id that always points to “garmin_ping...” in that case.
That’s not recommended:
The linked post was about Garmin uploads in general, not about the Garmin API.
Yeah it’s the individual activity data that needs to show where it’s coming from, not the athlete, since they could have multiple ways to track data. I was already pulling detailed activity data, so I just added a small line of text in my activity card that has displays device_name it if has Garmin in it.
I support this request.
Even if we could determine if the data comes from Garmin using the external_id (I am not able to test this because I don’t own a Garmin device), from what I understand the Garmin attribution requires the inclusion of the device name, which cannot be inferred by this id.
It would suffice to make additional endpoint of /athlete/activities that would return DetailedActivity[] (which contain device_info) instead of SummaryActivity[] (that does not) That would not be too hard I guess, and will save additiona requests by id to get DetailedActivity and get the device from there. I already also asked Garmin for clarifications, but no response from them atm.
I have already made the changes to my app :) but hesitate to lose another request per activity to just get the device id for table, when the stuff is all garmin stuff anyway (the app is for usb only garmin etrex 32x)
I also need this, so +1. We can’t rely on the external_id property. It seems to work for Garmin but not for other providers:
Funny that i don’t even use their API, i just upload GPX. It could be a gpx downloaded from Garmin unit, or gpx saved by strava app recorder or mapy.cz recorder for that matter. In this case, as i understand, i am not even mile close to their requirements. Still, when enquired about this, GARMIN says - if file is from garmin device - it adheres to the API guidelines. This is a political crap. That’s all I have to say, my app is the only way to upload my gpx from my garmin via usb cable. and it is a one user app, i do not show those maps or listings to anyone but user uploading the gpx. This is so cheezy …. getting responsible for a file on my disk from garmin? :) come on. Strava Team - plase - explain it to them ;) I have lost all hope. It’s going to crash either Garmin or Strava in the long run. :(
This is a political crap
Good explanation of the situation:
@Michal11 Yeah, Garmin isn’t much better than Strava when it comes to the question who rules over the data. It’s obviously bs to demand attribution (aka making free advertisement) if you don’t use their API and they can’t cut you off from their API if you don’t use it in the first place. But I fear that Strava apps aren’t allowed to make the distinction between Garmin API and file uploads, else Strava would have to investigate every time via what which way the Garmin activity data came from.
@Michal11 Yeah, Garmin isn’t much better than Strava when it comes to the question who rules over the data. It’s obviously bs to demand attribution (aka making free advertisement) if you don’t use their API and they can’t cut you off from their API if you don’t use it in the first place. But I fear that Strava apps aren’t allowed to make the distinction between Garmin API and file uploads, else Strava would have to investigate every time via what which way the Garmin activity data came from.
Let’s not forget this all started a year ago with Strava imposing restrictions on app developers about the use of Strava API data. Most of the activity data wasn’t even theirs in the first place, so Garmin is only trying to set the record straight…
@Jan_Mantau yes, the only thing my gramin does it appends creator tag to gpx xml. And strava recognizes it and I even asked to recognize it - since this garmin is not supported by any garmin app. But requiring attribution just because the file was recorded on garmin, come on I already paid for this, i have a garmin unit and DOWNLOAD gpx files from it. No api, no apps nothing. Anyway, i hope it backfires and make both strava and garmin to wait and rethink. Otherwise - we’re at war :)
Check out new swagger.json, device_name is on SummaryActivity now ;)