integrate with wodify to pull workout and performance data
domain: docs.wodify.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for Wodify API access and obtain an x-api-key credential sent as a request header.
Review the API reference at docs.wodify.com for the customers/locations, programs/classes, class reservations and sign-ins, and workouts categories.
Call the workout endpoints to retrieve programmed or logged workouts; use the formatted-workout endpoint if you need pre-rendered HTML for embedding, such as a WOD display board.
Call the class reservation and sign-in endpoints to correlate attendance with the workout performed that session.
For data Wodify's API doesn't expose, use its Zapier integration as a fallback automation path.
Known gotchas
Individual athlete performance/PR history coverage varies; confirm current endpoint support in docs.wodify.com before committing to a scores or leaderboard integration.
The x-api-key is a single static credential per account with no documented OAuth refresh flow; rotate it manually if compromised.
The formatted-workout HTML output is meant for display embedding, not structured parsing; use the raw workout endpoint for structured fields.
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?