The Create Session API allows you to generate a URL for a specific workflow where your users can start verifying their identity.
A unique identifier for the vendor or user, such as a UUID or email. This field enables proper session tracking and user data aggregation across multiple verification sessions.
URL to redirect the user after verification completes. Didit automatically appends verificationSessionId and status (Approved, Declined, In Review) as query parameters.
Determines which device should handle the redirect to the provided callback URL. Use initiator to redirect only the device that started the flow, completer for the device that finishes it, or both to allow either device to trigger the callback. If you ever notice the callback not triggering reliably, we recommend setting this value to both.
initiator, completer, both Additional data to store with the session not displayed to the user. For example: {"user_type": "premium", "account_id": "ABC123"}.
Language code (ISO 639-1) for the verification process interface. Controls the language displayed to the end user during verification. If not provided, the browser's language will be automatically detected and used. Check all the supported languages here.
en, ar, bg, bn, ca, cnr, cs, da, de, el, es, et, fa, fi, fr, he, hi, hr, hu, hy, id, it, ja, ka, ko, lt, lv, mk, ms, nl, no, pl, pt-BR, pt, ro, ru, sk, sl, so, sr, sv, th, tr, uk, uz, vi, zh-CN, zh-TW, zh User contact information that can be used for notifications, prefilling verification forms, and phone verification. This includes email address, preferred language for communications, and phone number.
Expected user details for cross-validation with extracted verification data.
A Base64 encoded portrait image of the user's face, with a maximum size of 1MB. This image is only required for Biometric Authentication workflow types that have face match active to perform facial matching against the face captured during the liveness check.
Created
Unique identifier for the session.
Sequential number assigned to the session.
Token used to access the verification flow URL.
Identifier provided by the vendor for tracking.
Additional data associated with the session.
Current status of the verification session.
Identifier of the workflow used for the session.
Callback URL to redirect the user after completion.
URL for the user to complete the verification flow.