ℹ️ 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 = verifying the counterparty's identity before signing (remote identification, AML). This section describes control via the API; for how the feature looks in the Signi app, see the user documentation What is Signi verification and what is it for.
Articles in this section:
- Signi verification — how it works — principles: verification groups and their checks, statuses, validity, two ways of creation.
- Verification with a document — main scenario: draft document → linking verification to the counterparty → sending; recycling valid verifications.
- Creating a contact verification — verification independent of a document, detailed results by component, contact history.
- Approving and rejecting a verification — proposer's review via API, a new attempt for the verified person (
spawnRetry). - Verification webhooks —
verification.*events, message signing (HMAC), default workspace subscriptions. - Verification sheets — a sealed record of the process, a ZIP for the entire document, shredding and shredding certificate.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article