Users
Get User
GET User details given the user_id.
GET
/
v2
/
user
/
{user_id}
Authorizations
x-vital-api-key
string
headerrequiredAPI key based authentication
Path Parameters
user_id
string
requiredResponse
200 - application/json
client_user_id
string
requiredA 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.
connected_sources
object[]
requiredA list of the users connected sources.
created_on
string
requiredWhen your item is created
fallback_birth_date
object
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.
fallback_time_zone
object
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).
team_id
string
requiredYour team id.
user_id
string
requiredUser 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.