Signi Verification — how it works

ℹ️ The new version of Signi Verification (including this API) will be released to production during September 2026. Until then, the calls are not available and the description may change slightly.

Signi Verification is verification of the counterparty's identity before they get to the signature — remote identification for cases where you need to know who is actually signing (AML obligations, remote contracts, HR). The counterparty goes through verification according to the rules you choose, the sender reviews the result, and only then can the counterparty sign.

Signi Verification must be enabled for your workspace — without it, the API returns a 406 error. Arrange this with your contact at Signi.

Verification groups

What exactly the verified person must prove is determined by the verification group — a set of checks (components), e.g. bank identity, identity document, liveness check (selfie), SMS, questionnaire, micropayment, or payment card. A workspace has access to Signi's system groups and possibly its own custom ones.

curl -H "x-api-key: VAS_API_KLIC" https://api.signi.com/api/v2/verifications-groups

[
    {
        "uuid": "11111111-2222-3333-4444-555555555555",
        "name": "AML ověření",
        "isSystem": true,
        "isAml": true,
        "validityPeriodDays": 365,
        "components": ["bankId", "document", "liveliness"]
    }
]

• isAml — the group is set as verification at the AML level, and Signi handles the data accordingly within the data retention policy.
• validityPeriodDays — how long an approved verification remains valid; during that period it can be reused without a new run.
• You can offer the verified person 1–2 groups — they choose which path to verify by (for example bank identity, or document + selfie).

Two ways to create a verification

1. On a document — the most common: you attach counterparty verification to a draft document. The counterparty cannot get to the signature until they are verified. If they already have a valid verification, it is automatically reused.
2. On a contact — verification independent of a document: you verify a contact from the address book "in advance", and the valid verification is then applied to future documents.

Verification statuses

You'll learn about status changes via verification webhooks or by querying the detail.

Where to go next

• Verification on a document — the main scenario: draft → attach verification → send
• Creating a contact verification
• Signi Verification — overview