Get User by Client User ID

Vital Team API Key

A unique ID representing the end user. Typically this will be a user ID number from your application. Personally identifiable information, such as an email address or phone number, should not be used in the client_user_id.

A unique ID representing the end user. Typically this will be a user ID from your application. Personally identifiable information, such as an email address or phone number, should not be used in the client_user_id.

A list of the users connected sources.

When your item is created

Fallback time zone of the user, in the form of a valid IANA tzdatabase identifier (e.g., `Europe/London` or `America/Los_Angeles`).
Used when pulling data from sources that are completely time zone agnostic (e.g., all time is relative to UTC clock, without any time zone attributions on data points).

Your team id.

User id returned by vital create user request. This id should be stored in your database against the user and used for all interactions with the vital api.

Fallback date of birth of the user, in YYYY-mm-dd format. Used for calculating max heartrate for providers that don not provide users' age.

Ending bound for user data ingestion. Data from this date or later will not be ingested and the connection will be deregistered.

Starting bound for user data ingestion. Data older than this date will not be ingested.