Skip to main content
GET
Retrieve Session
Retrieves the full details of a single verification session by its session ID, including analysis results and presigned URLs for uploaded documents.

Request

Headers

Path parameters

Example request

Response

200 — Success

Top-level response

Session object

meta_data object

applicantSubmissionLocationDetails object

Derived from a geo lookup of the submission IP. All fields are optional — any field may be absent if the lookup could not resolve it.

failureData object

Tracks per-attempt failures when the workflow has auto-session-failure enabled. Absent until the first failed attempt is recorded. When failedAttempts reaches the workflow’s configured maxAttempts, the session’s top-level status flips to FAILED and session_progress to COMPLETED. Each entry in attempts has the following shape:

declinedData object

Present only when the session was automatically declined by deepidv’s AI identity verification. It records the single decisive reason for the decline. Absent for sessions that passed, are awaiting manual review, or were auto-failed via attempt limits (see failureData — that is a separate, attempt-based mechanism). The full scoring breakdown that drove the decision remains available under analysis_data. The reason object: Reason codes:

analysis_data object

iGaming check data

Each iGaming check writes its result here when it runs, whether as a workflow step or a standalone POST /v1/igaming/* call. Keys inside these objects are snake_case in this response (the live check responses use camelCase evidence keys). A check whose action was block also sets the session’s top-level status to FAILED.

Carrier intelligence data

phone_checks holds the results of the carrier checks, whether they ran as passive workflow steps at session creation or were attached to the session by a standalone call with sessionId (Phone Trust, Carrier Age Gate, Phone Ownership). Keys are snake_case in this response. Carrier checks never change the session’s top-level status on their own.

id_analysis_data object

pep_sanctions_data object

Each match item contains:

compare_faces_data object

document_risk_data object

user / sender_user object

Both user (the applicant) and sender_user (the session creator) share the same shape:

Error responses