Register a Wodify webhook subscription in the sandbox environment to receive real-time booking and lead events, separate from pulling workout/performance data via the core API.
domain: docs.wodify.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate requests with the x-api-key header per docs.wodify.com/docs/authentication.
Use the Wodify sandbox environment to register a webhook endpoint before touching production data.
Subscribe to specific webhook events (e.g. new booking, new lead) via the Webhooks management API.
Verify signed payloads arriving at the endpoint and acknowledge them per Wodify's expected response contract.
Promote the verified webhook configuration from sandbox to the production API key once confirmed.
Known gotchas
This is a push/event integration, distinct from pulling workout/performance data — the two use different parts of the API surface and should not be conflated.
Sandbox and production use separate API keys/environments; a webhook registered in sandbox will not fire for production events.
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?