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

# Unilinks

> Launch identity verification without code using Didit Unilinks — one reusable URL per workflow. Share via email, SMS, QR code, or button for instant KYC.

**Unilink** is a single, reusable link per workflow that starts the hosted Didit verification flow — no backend required. Put it behind a button on your site, send it to users, or print it as a **QR code**. Each visit spins up a session for that workflow; results are visible in the **Business Console** for manual review.

***

## When Unilink is the right choice

Choose **Unilink** when you want **zero backend integration** and **maximum speed to market**, especially for manual or operational review scenarios:

<CardGroup cols={2}>
  <Card title="Low-code / no-code teams" icon="wand-magic-sparkles">
    No API integration or backend setup needed.
  </Card>

  <Card title="MVPs and pilots" icon="flask">
    Validate your verification flow before investing in a full integration.
  </Card>

  <Card title="In-person KYC" icon="qrcode">
    Use the QR code in-store, at a branch, or on a kiosk.
  </Card>

  <Card title="Affiliate or referral verification" icon="share-nodes">
    Share the link via email, SMS, or WhatsApp.
  </Card>
</CardGroup>

***

## When NOT to use Unilink

Skip Unilink if you need any of the following — use the [API (Create Session)](/sessions-api/create-session) instead:

* **Deep backend control** over sessions and lifecycle
* **Fully automated** user journey (no manual steps)
* **Silent** or background checks
* **Dynamic workflows** based on user attributes
* **Complex conditional logic** (branching by country, risk, document type)
* **High-volume, highly customized** enterprise orchestration

***

## Unilink vs API

| Use case                          | Best option |
| --------------------------------- | ----------- |
| Quick launch / MVP                | **Unilink** |
| No backend                        | **Unilink** |
| Send a link to a user             | **Unilink** |
| QR verification (kiosk / branch)  | **Unilink** |
| Manual operator review in Console | **Unilink** |
| Fully custom flow                 | **API**     |
| Backend automation                | **API**     |
| Conditional risk logic            | **API**     |
| Mass scale with per-user context  | **API**     |

<Info>
  **Simple rule of thumb:** if you want **speed and simplicity**, choose Unilink. If you want **control and automation**, choose the API integration.
</Info>

***

## How to use Unilink

<Steps>
  <Step title="Configure a workflow">
    In the **Business Console**, set up your verification steps, liveness/AML checks, and branding.
  </Step>

  <Step title="Copy the Unilink">
    Each workflow has a unique Unilink. Copy it from the workflow settings.
  </Step>

  <Step title="Distribute">
    Share the link via:

    * A button on your website
    * Email / SMS / WhatsApp
    * Printed or on-screen QR code
  </Step>

  <Step title="Review results">
    Operators review results in the **Console** and match to internal records.
  </Step>
</Steps>

### Example: website button

```html theme={null}
<a class="btn btn-primary"
   href="https://verify.didit.me/verify/UNILINK_TOKEN"
   rel="noopener"
   target="_blank">
  Verify your identity
</a>
```

***

## Best practices

1. **Start with Unilink** for manual ops and MVPs; evolve to [Create Session](/sessions-api/create-session) as automation needs grow.
2. **Sandbox vs. Live** — test with sandbox keys/links; swap for production at go-live.
3. **Security** — if you expose the link publicly, consider bot-mitigation on the host page.
4. **Webhooks** — verify signatures, retry on failure, and store event history if you automate later. See the [Webhooks guide](/integration/webhooks).