Signi verification — how it works (API)

Signi verification is verifying the counterparty's identity before they get to sign — 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; once they complete the checks, they can sign. The sender independently reviews the result and approves or rejects it.

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 person being verified 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 Signi's system groups available, and possibly 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 AML-level verification, and Signi handles the data accordingly within its 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 person being verified 1–2 groups — they choose which path to verify with (for example bank identity, or document + selfie).

Two ways to create a verification

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

Verification statuses

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

Where to go next

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