Verify any signed document by token or hash.

Every document completed through Docuplete can be independently verified. Provide the document's unique token or SHA-256 hash to confirm authenticity, view submission details, and check tamper status — no account required.

Start free trial See live demo →

How it works

What you get with this feature.

Verify by unique document token or SHA-256 hash
Confirms the document is genuine and unmodified since generation
Returns submission details: signer, timestamp, and document package name
Verification available via the Docuplete API for programmatic access
No Docuplete account required to verify a document
Token and hash printed on every signing certificate page

Details

Everything to know.

Two verification methods

Every Docuplete document has a unique token and a SHA-256 hash. Either can be used to verify the document — via the verification endpoint or directly through the API.

What verification confirms

Verification returns: whether the document is authentic, whether it has been modified since generation, the submission timestamp, and the signer's verified email address.

Printed on the certificate page

The document's unique token and SHA-256 hash are printed on the signing certificate page appended to every completed PDF — making verification possible from the document alone.

API access

Developer and Enterprise plans can verify documents programmatically via the Docuplete REST API — useful for automated compliance checks or downstream workflow validation.

No account required

A counterparty, auditor, or regulator can verify a Docuplete document without a Docuplete account. The verification endpoint is publicly accessible.

Combined with trusted timestamps

Verification also confirms the RFC 3161 trusted timestamp — providing independently verifiable proof of when the document was signed, not just whether it is authentic.