SmartSelfie™ Authentication

Required Class: WebApi Class

Running SmartSelfie™ Authentication on Python

  1. Get your Smile ID Partner ID

  2. Get your API Key

  3. Create a Callback Endpoint

  4. Get your user's Selfie

  5. Get the user ID you initially used to register the user

  6. Submit the Job to Smile ID

  7. Interpret your results

Get your Partner ID

You can find your Partner ID in the menu list when logged into the portal.

Get your API Key

Your encoded API Key is also in the developer section of the portal.

  • Click on the Generate New API Key button

  • Copy your api key (ensure you are in the right environment)

Generate a new API Key
Copy your API Key

Create a Callback Endpoint

Responses from this product are asynchronous (based on various actions we carry out on the product) and are sent as soon as they are ready, you will need to setup a callback when submitting a job. You can read about creating a Callback URL here.

Get the User's Selfie

To successfully run SmartSelfie™ Authentication jobs you need to submit the user's selfie. There are two types of selfies that can be submitted

  • Selfie - a single colour-image selfie of user

  • (optional but required for proof of life) Liveness images - 8 colour images of user

The selfies can either be submitted as files (with the path to the image specified during submission) or as base64 encoded strings.

We recommend that you use our Web SDK to capture both of these types of images

Get the User's User ID

Since SmartSelfie™ Authentication entails comparing a user's selfie with the selfie they have on file in Smile ID, you must supply the User's existing user_id in the partner params (the user_id must be the same as the one you used when you ran a successful "Biometric KYC" or "Document Verification" for the user). If the User ID you supplied does not exist, the job will fail.

Submit the Job to Smile ID

You can copy the sample code below and edit with your partner and job details.

Getting the Job Result

By default, you always get the result of your job in the callback url you provided, however for some use cases you might want to get the job result in sync after submission. The flag return_job_status can be set to True if you want to get the job result in sync.

Refer to the category column of result codes of SmartSelfie™ Authentication for the comprehensive list of final codes (approved or rejected) and in-progress codes (provisional approval or suspected for spoof).

Response when return_job_status is set to False

If return_job_status is set to False, the response will be a JSON string containing:

The job result will be sent to the callback url you provided, it will look as follows:

Response when return_job_status is set to True

If you have use cases that require you to get the result in sync, you can set the return_job_status to True. We advise that you use the result sent to your callback to make final decisions as there are times when the submitted job requires human review, the final result after the review is completed can not be retrieved by setting the return_job_status to True.

If you set return_job_status to True (with images and history also set to True) then you will receive the JSON object containing the machine result like below:

Interpret your Results

You can read more about result codes and responses in the SmartSelfie™ Authentication section of the docs.

Last updated

Was this helpful?