Pull a shop-affiliated club's recent activity feed via the Strava API
domain: developers.strava.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Strava API application in Strava's settings to get a client ID and secret
Complete the OAuth2 flow using a shop staff account that belongs to the target club
Call the club activities endpoint for the shop's club ID to retrieve recent member activities
Paginate through results using the documented pagination parameters for larger clubs
Respect Enhanced Privacy Mode flags on returned activities rather than assuming all data fields are populated
Stay within the documented default rate limits when polling for updates
Known gotchas
The authenticated athlete must belong to the club being queried — a shop's general API app credentials alone won't unlock a club's feed without a member's OAuth grant
Enhanced Privacy Mode can strip or limit activity details for individual athletes, so don't assume full data on every returned activity
Default rate limits are modest for a community feed feature — cache results rather than polling on every public page load
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?