Waymark / Routes / developers.wahooligan.com Authenticate with Wahoo Cloud API, read a user's workout history, and receive workout_summary webhook events
domain: developers.wahooligan.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Register an application in the Wahoo API developer portal to obtain a client ID and secret Complete OAuth2 authorization requesting user_read plus workouts_read (and offline_data if you want webhook delivery and refresh tokens) Call the workouts endpoint with the user's access token to list and read stored workout history and files Configure your webhook receiver URL in the app settings so Wahoo can POST workout_summary events when new workouts sync Respond to each webhook delivery with an HTTP 200 promptly so Wahoo does not treat it as failed Known gotchas Webhook delivery requires the offline_data scope to be granted by the user — without it you'll only get data via polling The user_read scope must always be included in the authorization request or the API returns a 403 on subsequent calls Webhook payloads are notifications, not full workout data — a follow-up API call is still needed to fetch the workout file/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