Get Current Biometric Session
Biometric
Get Current Biometric Session
Retrieve the latest embedded biometric session for an entity β same pattern as GET /api/kyc/entities/:entityId/current for KYC validations.
GET
Get Current Biometric Session
Overview
This endpoint returns the most recent biometric session for an entity (bycreatedAt), 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
sessionUrlor cancel it - Check status of the latest biometric attempt (
status,rejectionCode,decision) - Resolve
ACTIVE_SESSION_EXISTSwhen creating a new session: the active sessionidis here (or inactiveSessionIdon the 409 error)
Request
Headers
Response
200 OK β session found
200 OK β no sessions
Recommended Flow
POST /api/kyc/biometric/sessionsβ storeidandsessionUrl- Embed
sessionUrlin an iframe - Poll:
GET /api/kyc/biometric/entities/{entityId}/currentorGET /api/kyc/biometric/sessions/{id} - To restart:
POST /api/kyc/biometric/sessions/{id}/cancel(pending/in_progressonly)
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.
| Field / endpoint | Meaning |
|---|---|
GET .../entities/:entityId/current | Latest created session (any status) |
currentSessionId in list | Latest approved session |
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:
POST /api/kyc/biometric/sessions/{activeSessionId}/cancel, then create again.
Related
- Embedded biometric session β create session
- Biometric webhook events