Signature

Use cases

The last step an automation could not take.

Every one of these is a workflow that used to stop dead at “now email it to someone and wait”.

For an agent that got all the way to the end

Close the deal it negotiated

Your agent worked out the terms and drafted the statement of work. `paperwork` typeset it. `handoff` got a person to approve it. Neither of those can get a name on the line — that was the gap. One call here sends it, and the agent polls for free until it comes back executed.

  1. 01Draft the SOW, render it, or pass the markdown straight through
  2. 02POST the document plus both signers, with an order if the countersignature must come second
  3. 03Poll the status URL until it reads executed
  4. 04Store the executed PDF and the audit JSON against the deal

For an operations workflow

Onboard a contractor with nobody in the loop

A new contractor lands in your system. The workflow posts the agreement here with their address, watches the status, and files the executed copy against their record. No tab is opened and no template is uploaded to a portal.

  1. 01Fill your agreement template and hand it over as base64 or a URL
  2. 02Send it — 15 credits — and record the envelope id
  3. 03The contractor signs in a browser, with no account and no app
  4. 04Your webhook fires once; the executed PDF is a free download from then on

For a two-party agreement

Make the countersignature a real step

Give the signers an order and the second is only invited once the first has signed. That is how a counterparty and a countersignatory actually behave — not two people racing the same document and hoping the certificate makes sense afterwards.

  1. 01Signer one at order 1, signer two at order 2
  2. 02Only signer one is invited; the second link does not exist yet
  3. 03When one signs, two is invited automatically with a fresh token
  4. 04The certificate lists them in the order they actually signed

For consent and acknowledgement

Keep something you can point at

A waiver, a permission, a policy acknowledgement. What you get back is not merely a yes — it is a record of which exact bytes they were shown, when they first opened them, from what address, and what they typed.

  1. 01Send the notice as markdown and let it be typeset
  2. 02One signer, a short expiry window
  3. 03The audit trail records the first open separately from the signature
  4. 04The document hash on the certificate proves what they saw

Where it does not belong

Signature produces an executed record with an audit trail. It is not legal advice and makes no claim of ESIGN, UETA or eIDAS qualification. Signer identity is not verified.

If your matter needs a qualified electronic signature, a notary, a witness, or verified identity, this is the wrong product and we would rather say so here than after you had signed something with it.

Read the API15 to send, 10 on execution