Skip to main content
Start Didit identity verification for a user who does not yet have a DHMAD account. DHMAD sends a verification email with the Didit link. The Didit session URL is not included in the API response.
Configure allowed redirect URLs in your Developer Dashboard before passing redirect_url. Unlisted URLs return 400.
On sandbox, verifications are auto-approved immediately — no email is sent. See Identity Verifications overview.

Request Body

string
required
Email address for the user. Lowercased on input. Must match the email they will use when registering on DHMAD.
string
Your internal user or seller ID. Returned in webhooks so you can update your database.
string
URL to redirect the user after they complete Didit. Must match one of your allowed redirect URLs in developer settings. Must use HTTPS in production (http://localhost allowed for development).
object
Optional key-value pairs (string values, max 500 characters each). Not returned in webhooks; stored on the verification record.

Response Fields

There is no verification_url field. The Didit link is only delivered by email to the end user.

Duplicate pending sessions

If you POST again with the same developer account and email while a pending session exists, the API returns 200 with the existing record and may resend the invite email (5-minute cooldown between resends).

Error Responses

User already has approved KYC on DHMAD:
Redirect URL not allowed:
Blocked email domain:

After creation, subscribe to identity.verification.updated and identity.verification.linked webhooks. See the Webhooks guide.