Skip to main content

FaceApi

MethodHTTP requestDescription
create_face_authenticator_using_postPOST /api/web/v2/users/{userid}/faceCreate a Face Biometric for a user
create_face_using_postPOST /api/web/v1/users/{userid}/faceCreate a Face Biometric for a user
delete_face_using_deleteDELETE /api/web/v1/face/{faceid}Delete a Face Biometric
get_faces_using_getGET /api/web/v1/users/{userid}/facesGet the Face Biometrics for a given user
get_user_face_settings_using_getGET /api/web/v1/users/{userid}/settings/faceGets a users Face Biometric settings
send_face_activation_email_using_putPUT /api/web/v1/face/{faceid}/activationSend an activation email for the Face Biometric
update_face_using_putPUT /api/web/v1/users/{userid}/faceUpdate the Face Biometric for a given user

create_face_authenticator_using_post

FaceCreateResponse create_face_authenticator_using_post(userid, face_create_parms)

Create a Face Biometric for a user

Create a Face Biometric for the specified user. Caller requires the FACE:ADD permission.
The Face Biometric can be created using either the web flow or the mobile flow.
If using the web flow, the Face Biometric can optionally use the Onfido applicantId and workflowRunId to link the Face Biometric to the correct Onfido applicant and workflow run.
If using the mobile flow, setting deliverActivationEmail to true will send an activation email to the user with instructions to download the mobile app and complete activation.
Setting returnQRCode to true will include a QR code in the response that can be scanned by the user to start the activation process.
If using the IDaaS stored biometric web flow, the encryptedBiometricToken parameter is required and must include both the encrypted biometric token and the customer user ID used to create the token in Onfido.

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
useridstr
face_create_parmsFaceCreateParms

Return type

FaceCreateResponse

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: application/json
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

create_face_using_post

FaceAuthenticator create_face_using_post(userid, face_create_parms)

Create a Face Biometric for a user

Create a Face for the specified user. Caller requires the FACE:ADD permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
useridstr
face_create_parmsFaceCreateParms

Return type

FaceAuthenticator

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: application/json
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

delete_face_using_delete

delete_face_using_delete(faceid)

Delete a Face Biometric

Delete a Face Biometric by the specified ID. Caller requires the FACE:REMOVE permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
faceidstrThe ID of the Face Biometric.

Return type

void (empty response body)

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: Not defined
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

get_faces_using_get

List[FaceAuthenticator] get_faces_using_get(userid)

Get the Face Biometrics for a given user

Get the Face Biometrics for the specified user. Caller requires the FACE:VIEW permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
useridstrThe UUID of the user to get the Face Biometrics for.

Return type

List[FaceAuthenticator]

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: Not defined
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

get_user_face_settings_using_get

UserFaceSettings get_user_face_settings_using_get(userid)

Gets a users Face Biometric settings

Get Face Biometric settings information for the specified user. Caller requires the FACE:VIEW permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
useridstrThe UUID of the user whose Face Biometric settings information is to be fetched.

Return type

UserFaceSettings

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: Not defined
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

send_face_activation_email_using_put

send_face_activation_email_using_put(faceid)

Send an activation email for the Face Biometric

Send an activation email for the Face Biometric specified by ID. Caller requires the FACE:ADD permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
faceidstrThe ID of the Face Biometric.

Return type

void (empty response body)

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: Not defined
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-

update_face_using_put

update_face_using_put(userid, face_update_parms)

Update the Face Biometric for a given user

Update the Face Biometric for the specified user. Caller requires the FACE:EDIT permission.

Example

  • Api Key Authentication (AdminAPIAuthentication):

Parameters

NameTypeDescriptionNotes
useridstrThe UUID of the user to update the Face Biometric for.
face_update_parmsFaceUpdateParms

Return type

void (empty response body)

Authorization

AdminAPIAuthentication

HTTP request headers

  • Content-Type: application/json
  • Accept: application/json

HTTP response details

Status codeDescriptionResponse headers
200Successful-
400Bad Request-
401Access denied-
403Forbidden-
404Not Found-
409Conflict-