This guide will take you from zero β first live verification in 3 simple steps.
π₯ Want to see it first?
Watch the full console + integration walkthrough here:
β
Step 1 β Create Your Free Didit Account
- Go to business.didit.me
- Sign up with your business email and use the magic login link.
- Create your Organization workspace β where your team will manage workflows, API keys, and all verification activity.
β
Step 2 β Build Your First Verification Workflow
- In the Console β Verifications β Workflows β Create New
- Choose a template:
- KYC β Standard onboarding
- Adaptive Age Verification β Fast selfie check w/ fallback to document
- Biometric Authentication β Password-less selfie login
- Address Verification
- Customize with blocks like Liveness Detection, Face Match, AML, NFC, fallback logic, etc.
β
Step 3 β Configure Webhook & Copy API Key
- Go to Verifications β Settings β API & Webhooks
- Add your Webhook URL (Didit will post live status updates here)
- Copy your API Key (keep it secure β do not expose it in frontend code)
β
Step 4 β Start a Verification Session
β‘ Option A β Verification Links (Fastest)
- In Verifications, click the β+β button and select a workflow.
- Generate a secure link or QR code.
- Send URL via email/SMS β or embed it in your product.
Or programmatically:
POST /v2/session/ { "workflow_id": "your-workflow-id" }
Tip: You can find your
workflow_id
inside the console under
Verifications β Workflows, where all your workflows are listed β simply copy the ID of the one you want to use.
π» Option B β Standalone APIs (Advanced)
Call specific endpoints directly from your backend:
/v2/id-verification/
β ID document check/v2/face-match/
β selfie vs ID/v2/aml/
β compliance lists/v2/passive-liveness/
β deepfake detection- and more ...
Best for fully custom UI / backend-only flows.
β
Step 5 β Receive Real-Time Results
Once a session starts, Didit will send webhook events to your endpoint allowing you to sync data without polling.
We send webhooks for the following event types:
status.updated
: Triggered whenever the verification status changes (e.g., from Not Started to In Progress, or from In Review to Approved). This includes the initial webhook sent when a session starts.data.updated
: Triggered when KYC or POA data is manually updated by a reviewer via the API. This allows you to stay in sync with data corrections or manual reviews.
β
Step 6 β Manage & Monitor in the Console
- View session progress in real time
- Download PDF / CSV reports for compliance
- Blocklist suspicious IDs or faces
- Manually delete or reject sessions

π€ Need Help?
- π¬ WhatsApp (fastest, recommended): Whatsapp
- π§ Email: [email protected]