Waymark / Routes / developers.strava.com Create a Strava webhook subscription and handle push events for activity and athlete changes
domain: developers.strava.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps POST client_id, client_secret, callback_url, and a verify_token to the push_subscriptions endpoint to request a subscription Respond to Strava's GET validation request on your callback URL by echoing back the hub.challenge value within 2 seconds Once validated, receive POSTed event payloads for activity create/update/delete and athlete deauthorization events Use each event's object_type, aspect_type, and object_id fields to decide which Strava API call to make for full details Periodically verify your subscription with a GET request, since an app may only have one active subscription at a time Known gotchas Each application is limited to exactly one webhook subscription covering all authorized athletes — you cannot create per-athlete subscriptions The callback validation GET must respond within 2 seconds or subscription creation fails Webhook events only contain IDs and change type, not full activity data — a follow-up API call is required to get details
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