Get User
Fetch one user by vendor_data (exact match). Adds metadata, comments, and updated_at to the list view, and switches tags to the detailed tag-link shape. Returns soft-deleted users too.
Overview
Returns a single User entity keyed byvendor_data. Responses include didit_internal_id — Didit’s stable internal identifier.
When to use it
- Lookup a user’s current verification state — the
featuresmap gives you the latest status of every feature in a single object. - Detail views in your own UI — pull the profile on demand before rendering.
- Risk scoring — combine session counters and
featuresto score each user on your side.
Notes
vendor_datain the URL is case-sensitive.- Returns
404if no user with thatvendor_dataexists in the application. - Aggregate counters (
session_count,approved_count,declined_count,in_review_count) update in real time as sessions complete. - See the User data model for every field.
Permissions
Role must grantread:users.
Related
Authorizations
Path Parameters
Your unique identifier for the user — a free-form string (NOT a UUID). This is the same value you passed as vendor_data when creating the session that first introduced this user, matched exactly as sent.
Response
Full user detail including metadata, comments/activity log, and aggregated session data.
Full user detail. Extends UserListItem with metadata, comments, and updated_at.
Didit's stable internal UUID for this user.
Your unique identifier for this user (passed when creating sessions). This can be null when no vendor identifier was supplied.
Custom display name set by you
Full name extracted from verified documents
Best available name: display_name if set, otherwise full_name
Lifecycle status of the user record (NOT a session status). ACTIVE is the default, FLAGGED marks the user for manual attention, BLOCKED prevents new sessions for this vendor_data.
ACTIVE, FLAGGED, BLOCKED Presigned URL of the user's portrait photo (expires after a few hours)
Total number of verification sessions for this user
Number of approved sessions
Number of declined sessions
Number of sessions in review
ISO 3166-1 alpha-3 codes of issuing countries seen on this user's approved ID documents, e.g. ["USA", "ESP"]. Empty array when none.
Verified email addresses collected from this user's approved sessions, e.g. ["john@example.com"].
Verified phone numbers collected from this user's approved sessions, e.g. ["+14155551234"].
Aggregated per-feature status across all of this user's sessions. Possible keys: ID_VERIFICATION, NFC, LIVENESS, FACE_MATCH, POA, QUESTIONNAIRE, EMAIL_VERIFICATION, PHONE, AML, IP_ANALYSIS, AGE_ESTIMATION, DATABASE_VALIDATION. Possible values: Approved, Declined, In Review, Not Finished, Resub Requested.
Same data as features, as an ordered array of {feature, status} objects.
Timestamp of the most recent session
Timestamp of the first session
Timestamp of the most recent activity on this user (session, transaction, status change, data edit, etc.).
Tag assignments. NOTE: on detail responses each entry is a tag link object ({uuid, tag: {...}, added_by_email, added_by_name, created_at}), unlike the flat {uuid, name, color} shape used on list responses.
Custom metadata JSON you attached to this user. Defaults to {}.
Activity log and comments for this user (status changes, profile edits, manual notes).