Register a Concept2 Logbook API application on the development site and read/write a rower's workout results via OAuth2.
domain: log.concept2.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an account and generate a Client ID/Client Secret on the Concept2 development site's key-creation page first, not production.
Implement the standard OAuth2 flow to get user consent and an access token scoped to the athlete's logbook.
Call the Logbook API's results endpoints to read a user's existing workout results, or write a new result from a connected performance monitor.
Validate the full read/write flow against development-site data before requesting production API credentials.
Once verified, repeat client registration on the production key-creation page and switch endpoints/credentials.
Known gotchas
Concept2 explicitly recommends developing against the dev site first, then re-registering separately for production — a dev Client ID will not work against production.
The developer documentation requires a logged-in Concept2 account to view in full.
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?