Emver
Emver
Profiden+ Blog
Documents & Biometrics

Video KYC API

Complete identity verification over a live video session: document capture, liveness, face match, location capture and an optional agent review, with the recording and audit trail stored for compliance. Built for regulated onboarding that must happen remotely.

Response
Async, by webhook
Inputs
2 required
Consent
Recorded per request
Billing
Per successful call
POST /v1/video-kyc
Sandbox · Production
  1. Your application sends

    • Customer name and contact for the session link*
    • Documents to capture and checks to run*
  2. Profiden API

    Issues a hosted consent link, tracks the person's authorisation and assembles the result.

  3. Completed via

    Hosted video session with document and biometric checks

  4. You receive by webhook

    • Session outcome
    • Extracted document data
    • Liveness and face-match results
    • Geo-location and timestamps
    • Recording and audit trail reference
video-kyc Full reference

What the Video KYC API does

Video KYC combines the biometric and document APIs into one hosted session. The customer joins from a link, shows their ID, completes liveness and face match, and an agent can review and approve in real time or later. Every step is timestamped and the session recording is retained per your policy.

Because it is a hosted flow, you integrate a link and a webhook rather than building capture screens yourself.

Consent is part of the contract

Consent to record the session and process biometric data is captured at the start of the call and stored with the session.

Benefits of the Video KYC API

Agent-assisted or self-serve video identification with recording and audit trail.

Fully remote

Onboard customers anywhere without a branch visit.

Agent optional

Self-serve for low risk, agent-assisted where regulation requires it.

Audit-ready

Recording, timestamps and outcomes preserved together.

Link plus webhook

No capture UI to build.

Use cases

Video KYC API use cases

Where the Video KYC API is typically called, and what it settles there.

Bank and NBFC onboarding

Regulated remote KYC for new customers.

Lending

Verified identity before disbursal for digital loans.

Insurance

Proposal-stage identification without paperwork.

Executive hiring

Identity confirmation for remote senior hires.

How the Video KYC 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

Create the consent link

Send the person's details and the documents you need. You receive a hosted link to share on any channel.

03

The person authorises

They sign in and choose what to share. Nothing moves without their approval.

04

Receive the result

Verified documents and details arrive by webhook or on the status endpoint, and attach to the case.

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

Video KYC API: frequently asked questions

What teams ask before adding the Video KYC API to their integration.

Yes. Sessions can be routed to your reviewers, to Profiden's team, or approved automatically based on the biometric results.

For the retention period you configure, after which they are purged automatically.

Related APIs

APIs that usually run alongside the Video KYC API, on the same key.

All APIs

Get access to the Video KYC API

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