How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

agent native

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles EGYM the way a machine reads it — 27 machine-readable artifacts across 10 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 59.8/100 (strong), with a separate agent-readiness read of 73/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.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 59.8/100 · strong
Contract Quality 16.8 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 9.6 / 13
Governance 2.5 / 12
Discoverability 7.2 / 10
Regulatory · Health 7.9 / 15
Agent readiness — 73/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency documented 4.5 / 9
Stable Error Semantics 8.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
EGYM Kin Score — API readiness rating by API Evangelist

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>

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 10

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 MMS API V2

The current member-management-system integration API. RESTful contract for gym management software to sync member accounts and memberships into EGYM Cloud, manage profile pictur...

EGYM MMS API v1

The legacy member-management-system API (Gym API v1). Publishes and reads member profiles, gym and user products, check-in / check-out events, trainer tasks and a liveness endpo...

EGYM Data Hub API

Analytics and measurement export API for the authenticated gym location. Offers six synchronous CSV/JSON export endpoints — general analytics, Smart Strength workouts, Smart Str...

EGYM Data Export API

Per-account export API returning a member's workouts and their strength, cardio and body measurements. Marked "Alpha preview" by EGYM. Notable discovery property: this API is li...

EGYM Equipment Vendor API (standalone clients)

Device-to-server API for equipment vendors integrating cardio, strength and measurement hardware directly with EGYM Cloud. Covers OAuth token exchange (RFID, NFC wallet, encrypt...

EGYM Equipment Vendor API (server-to-server)

Backend-to-backend API for equipment vendors whose measurement devices report through the vendor's own cloud rather than talking to EGYM directly. Covers OAuth token creation wi...

EGYM User Connect API

User-authorized API that lets third-party fitness and wearable apps write a member's own data into their EGYM ID account. Accepts workout submissions and cardio measurements — V...

EGYM Canonical GroupX Classes API (blueprint)

An inverted contract: rather than an API EGYM operates, this is an "API blueprint" that EGYM publishes for member-management-system vendors to IMPLEMENT on their own hosts, so E...

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...

Scroll within the panel for all 10 ·

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).

DATA EXPORT API

OPEN COLLECTION

Data Hub API

OPEN COLLECTION

MMS API v1

OPEN COLLECTION

MMS API V2

OPEN COLLECTION

OpenAPI definition

OPEN COLLECTION

Scroll 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.yml

MCP SERVER

Pricing 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 six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Egym Plans Pricing

0 plans

PLANS

Rate 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

1 limits

RATE LIMITS

Event 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 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...

ASYNCAPI

Security 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.

Egym Authentication

apiKey/http/oauth2 · 4 schemes

SECURITY

Egym Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

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.

Egym Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

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.

Egym Agentic Access

117 operations · 62 acting

117 operations · 62 acting

AGENTIC

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.

Documentation 4

Reference material describing how the API behaves

Access & Security 3

Authentication, authorization, and security posture

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/egym · machine-readable index on apis.io

Where this information came from

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.