> ## Documentation Index
> Fetch the complete documentation index at: https://docs.argyle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Re-verification

> Request updated verification results.

Reuse the existing user when requesting updated results. The next step depends on whether the user's connection is still valid or they need to reconnect or provide new documents.

<a id="instant-refresh" />

## Refresh without user action

<Note>
  The refresh endpoint supports payroll, banking, and Doc VOI verifications. It returns a new verification ID and report.
</Note>

Use [`POST /v2/verifications/refresh`](/api-reference/verifications/refresh-a-verification) to create a **new** payroll or banking verification without the user needing to reconnect, as long as a valid connection is still available. For Doc VOI, use the same endpoint with `report.type = doc-voi-mortgage` to generate a new report from the user's existing uploaded documents without uploading additional documents.

Track the new verification through [`verifications.updated`](/api-reference/verifications-webhooks/updated) webhooks. Retrieve its report when the status reaches `completed` or `completed_with_errors`. See [Verification Statuses](/verifications/verification-statuses).

## Reconnection required

If a previously completed payroll or banking verification needs updated data and the connection is no longer valid, the user must reconnect. The same path applies when the user needs to connect another account.

1. Order a new verification for the existing `user` with [`POST /v2/verifications`](/api-reference/verifications/order-a-verification).
2. Create a [session](/verifications/quickstart#create-a-session) for the new verification.
3. Return the user to [Link for payroll](/verifications/verification-types/payroll#user-experience) or the [banking connection experience](/verifications/verification-types/banking#choose-a-session-type) to complete the required connection steps.
4. Track the new verification's status and retrieve its completed report.

<Note>
  If the verification is still active, create another session for that verification instead. An expired session or a request for MFA does not by itself require a new verification. See [Recovery and Errors](/verifications/recovery-and-errors#session-not-completed).
</Note>

## Doc VOI with new documents

To refresh a Doc VOI report with additional or updated documents, order a new `doc-voi-mortgage` verification for the same `user` with [`POST /v2/verifications`](/api-reference/verifications/order-a-verification). The request shape is the same as a new document verification, including the `employments` requirements.

Previously uploaded documents for the user remain available as the baseline for the new verification. After the new verification is created:

1. Upload each net-new document for the same `user` with [`POST /v2/user-uploads`](/api-reference/user-uploads/upload-a-document).
2. Listen for [`verifications.updated`](/api-reference/verifications-webhooks/updated) webhooks as the verification moves through document processing.
3. Retrieve the refreshed report from `report.file_url` or `report.json_url` when the verification is complete.