Cardio load

Get historical data by months

Changed on

Returns historical cardio load data for selected period of months counting from current date.

get/v3/users/cardio-load/period/months/{months}

Request

Path parameters

monthsinteger required

Period of months.

Response

Request was successful.

datestring date

Date in format YYYY-MM-DD.

cardio_load_status'LOAD_STATUS_NOT_AVAILABLE' | 'DETRAINING' | 'MAINTAINING' | 'PRODUCTIVE' | 'OVERREACHING' | 'RECOVERY_AFTER_OVERREACHING' | 'PRODUCTIVE_DROPPED_FROM_OVERREACHING' | 'PRODUCTIVE_ALMOST_OVERREACHING' | 'UNRECOGNIZED'

Text representation of cardio load status.

cardio_loadnumber float

Cardio load (training impulse, TRIMP) shows your cardiac response to a training session.

strainnumber float

Strain shows how much you have strained yourself with training lately. It shows your average daily load from the past 7 days.

tolerancenumber float

Tolerance describes how prepared you are to endure cardio training. It shows your average daily load from the past 28 days.

cardio_load_rationumber float

Ratio between strain and tolerance.

Example response

[
  {
    "date": "2023-01-01",
    "cardio_load": 0.2,
    "strain": 0.3,
    "tolerance": 0.4,
    "cardio_load_ratio": 0.1,
    "cardio_load_level": {
      "very_low": 0.1,
      "low": 0.1,
      "medium": 0.1,
      "high": 0.1,
      "very-high": 0.1
    }
  }
]

Changes

    • warning

      added the new PRODUCTIVE_ALMOST_OVERREACHING enum value to the / response property for the response status

    • warning

      added the new PRODUCTIVE_DROPPED_FROM_OVERREACHING enum value to the / response property for the response status

    • warning

      added the new RECOVERY_AFTER_OVERREACHING enum value to the / response property for the response status

    • info

      api tag Cardio load added

    • info

      api tag Cardio load (Beta) removed

    • info

      endpoint added