Skip to main content
GET
Get Current Biometric Session

Overview

This endpoint returns the most recent biometric session for an entity (by createdAt), regardless of status: pending, in_progress, approved, rejected, etc. It mirrors GET /api/kyc/entities/{entityId}/current for KYC validations.
If the entity has never had a biometric session, the API responds with 200 and null (not 404), same as the KYC current endpoint.

When to Use

  • Recover a pending session to re-embed sessionUrl or cancel it
  • Check status of the latest biometric attempt (status, rejectionCode, decision)
  • Resolve ACTIVE_SESSION_EXISTS when creating a new session: the active session id is here (or in activeSessionId on the 409 error)

Request

Headers

Response

200 OK β€” session found

200 OK β€” no sessions

  1. POST /api/kyc/biometric/sessions β†’ store id and sessionUrl
  2. Embed sessionUrl in an iframe
  3. Poll: GET /api/kyc/biometric/entities/{entityId}/current or GET /api/kyc/biometric/sessions/{id}
  4. To restart: POST /api/kyc/biometric/sessions/{id}/cancel (pending / in_progress only)

Difference From List currentSessionId

GET /api/kyc/biometric/sessions?entityId=... includes currentSessionId: the latest approved session (active biometric verification). This /current endpoint returns the latest created session, which may be pending.

Error When Creating a Second Session

If you try to create another session while one is active (pending / in_progress), you get 409 ACTIVE_SESSION_EXISTS with the blocking ID:
Cancel with POST /api/kyc/biometric/sessions/{activeSessionId}/cancel, then create again.