Create User
POST Create a Vital user given a client_user_id and returns the user_id.
When the supplied client_user_id conflicts with an existing user, the 400 Bad Request error response
includes the Vital User ID (user_id) and the creation date (created_on) of the conflicting user.
Authorizations
Vital Team API Key
Body
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.
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).
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.
Starting bound for user data ingestion. Data older than this date will not be ingested.
Ending bound for user data ingestion. Data from this date or later will not be ingested and the connection will be deregistered.
Response
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.
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.