--- title: "Retrieve a Document Verification" method: GET path: "/verification/documents/{verification-id}" tags: ["documentVerifications"] --- # Retrieve a Document Verification `GET /verification/documents/{verification-id}` ## Request - Base URL: `https://api.withpersona.com/api/v1` - URL: `https://api.withpersona.com/api/v1/verification/documents/{verification-id}` - Auth: HTTP bearer Retrieves the details of a specific document verification ## Path parameters - `verification-id` string, required ## Query parameters - `include` string - `fields` object ## Headers - `Key-Inflection` 'camel' | 'kebab' | 'snake' - `Idempotency-Key` string - `Persona-Version` '2026-09-29' | '2025-12-08' | '2025-10-27' | '2023-01-05' | '2022-09-01' | '2021-08-18' | '2021-07-05' | '2021-02-21' | '2020-05-18': Server API version. More info on versioning can be found [here](https://docs.withpersona.com/versioning). ## Response `200` This endpoint returns a Document Verification object and (optionally) its related objects in `included`. - DocumentVerificationsRetrieveADocumentVerificationResponse200 - `data` VerificationDocument, required: A Document Verification - `id` string: The token of the verification - `attributes` VerificationDiscriminatorMappingVerificationDocumentAttributes - `status` string: The status of the verification Possible values: - initiated - submitted - tentatively_passed (only for `verification/document` and `verification/qes-infocert`) - tentatively_failed (only for `verification/database-business` and `verification/database-business-footprint`) - passed - failed - requires_retry - skipped - canceled - confirmed (only for `verification/email-address` and `verification/phone-number`) Do not assume this is a static enumeration; Persona may add new values in the future without a versioned update. - `created-at` string, date-time: The time the verification was created in ISO 8601 format - `created-at-ts` integer: The time the verification was created in Unix timestamp format - `submitted-at` string, date-time, nullable: The time the verification was submitted in ISO 8601 format - `submitted-at-ts` integer, nullable: The time the verification was submitted in Unix timestamp format - `completed-at` string, date-time, nullable: The time the verification was completed in ISO 8601 format - `completed-at-ts` integer, nullable: The time the verification was completed in Unix timestamp format - `redacted-at` string, date-time, nullable: The time the verification was redacted in ISO 8601 format - `country-code` string, nullable: ISO 3166-1 alpha 2 country code. - `tags` string[]: Tags on the verification - `checks` VerificationSharedAttributesChecksItems[] - `name` string - `status` string: Possible values: - passed - failed - not_applicable Do not assume this is a static enumeration; Persona may add new values in the future without a versioned update. - `category` string, nullable: The category assigned to the check. Possible values include: - biometrics - fraud - user_action_required - validity This categorizes the check itself, not its outcome. A null category means the check is uncategorized or its category is unknown; it must not be interpreted as non-fraud. Do not assume this is a static enumeration; Persona may add new values in the future without a versioned update. - `reasons` string[]: If applicable, reasons are the list of reasons explaining why the check failed or is not applicable. For some checks, `reasons` is the primary signal carrying the underlying detection results. For example, `business_website_malicious_website_detection` surfaces its IPQS and Google Web Risk signals here (e.g. `malware`, `phishing`, `spam-source`) rather than in `metadata`. - `requirement` string: Possible values: - required - not_required - requires_retry Do not assume this is a static enumeration; Persona may add new values in the future without a versioned update. - `metadata` object: This is a free-form object containing relevant metadata to the processing and result of the check. - `fields` VerificationDiscriminatorMappingVerificationDocumentAttributesFields: JSON key-value pairs of field name to field value. - `files` File[]: The files uploaded to the associated document for processing. - `filename` string - `url` string - `byte-size` integer - `files-normalized` File[] - `filename` string - `url` string - `byte-size` integer - `extraction-responses` ExtractionResponsesItems[], nullable: A list of extractions resulting from processing the uploaded documents corresponding to the document's extraction configuration. - `extraction-type` string - `field-name` string - `structured-results` object[]: A list of structured AI extraction results with locations stripped. Values are recursive — objects contain nested structured results — but bounding-box location data is omitted from the API response. - `results` ExtractionResponsesItemsResultsItems[]: A list of objects containing the actual value extracted and additional information relevant to the extraction result. - `value` string - `page` integer: The page number the extraction result is detected. Page is 1-indexed. - `match-level` string: If extraction-type is guided, match-level describes the degree in which the extracted value is similar to the source value. Otherwise the match-level is full. - `metadata` ExtractionResponsesItemsResultsItemsMetadata: This is a free-form object containing potentially helpful metadata on the extraction result. - `document-type` string, nullable: Document classification assignment based on document content. - `relationships` VerificationDiscriminatorMappingVerificationDocumentRelationships - `inquiry` VerificationSharedRelationshipsInquiry: The inquiry linked to the verification - `data` VerificationSharedRelationshipsInquiryData - `id` string - `type` 'inquiry' - `template` VerificationSharedRelationshipsTemplate - `data` VerificationSharedRelationshipsTemplateData - `type` 'template' - `id` string - `inquiry-template-version` VerificationSharedRelationshipsInquiryTemplateVersion - `data` VerificationSharedRelationshipsInquiryTemplateVersionData - `type` 'inquiry-template-version' - `id` string - `inquiry-template` VerificationSharedRelationshipsInquiryTemplate - `data` VerificationSharedRelationshipsInquiryTemplateData - `type` 'inquiry-template' - `id` string - `transaction` VerificationSharedRelationshipsTransaction - `data` VerificationSharedRelationshipsTransactionData - `type` 'transaction' - `id` string - `verification-template` VerificationSharedRelationshipsVerificationTemplate - `data` VerificationSharedRelationshipsVerificationTemplateData - `type` string - `id` string - `verification-template-version` VerificationSharedRelationshipsVerificationTemplateVersion - `data` VerificationSharedRelationshipsVerificationTemplateVersionData - `type` string - `id` string - `accounts` VerificationSharedRelationshipsAccounts - `data` VerificationSharedRelationshipsAccountsDataItems[] - `id` string - `type` 'account' - `document` VerificationDiscriminatorMappingVerificationDocumentRelationshipsDocument - `data` VerificationDiscriminatorMappingVerificationDocumentRelationshipsDocumentData - `id` string - `type` string ## Other responses - `400`: The request was unacceptable, often due to invalid parameters. - `401`: An invalid API key was provided. - `403`: The given API key doesn’t have permissions to perform the request or a quota has been exceeded. - `404`: The requested resource doesn’t exist. - `429`: Your organization’s rate limit has been exceeded. We recommend an exponential backoff on requests. --- [API](https://skmtc.dev/withpersona/apis/withpersona-8.md) - [All operations](https://skmtc.dev/withpersona/apis/withpersona-8/llms.txt) - [OpenAPI document](https://skmtc.dev/withpersona/apis/withpersona-8/revisions/3683a7f9e1fe?raw)