Get epoch data

DynamicEpochValues represents a period that is composed of a start and end timestamp. This data type is available up to second precision. The DynamicEpochValue REST-API allows for data retrieval of one user.

Please check the data type documentation for valueTypes (dataTypeIds) definitions and availability.

Retrieve DynamicEpochValues for a user

post

Retrieve harmonized intraday measurements (e.g., heart rate) for one user within a specified time range.

Header parameters

AuthorizationstringRequired

Basic Auth for your username:password. Required for all endpoints

Example: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

AppAuthorizationstringRequired

Basic Auth for your authID:authSecret. Required for all endpoints.

Example: Basic YXV0aElEOmF1dGhTZWNyZXQ=

Body

anyOptional

or

anyOptional

Responses

200

Request successful. Returns an array of DynamicEpochValues per user.

application/json

authenticationTokenstringOptional

The unique identifier of a user in Thryve's system. Newer interfaces call this parameter endUserId.

partnerUserIDstringOptional

The optional alias set by the developer when creating a user. Newer interfaces call this parameter endUserAlias.

400

Error response (invalid parameters, unauthorized, etc.).

application/json

post/v5/dynamicEpochValues

POST /v5/dynamicEpochValues HTTP/1.1
Host: api.thryve.de
Authorization: text
AppAuthorization: text
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 305

"authenticationToken='de3d1e068537dd927b48988cb6969abe'&startTimestamp='2025-06-02T00:00:00Z'&endTimestamp='2025-06-02T01:00:00Z'&startTimestampUnix=1581033600000&endTimestampUnix=1581034080000&valueTypes=1000&dataSources=1&detailed=true&displayTypeName=true&displayPartnerUserID=true"

[
  {
    "authenticationToken": "text",
    "partnerUserID": "text",
    "dataSources": [
      {
        "dataSource": 1,
        "data": [
          {
            "startTimestamp": "text",
            "endTimestamp": "text",
            "createdAt": "text",
            "startTimestampUnix": 1,
            "endTimestampUnix": 1,
            "createdAtUnix": 1,
            "dynamicValueType": 1,
            "dynamicValueTypeName": "text",
            "details": {},
            "value": "text",
            "valueType": "text"
          }
        ]
      }
    ]
  }
]

When retrieving the desired data period, a startTimestamp(Unix) endTimestamp(Unix) or a createdAfter(Unix) date needs to be added as parameters to the request. If both startDay and startTimestampUnix are provided, the system will use the ISO format and ignore the Unix timestamps entirely. The query range is set to a maximum of 30 days.

The response will include all values that overlap with the date range specified in the request. E.g., a user has the epoch values with timestamps 10:00:00 - 10:04:00 and 10:06:00 - 10:10:00, and the timestamps specified in the POST request are 10:02:00 - 10:08:00, the response will contain both epoch values.

The end timestamp will be null, if the epoch entry indicates an instant measurement, such as a weight or heart rate value.