Secure image capture

Yoti age estimation also supports SICAP (Secure Image Capture) which works alongside the web browser face capture module. This ensures the captured image has not been manipulated (for e.g., injection attacks) before it is submitted to the Yoti backend for processing.

In order to use SICAP, you will need to:

  • Use Yoti’s React/JS Face Capture Module (FCM) version 1.0.0 or later.
  • Use the fields "img" and "secure" from FCM output.
  • Add a query parameter when calling the Yoti API endpoints.
  • Modify the API request body with a "secure" output added.
Good to know
FCM image output cannot be modified. Any change in ‘img’ will be rejected by the backend.

Endpoints

If you wish to use the secure feature, you will need to add the query parameter ‘?secure=true’ to the applicable endpoint below:

  • /v1/age-verify?secure=true
  • /v1/age-antispoofing-verify?secure=true

Note: if secure is requested, you will also need to add a “secure” field in the request body, or you will get an 'INVALID_REQUEST_BODY' error message.

Request body

JSON
Copy

Use the “img” and “secure” fields that are automatically returned from the Face capture module on success. Do not modify these fields manually.

Response body

JSON
Copy

This remains the same as the response without the SICAP.

Error codes

SICAP feature introduces new API error codes:

HTTP CodeError CodeError Description
400SECURE_REQUEST_IS_EMPTYSecure request field is empty.
400SECURE_SESSION_NOT_FOUNDSecure session not found.
400SECURE_SIGNATURE_NOT_FOUNDSecure signature not found.
400SECURE_VERSION_NOT_FOUNDSecure version not found.
400INVALID_SECURE_SIGNATUREFailed to verify secure session signature.
400SECURE_VERIFICATION_NOT_FOUNDSecure verification not found.
400UNTRUSTED_SECURE_SESSIONUntrusted secure session
401INVALID_SECURE_SESSIONInvalid secure session token.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard