The user ID set in the PartnerParams JSON must be unique. It is used to connect future jobs to the correct user. It can also be used to re-enroll a user if there is a problem with their first try. You can also deactivate a user so they can't do any other jobs. An example of this use case if if you want to temporarily block a user from authenticating. You can also permanently block a user from any future actions.
To allow a user ID to re-enroll, it is necessary that you enable a re-enrollment before it occurs on that specific user ID. This is done by making a call to:
POST https://[env].smileidentity.com/api/v2/partner/enrollee
Where [env]
is either "portal" or "prod"
With a JSON body shown below and the allow_re_enroll flags set to true:
{'user_id': '<Put User ID here>','allow_re_enroll': true,'partner_id': '<Put your partner ID here>','timestamp': <Put the timestamp recieved from generate_sec_key() call here>,'sec_key': '<Put sec_key recieved from generate_sec_key() call here>','email': '<Put your email address here>','environment': '<test | production>'}
To temporarily deactivate a user ID, use the same endpoint as above with the active flag set to false as in the following example body.
{'user_id': '<Put User ID here>','active': false,'partner_id': '<Put your partner ID here>','timestamp': <Put the timestamp recieved from generate_sec_key() call here>,'sec_key': '<Put sec_key recieved from generate_sec_key() call here>','email': '<Put your email address here>','environment': '<test | production>'}
To permanently block a user ID, use the same endpoint as above with delete flag set to true as in the following example body.
{'user_id': '<Put User ID here>','delete': true,'partner_id': '<Put your partner ID here>','timestamp': <Put the timestamp recieved from generate_sec_key() call here>,'sec_key': '<Put sec_key recieved from generate_sec_key() call here>','email': '<Put your email address here>','environment': '<test | production>'}