domain: openplatformdocs.mywellness.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Decide which Technogym API surface you need: the Enterprise API for partner/touchpoint features, or the mywellness cloud API (apidocs.mywellness.com) for exchanging user/activity data with the wellness ecosystem.
Contact developer@technogym.com to request partner credentials, since access is issued per integration rather than open self-signup.
For server-to-server (membership software) integrations, implement user create/update/delete and behavioral-data retrieval endpoints.
For equipment or activity data, use the equipment login and tracking flow (QR-code based) or upload workout files (TCX/FIT) as shown in Technogym's sample app on GitHub (mywellnesscloud org).
Use the prescription endpoints if you need to list or assign training programs and read back results.
Known gotchas
Technogym's docs are split across multiple domains (openplatformdocs.mywellness.com, apidocs.mywellness.com, developer.technogym.com); confirm which one matches the credentials you were issued.
This is a partner-gated API, not open registration; expect a business and technical review before receiving keys.
Server-to-server and end-user-to-end-user integration patterns use different auth flows; mixing them up is a common early mistake.
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?