Trust

How agent-sent envelopes are recorded

An agent or the REST API initiates the send. The human signer consents. The audit trail is the same stack used when a person sends from the dashboard.

Not legal advice

Not legal advice. zSign is not a law firm and does not provide legal advice. We do not guarantee that any signature or document will be enforceable in every jurisdiction or for every document type. The sender is responsible for determining whether electronic signature is appropriate. See Terms and Privacy.

Mechanics

Initiate → consent → audit trail → certificate

Agent initiates

send_envelope or POST /api/v1/documents/send creates the envelope. The agent is the sender’s software, not the signer.

Signer consents

The recipient reviews the document and consents to sign electronically before ink is applied. zSign does not treat the agent’s send as the signer’s consent.

Audit trail

Each envelope records IP address, view and signature timestamps, consent, and a SHA-256 hash of the document — the same fields as a human-sent envelope.

Completion certificate

A completed envelope ships with a tamper-evident completion certificate. Teams sometimes call this court-ready evidence — that phrase is descriptive of the artifact, not a promise that a court will enforce any particular document. See the disclaimer on this page.

Eligibility

Some documents are not eligible

Examples that may not be eligible for electronic signature include wills and certain notarized instruments. That list is not exhaustive. Whether electronic signature is appropriate is the sender’s call.