Create User
/v2/user
curl --request POST \
--url https://api.tryvital.io/v2/user \
--header 'x-vital-api-key: <x-vital-api-key>' \
--data '{
"client_user_id": "<client_user_id>"
}'curl --request POST \
--url {{BASE_URL}}/v2/user/ \
--header 'Accept: application/json' \
--header 'x-vital-api-key: <API_KEY>' \
--header 'Content-Type: application/json' \
--data '
{
"client_user_id": "your_unique_id"
}
'
{
"client_user_id": "5269f80a-fb0b-432a-b311-c3eac1a46260",
"user_id": "e209947b-323e-4108-8e18-1518b80da0bd"
}
​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).
​Response
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.
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.
User key returned by vital create user key request. This key should be stored in your database against the user and used for all interactions with the vital api.
curl --request POST \
--url {{BASE_URL}}/v2/user/ \
--header 'Accept: application/json' \
--header 'x-vital-api-key: <API_KEY>' \
--header 'Content-Type: application/json' \
--data '
{
"client_user_id": "your_unique_id"
}
'
{
"client_user_id": "5269f80a-fb0b-432a-b311-c3eac1a46260",
"user_id": "e209947b-323e-4108-8e18-1518b80da0bd"
}