Verification Records

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

Every completed verification has a Signi verification record — a sealed PDF with an audit trail of the entire process. This is your proof for any potential inspection (e.g., under the AML law).

Verification record for a single verification

curl -H "x-api-key: YOUR_API_KEY" \
  https://api.signi.com/api/v2/verifications/VERIFICATION_UUID/revision-list

{ "url": "https://…(signed link to the PDF)…" }

The link is signed and time-limited — download the PDF right away. As long as the verification record is not yet sealed (it is generated in the background), the call returns 400 — try again in a moment.

Verification records for an entire document

With a single call you can download a ZIP containing the verification records of all document counterparties that had a linked verification:

curl -H "x-api-key: YOUR_API_KEY" -o verification-records.zip \
  https://api.signi.com/api/v2/docs/DOCUMENT_UUID/verifications/revision-lists

Destruction

Personal data from a verification does not stay in Signi forever — once the retention period expires, the verification record is destroyed. The call then returns 410:

{
    "error": "PURGED",
    "message": "…",
    "destructionListUrl": "https://…(link to the destruction certificate)…"
}

Instead of the verification record, you receive a destruction certificate — a sealed document proving that the data was properly disposed of (destructionListUrl may be null for a while until the certificate is generated). For this reason, download and archive the verification records on your side while they are still available.

Where to go next

• Signi Verification — how it works