---
title: "Validate and assess a selfie via session (mobile)"
method: POST
path: "/api/v1/verify/session/{id}/validate-selfie"
tags: ["Verification"]
---

# Validate and assess a selfie via session (mobile)

`POST /api/v1/verify/session/{id}/validate-selfie`

## Request

- Base URL: `https://api.tuteliq.ai`
- URL: `https://api.tuteliq.ai/api/v1/verify/session/{id}/validate-selfie`
- Auth: one of:
  - HTTP bearer
  - API key in header `x-api-key`

Per-step selfie validation for the cross-device flow. Always checks that a face is present. When the request also carries the liveness capture (`liveness_frame` files and the `liveness_token` field), it runs the selfie assessment now (liveness, age estimation, and the face match against the document already processed by validate-document) and the session carries the DECISION, never the selfie or the frames, to submit, which then needs no images. `assessed: false` means the assessment did not run (no capture sent, or nothing to match against) and the submit must carry the selfie and liveness as before. Free, no credits consumed.

## Path parameters

- `id` string, required

## Response `200`

Default Response

- object
  - `valid` boolean
  - `face_detected` boolean
  - `message` string, nullable
  - `assessed` boolean

---

[API](https://skmtc.dev/tuteliq/apis/tuteliq-api.md) · [All operations](https://skmtc.dev/tuteliq/apis/tuteliq-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tuteliq/apis/tuteliq-api/revisions/8490332e0031?raw)