Identity Verification Documentation
Technical reference for the Proofglint IDV module: document types, API, webhooks, consent flow, and turnaround SLA.
Overview
The Proofglint IDV module verifies candidate identity through two mechanisms: document authenticity check and liveness detection. The result is stored in a separate data partition from interview scoring data. Interviewers have no programmatic access to IDV results.
Document Types Accepted
The IDV module accepts government-issued identity documents from 190+ countries. Supported document types include:
- Passports (biometric and non-biometric)
- National identity cards
- Driver's licenses (US, CA, UK, EU, AU, and others)
- Residence permits (US Green Card, EU residence documents)
Liveness Detection
Liveness detection is an active challenge that requires the candidate to perform a brief gesture (e.g., blink or turn head) to confirm physical presence. This prevents the use of printed photographs or replay attacks. Passive liveness is applied to the document side to detect screen captures or photocopies.
Turnaround SLA
Standard checks return results in under 5 minutes. Average turnaround including all retries and manual review escalations is under 24 hours. A check is escalated to manual review when: document quality is insufficient for automated processing, the document is a rare or uncommon type, or liveness confidence falls below threshold.
API Reference
POST /v1/idv/initiate Authorization: Bearer sk_live_... { "candidate_id": "cand_abc123", "loop_id": "loop_xyz789", "document_country": "US" } // Response { "idv_session_id": "idv_session_...", "invite_url": "https://verify.proofglint.com/...", "expires_at": "2026-05-27T23:59:59Z" }
Webhook Events
Proofglint sends webhook events to your configured endpoint for the following IDV events:
idv.initiated— candidate opened the invite linkidv.document_submitted— document uploaded and in processingidv.completed— verification completed (result: verified or review_required)idv.failed— verification failed (liveness failure or document rejection)
Candidate Consent Flow
Before submitting any documents, candidates are presented with a consent screen that explains: what data is collected, how it is used, how long it is retained, and their right to request deletion. Consent is timestamped and stored in the IDV audit log.
Data Retention
Raw document images are deleted after verification completes. The verification result (verified/failed), timestamp, and document type are retained in the audit log per your data retention policy settings (default: 24 months). Candidates may request deletion via the right-to-erasure workflow.