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

# Verification links

> Send a person a verification link from the console, without writing code.

A verification link lets anyone on your team start a verification by hand: for a customer on the phone, a prize winner, or someone onboarded outside your product.

## Create a link

1. In **Verifications**, choose **New link**.
2. Pick the **workspace**: its check is what the person will do.
3. Optionally type a **reference**, such as a ticket or order number. It becomes the verification's `external_id`, so you and your systems can find it later.
4. Choose **Create link**.

You get the link, a QR code for the person to scan with their phone, a copy button, and the date the link expires. **Create another** starts over.

## What the person sees

The same hosted verification as any integration: consent, selfie and, depending on the check, their identity document. See [What the person sees](/getting-started/user-verification-journey).

## Follow the result

The verification appears in **Verifications**, findable by its reference. If your workspace has a webhook URL, your systems receive the outcome as for any other verification.

## Limits

* A link nobody starts expires after seven days.
* A live link creates a billable verification once the person submits it; a test link never does.
* Creating links is rate-limited per user.

Everyone on the team can create links, support specialists included. The [MCP server](/integration/mcp/overview) does the same with `create-verification`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.