Step 2: User Provisioning
Provisioning users is an ID exchange mechanism that allows your users data to remain de-identified, safe and secure. To provision users in Validic, you will need the Organization ID and Organization Access Token you received from Validic. You will identify a user to Validic via a POST call containing a non-identifiable UID and Validic will return to you a Validic user ID and user Access Token.
First, the user provisioning POST call requires setting HTTP headers to “Content-Type: application/json”.
Second, the CUSTOMER_USER_ID information you need to pass is your user’s identifier in your application, typically a user ID. We require using non-identifiable IDs instead of emails or names in order to remain compliant with HIPAA/PHI deidentification standards.
You need to store the corresponding USER_ID and USER_ACCESS_TOKEN from the response for the provisioned user. You will refer to them when accessing user-related API calls in the future.
The user provisioning call is made as follows:
POST https://api.validic.com/v1/organizations/{ORGANIZATION_ID}/users.json
{
"user": {
"uid": "{CUSTOMER_USER_ID}"
},
"access_token": "{ORGANIZATION_ACCESS_TOKEN}"
}
201
{
"code": 201,
"message": "Ok",
"user": {
"_id": "{USER_ID}",
"access_token": "{USER_ACCESS_TOKEN}"
}
}
For full detail regarding user provisioning and user related API calls, please visit
the Users section of our API Documentation.