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 1. Cardio Measurements API

API for submitting cardio measurements

EGYM 1. Cardio Measurements API is one of 38 APIs that EGYM publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include 1. Cardio Measurements. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 3 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v0.

Requests are made against 3 base URLs: https://user-connect-api.cgn-3.test.co.egym.coffee/user-connect-api, https://user-connect.api.egym.com/user-connect-api, http://localhost:8080/user-connect-api.

3 operations 3 paths 8 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0
Base URL
https://mms.api.egym.com
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

1. Cardio Measurements 3

API for submitting cardio measurements

POST
/measurements/v1.0/cardio/vo2max
Submit VO2max
submitVo2MaxMeasurement body → 200400
POST
/measurements/v1.0/cardio/resting-heart-rate
Submit Resting Heart Rate
submitRestingHeartRateMeasurement body → 200400
POST
/measurements/v1.0/cardio/blood-pressure
Submit Blood Pressure
submitBloodPressureMeasurement body → 200400

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ValidationErrorDto (4 properties), SubmitBloodPressureDto (3 properties), SubmitRestingHeartRateDto (2 properties), FieldErrorDto (2 properties). Each schema is shown below with its type and property counts.

SubmitVo2MaxDto
object
2 properties 2 required
SubmitVo2MaxRequest
object
1 property 1 required
SubmitBloodPressureDto
object
3 properties 3 required
FieldErrorDto
object
2 properties
SubmitRestingHeartRateDto
object
2 properties 2 required
SubmitBloodPressureRequest
object
1 property 1 required
SubmitRestingHeartRateRequest
object
1 property 1 required
ValidationErrorDto
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

egym-1-cardio-measurements-api-openapi.yml Raw ↑

Other APIs EGYM publishes across the network.

EGYM Pay with Wellpass API
EGYM Documentation MCP Server
EGYM 2. Workouts API
EGYM Alive API
EGYM Asynchronous exports API
EGYM Body Measurement API
EGYM Cardio Measurement API
EGYM Cardio Test API
EGYM Cardio Workouts API
EGYM Flexibility Measurement API
EGYM Gym API
EGYM Gym Visit API
Where this information came from

This is an independent, third-party profile of EGYM 1. Cardio Measurements API, 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.