Can you please update the clubs documentation at https://developers.strava.com/docs/reference/#api-Clubs. The data returned does not match the docs and there is some limit to the pagination effecting the number of activities that can be returned. Many users ran into both these issues and posted on the old Google groups.
Hopefully when you document these it will become clear this endpoint needs to be improved as it's currently of very limited use.
Solved! Go to Solution.
Hi @Elliott , it seems that the swagger json for this piece of the API spec (https://developers.strava.com/swagger/activity.json#/DetailedActivity) has become invalid because of this update. Can someone please correct it? Thanks!
@rorhug @Nick got it - we see where the inconsistency is now in the docs. The documented SummaryActivity model is out of sync with the documented response for club activities. I've added a ticket to get this updated. Apologies for any confusion and really appreciate you both flagging & talking through things here!
Thanks for the feedback!
Which data points are you finding returned that does not match our documentation so that we can take a look? The team just did an audit of a response returned by the get club activities endpoint and it matched up with our docs. We want to be sure to investigate what you're seeing on your end as well, thanks!
Great, I see you have (at some point) updated the docs to show you return `MetaAthlete` objects within the `SummaryActivity` objects. This wasn't the case before. The `MetaAthlete` objects contain just a userid, this is useless... but at least it's accurate!
The other big issue is the number of `SummaryActivity` objects that are returned. There used to be a weird hard limit and it didn't respect the paging params. Did you fix that too?
Oh, and now there's a start datetime! I think that's new too. Wow, is this finally approaching something usable?!