Attach a selfie image to a KYC check
/v1/kyc/checks/{id}/selfie-imageRequires an API client bearer token.
Attaches a selfie image to a case for face-match comparison against its retained document image (S5a) — the API-population intake path, called by a programme manager’s own backend on the applicant’s behalf (no capture widget, no operator supervision). The image is stored under purpose-bound custody and referenced by token, exactly like the document image; a replacement selfie erases the one it supersedes. If the case is already evaluating and the active policy requires `face_match`, a fresh evaluation is enqueued. Requires an Idempotency-Key header. Callable by `user` or `admin` callers, which includes API clients (OAuth2 client-credentials).
Parameters
Path parameters
| Name | Required | Description |
|---|---|---|
| id | required |
Header parameters
| Name | Required | Description |
|---|---|---|
| Idempotency-Key | required | Client-chosen. An identical retry with the same key returns the stored response; reusing the key with a different payload returns 409. |
Request body
Example
curl -X POST https://api.rigid.fi/v1/kyc/checks/{id}/selfie-image \
-H "Authorization: Bearer $RIGID_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"selfie_image_base64": "string"
}'Responses
200The selfie image was attached.
400Validation error
401Authentication required
403Forbidden
404No such check
409The case is in a terminal state and can no longer accept a selfie image, or the Idempotency-Key was reused with a different payload
429Too many KYC writes from this caller — see Retry-After
500Internal server error