Verification lists (API)

Modified on Thu, 22 Oct at 4:46 PM

For every completed verification, Signi generates a verification list — a sealed PDF with an audit record of the entire process. This is your proof in case of an inspection (e.g. under the AML Act).

Verification list of a single verification

curl -H "x-api-key: VAS_API_KLIC" \
  https://api.signi.com/api/v2/verifications/UUID_OVERENI/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 list isn't sealed yet (it's being generated in the background), the call returns 400 — try again in a moment.

Verification lists for an entire document

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

curl -H "x-api-key: VAS_API_KLIC" -o kontrolni-listy.zip \
  https://api.signi.com/api/v2/docs/UUID_DOKUMENTU/verifications/revision-lists

Shredding

Personal data from verifications doesn't stay in Signi forever — once the retention period expires, the verification list is shredded. The call then returns 410:

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

Instead of the verification list, you receive a destruction certificate — a sealed proof that the data was properly disposed of (destructionListUrl may be null for a while, until the certificate is generated). For this reason, download your verification lists and archive them yourself while they are available.

Where to go next

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article