Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.didit.me/llms.txt

Use this file to discover all available pages before exploring further.

A Verification Link is a unique, secure URL that directs your end user to a verification flow hosted entirely by Didit. You design the verification steps and logic in your Business Console, and Didit handles the user interface, data capture, and security. This allows you to launch a robust verification process in minutes, often with no code required. This method is part of the Orchestrated Workflows integration path, giving you the power of the workflow engine with maximum simplicity.

​
How it works

1

Configure your workflow

In the Didit Business Console, use the no-code editor to design a workflow with the exact sequence of checks you need (e.g., ID Document Scan → Liveness Check → AML Screening). Each workflow has a unique workflow_id.
2

Generate a verification link

Create a unique session for a user. This can be done no-code directly from the Business Console, or low-code via a single API call to the Create Session endpoint.
3

Share the link

Send the generated URL to your user through any channel — email, SMS, in-app message — or embed it in an iframe.
4

Get real-time results

Didit sends automated updates to your configured webhook URL as the user progresses and when the final verification result is ready.

​
Method 1: No-code generation (via Business Console)

The perfect method for getting started instantly, for manual processes, or for teams without developer resources.
  1. Navigate to the Verifications section in your Didit Business Console.
  2. Click + Create Verification.
  3. Select the workflow_id you want to use for this session.
  4. Optionally enter vendor_data (like a user ID from your system) to map the verification back to your user.
  5. A unique URL and QR code are generated instantly.
  6. Copy the link, have the user scan the QR code, or send the link directly to the user’s email.

​
Method 2: Low-code generation (via API)

This method offers full automation and is the standard way to integrate verification links into your application logic. Send a single POST request to the /v3/session/ endpoint with your API key and workflow_id: 
curl --request POST \
     --url https://verification.didit.me/v3/session/ \
     --header 'x-api-key: YOUR_API_KEY' \
     --header 'Content-Type: application/json' \
     --data '{
       "workflow_id": "550e8400-e29b-41d4-a716-446655440000",
       "vendor_data": "your_internal_user_id_123",
       "callback": "https://yourapp.com/didit/webhook/handler"
     }'
The API returns a JSON object containing the session_id and the unique verification url: 
{
  "session_id": "11111111-2222-3333-4444-555555555555",
  "session_number": 1234,
  "vendor_data": "your_internal_user_id_123",
  "status": "Not Started",
  "workflow_id": "550e8400-e29b-41d4-a716-446655440000",
  "callback": "https://yourapp.com/didit/webhook/handler",
  "url": "https://verify.didit.me/session/abcdef123456"
}
Full API details are available in the Create Session API Reference.

Speed to market

Launch a complete, secure, and compliant verification process in hours, not weeks.

No frontend development

Offload the entire user interface — document capture, liveness checks, and user guidance — to Didit’s pre-built UI.

Multi-channel delivery

Send verification requests via email, SMS, support chat, or any other communication channel.

Physical onboarding

Use the QR code for in-person scenarios where a user needs to complete verification on their own device.

​
Next steps

  • Configure your first workflow — head to the Business Console to design your verification journey.
  • Set up your webhooks — learn how to receive real-time status updates in the Handling Webhooks guide.
  • Explore Unilinks — for a reusable, zero-backend alternative, see Unilinks.