Emver
Emver
Profiden+ Blog
Documents & Biometrics

Liveness Detection API

Detect presentation attacks in a single selfie or short capture. Liveness Detection returns a live or spoof decision with a confidence score, protecting Face Match and remote KYC from printed photos, replayed videos and masks.

Response
Real-time
Inputs
1 required
Consent
Recorded per request
Billing
Per successful call
POST /v1/liveness-detection
Sandbox · Production
  1. Your application sends

    • Selfie image or short capture*
  2. Profiden API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    Profiden biometric engine

  4. You receive

    • Liveness decision (live / spoof)
    • Confidence score
    • Capture quality feedback
liveness-detection Full reference

What the Liveness Detection API does

Remote onboarding is only as strong as its weakest capture. Liveness Detection analyses the selfie for signs of a real, present person, without asking them to perform awkward gestures, and returns a decision your flow can act on before running Face Match.

It works passively on a single frame or actively with a short guided capture when your risk policy calls for it.

Consent is part of the contract

Facial images are biometric data. Capture consent before the check; images are purged after processing.

Benefits of the Liveness Detection API

Prove the selfie is a live person, not a photo, screen or mask.

Blocks spoofing

Printed photos, screens and masks are rejected.

Low friction

Passive mode needs no gestures from the user.

Real-time

Runs before Face Match in the same flow.

Policy-driven

Choose passive or active capture per journey.

Use cases

Liveness Detection API use cases

Where the Liveness Detection API is typically called, and what it settles there.

Video and selfie KYC

Ensure the capture is live before the identity decision.

App login step-up

Liveness plus Face Match for sensitive actions.

Field partner check-ins

Confirm the assigned person is the one on shift.

Remote proctoring

Keep the verified candidate in front of the camera.

How the Liveness Detection API works

Request and response details, environments and a ready-to-import collection are in the developer console at console.profiden.com.

01

Authenticate

Call with your organisation API key. Sandbox and production use the same contract.

02

Send the inputs

Selfie image or short capture as a JSON body. Optional fields sharpen the match.

03

We verify at source

Profiden queries the authoritative record, normalises the answer and logs the request.

04

Act on the result

A verification status plus the fields listed above, in the same response envelope as every other API.

Built for the DPDP Act 2023

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

Encryption in transit and at rest
Data processed in India
Per-request audit trail
Masked identifiers in responses

Liveness Detection API: frequently asked questions

What teams ask before adding the Liveness Detection API to their integration.

No. Passive liveness works on a single selfie. Active mode uses a short capture for higher assurance.

No. Liveness proves a live person is present; Face Match proves it is the right person. Use both.

Related APIs

APIs that usually run alongside the Liveness Detection API, on the same key.

All APIs

Get access to the Liveness Detection API

Tell us your use case and expected volume. We set up the organisation, share per-call pricing and issue keys.