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/operational review scenarios:
- You won’t build or manage the Create Session API yet.
- You need a ready-to-use link that just works.
- You’ll share the link via:
- Email / SMS / WhatsApp
- QR codes (in-store, branch, on devices)
- A simple button on your website
Perfect for:
- Low-code / no-code teams
- Manual operations (analyst console review, record matching)
- MVPs and pilots
- Simple onboarding flows
- Affiliate / referral verification
- In-person KYC (QR in store or branch)
When not to use Unilink ⚠️
Skip Unilink if you need any of the following—use the 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, doc type)
- High-volume, highly customized enterprise orchestration
Unilink vs API — Quick comparison
| 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 |
Simple rule of thumb
- If you want speed & simplicity → Unilink
- If you want control & automation → API integration
How to use Unilink
- Configure a Workflow in Business Console (steps, liveness/AML, branding).
- Copy the Unilink (unique per workflow).
- Distribute it:
- Button on your website
- Email/SMS/WhatsApp
- Printed or on-screen QR code
- Operators review results in Console and match to internal records.
Example: Website button
<a class="btn btn-primary"
href="https://verify.didit.me/verify/UNILINK_TOKEN"
rel="noopener"
target="_blank">
Verify your identity
</a>Best practices
- Start with Unilink for manual ops and MVPs; evolve to Create Session as automation needs grow.
- Sandbox vs Live: test with sandbox keys/links; swap for production at go-live.
- Security: if you expose the link publicly, consider bot-mitigation on the host page.
- Webhooks (API paths): verify signatures, retry on failure, and store event history if you automate later.