EGYM
EGYM is a Munich-headquartered fitness and health technology company that builds the connected-gym platform used by commercial fitness operators worldwide: Smart Strength and Smart Flex networked equipment, the EGYM Genius AI training engine, the EGYM Fitness Hub and Trainer apps, and the EGYM Wellpass / Corporate Fitness membership network that lets employers give staff access to thousands of partner venues. For developers, EGYM operates a public developer portal at developer.egym.com covering eight machine-readable APIs across three integration audiences — member-management-system (MMS) vendors syncing members, memberships, RFID/NFC credentials, check-ins, products and trainer tasks into EGYM Cloud; equipment vendors submitting body, cardio and flexibility measurements from devices or backends; and analytics consumers exporting workout and measurement data. EGYM also publishes an official documentation MCP server, an llms.txt, a written AI-agent instruction page, a dated change log, published rate limits and a documented webhook event catalog.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles EGYM the way a machine reads it — 55 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — EGYM scores 58.7/100 (strong), with a separate agent-readiness read of 51/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from EGYM's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/egym/"
title="EGYM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/egym.svg"
alt="EGYM Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/egym/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/egym/"
title="EGYM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/egym/card.svg"
alt="EGYM Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile EGYM
Each block below is one kind of artifact we hold for EGYM. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 38
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
EGYM Pay with Wellpass API
Authorization-and-capture API for booking platforms. A Wellpass member generates a single-use booking code in the Wellpass app for a specific gym; the partner platform validates...
EGYM Documentation MCP Server
Official hosted Model Context Protocol server published by EGYM at developer.egym.com/mcp and documented on the portal with copy-paste Codex configuration. Exposes six tools ove...
EGYM 1. Cardio Measurements API
API for submitting cardio measurements
EGYM 2. Workouts API
API for submitting workouts
EGYM Alive API
The alive API from EGYM — 1 operation(s) for alive.
EGYM Asynchronous exports API
Background export jobs that produce downloadable JSON, JSONL, or CSV files.
EGYM Body Measurement API
The Body Measurement API from EGYM — 2 operation(s) for body measurement.
EGYM Cardio Measurement API
The Cardio Measurement API from EGYM — 2 operation(s) for cardio measurement.
EGYM Cardio Test API
The Cardio Test API from EGYM — 3 operation(s) for cardio test.
EGYM Cardio Workouts API
The Cardio Workouts API from EGYM — 2 operation(s) for cardio workouts.
EGYM Flexibility Measurement API
The Flexibility Measurement API from EGYM — 2 operation(s) for flexibility measurement.
EGYM Gym API
The gym API from EGYM — 2 operation(s) for gym.
EGYM Gym Visit API
These operations are needed to transmit the information to EGYM, that a specific member is currently in the gym. Based on that information several business logics are built, to ...
EGYM Image API
The Image API from EGYM — 1 operation(s) for image.
EGYM L2 API
Operations related to L2 level of integration
EGYM L3 API
Operations related to L3 level of integration
EGYM Machine API
The Machine API from EGYM — 1 operation(s) for machine.
EGYM Measurements API
These operations are needed to retrieve measurements with corresponding metrics. Additional permissions are required to access these endpoints.
EGYM Member Account API
These operations are needed to create and update member accounts and their membership information.
EGYM Member Account NFC API
Note that NFC API endpoints are in beta as we've been tuning setup processes on both EGYM and partner sides.
EGYM Member Account Roles API
These operation are needed to assign and retrieve member account roles
EGYM Member RFIDs API
Operations with RFIDs
EGYM Migrating members API
These operations are needed to migrate members from V1 API to V2 API.
EGYM Open Exercise Workouts API
The Open Exercise Workouts API from EGYM — 1 operation(s) for open exercise workouts.
EGYM Partners API
The Partners API from EGYM — 1 operation(s) for partners.
EGYM Products booking API
Operations on EGYM products. Currently available products are EGYM Smart Strength (Machine Admission) and EGYM+
EGYM Push notifications API
Send push notifications to EGYM mobile apps
EGYM Resource API
The Resource API from EGYM — 2 operation(s) for resource.
EGYM Statistics API
The Statistics API from EGYM — 2 operation(s) for statistics.
EGYM Strength Workouts API
The Strength Workouts API from EGYM — 2 operation(s) for strength workouts.
EGYM Synchronous exports API
Immediate paginated JSON exports for weekly analytics and recent event data.
EGYM Task API
The task API from EGYM — 2 operation(s) for task.
EGYM Trainer Task API
These operations are needed to create and update trainer tasks.
EGYM User API
The User API from EGYM — 9 operation(s) for user.
EGYM User Details API
The User Details API from EGYM — 1 operation(s) for user details.
EGYM Webhooks API
Operations with webhooks
EGYM Workouts API
These operations are needed to retrieve workouts. Additional permissions are required to access these endpoints.
EGYM O Auth API
The OAuth API from EGYM — 2 operation(s) for oauth.
Scroll within the panel for all 38 ·
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Canonical GroupX Classes API
OPEN COLLECTIONDATA EXPORT API
OPEN COLLECTIONData Hub API
OPEN COLLECTIONEquipment Vendor API (for server-to-server cases)
OPEN COLLECTIONEquipment Vendor API (for standalone clients)
OPEN COLLECTIONMMS API v1
OPEN COLLECTIONMMS API V2
OPEN COLLECTIONOpenAPI definition
OPEN COLLECTIONScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
EGYM MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Egym Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Egym Rate Limits
RATE LIMITSEvent Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Egym Events Webhooks
ASYNCAPIEGYM MMS Webhook Events
DERIVED, NOT PUBLISHED BY EGYM. EGYM documents its webhook surface in prose at https://developer.egym.com/general/webhooks and manages subscriptions through the MMS API V2 OpenA...
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for EGYM — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/egym · machine-readable index on apis.io
This is an independent, third-party profile of EGYM, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.