Platform API · API Docs · eKYC Platform
Verify selfie
POST/ekyc/platform/verify_selfie
Uploads selfie images, runs liveness detection and face matching, and returns the final verification result synchronously.
Request
MethodPOST
Path/ekyc/platform/verify_selfie
Content-Typeapplication/json
Auth requiredYes — Bearer access_token
| Name | Type | Required | Description |
|---|---|---|---|
images | array | Required | Array of selfie images: [{ "base64": "<base64_string>", "metadata": "<string>" }]. The last element is the primary selfie. |
selfie_type | string | Optional | Type of selfie flow (e.g. passive, flash) |
Response
data.status carries the verification result. The data fields are identical to Verify ID — same names, same types, same meanings.
{
"data": {
"status": "success",
"error_code": "",
"error_message": {},
"label": "portrait",
"next_action": "",
"application_state": ""
},
"message": "verify selfie completed",
"time": "2026-01-01T00:00:00Z",
"verdict": "success"
}
Failure codes
The top-level verdict names the outcome, alongside the HTTP status code:
verdict | Status code | Description |
|---|---|---|
success | 200 | Verification completed (check data.status for result). |
invalid_parameters | 400 | images is empty or contains invalid base64 data. |
missing_authorization | 401 | Bearer access_token is missing. |
expired_token | 401 | Access token expired — call Initialize again. |
record_not_found | 404 | Session referenced by the access token no longer exists (expired or reset). |
limit_exceeded | 429 | A verification is already in progress for this session. |
failure | 500 | Internal server error or verification timeout. |