Skip to main content
This page pairs with the Academy lesson below: a 19-minute screen recording that builds a verification workflow in the real console, from template to published flow, including rules, branching, pricing, and the shareable link.
1

Create your Didit account

  1. Go to business.didit.me
  2. Sign up with SSO or email and password
  3. Create your Organization — this is where your team manages workflows, API keys, and verification activity
2

Build a verification workflow

Navigate to Workflows in the sidebar and click Create New. Choose a workflow type:Pick a template to get started:Customize by toggling blocks: Liveness, Face Match, AML, NFC, Phone, Email, and more.The clip below picks up the Academy lesson at 2:50, where a new workflow is created from a template and configured node by node.
3

Configure webhook and copy API key

Go to API & Webhooks in the sidebar:
  1. Add your Webhook URL — Didit sends status updates here
  2. Copy your API Key — keep it server-side only, never expose in frontend code
  3. Save the destination’s signing secret as DIDIT_WEBHOOK_SECRET in your .env — it’s required to verify the X-Signature-V2 HMAC on incoming webhooks
You can test webhooks directly from this page with different data and statuses — no need to run a full verification. This lets you validate your integration is working correctly before going live.
4

Start a verification session

Option A — Hosted sessions (recommended)Our preferred integration method. Didit A/B tests the hosted flow continuously, so completion rate, speed, and fraud resistance keep improving without you shipping any UI.In the Console, click ”+” → select a workflow → generate a link or QR code. Or create sessions programmatically:
Find your workflow_id under Workflows in the sidebar.
In the integration Academy lesson, this is the 3:36 mark: the create-session call with its one required field, then vendor data and the callback URL.Option B — Standalone APIs (advanced)Call endpoints directly from your backend — no session required. Best for server-to-server or custom flows:See the full list in API Reference.
5

Receive real-time results

Didit sends webhook events to your endpoint — no polling needed.See Webhooks for payload format and signature verification.
6

Manage and monitor

Use the Console to:
  • View session progress in real time
  • Download PDF/CSV reports for compliance
  • Blocklist suspicious IDs or faces
  • Manually update or reject sessions
The Academy lesson on reading results walks a real session check by check: warnings, scores, the event log, webhook deliveries, and the PDF export your compliance team will ask for.

Need help?

WhatsApp

Fastest response — reach us directly.