The signing experience

What signers see, how they are identified, access codes, branding, white-label, and what happens after they sign.

What signers see

A signer opens their link and sees who sent it, the message, the deadline and the documents, with their fields marked by a yellow "Sign here" flag. "Next field" takes them through each one. They draw or type a signature, tick the agreement to sign electronically, read the intent statement, and select Sign. It works on phones and needs no account, app or password.

Access codes

Add access_code to a signer and they must enter it before they can see anything about the document. Give them the code another way, by phone, SMS or in person: it identifies them by more than holding the link. It is the recommended way to send links you hand over yourself (delivery: "link").

"signers": [{ "name": "Ava Chen", "delivery": "link", "access_code": "4821" }]

Five wrong codes lock the link for 15 minutes. The code is stored as a hash, never as typed, and a correct entry is recorded in the audit trail.

Declining

A signer can decline with a reason. The envelope becomes declined, nobody else can sign, the sender is emailed, and envelope.declined fires.

After they sign

Once everyone has signed, each signer is emailed a link to the signed PDF, and their signing link keeps working to download it and the certificate. With redirect_url, signers go to your site a few seconds after signing.

Your branding

Under Settings, Branding (or PATCH /v1/settings) set the name signers see, a PNG logo, and a brand colour as a hex code (#2340c8, 2340c8 or #24c). The colour is used for the Sign button and the email button; the app warns if white text on it would be hard to read.

White-label

With whitelabel: true, squiggli's name appears nowhere signers look: not on the signing page, not in emails, not on the PDF footer or certificate. Your name, logo and colour only. White-labelled envelopes are $1.50. Set whitelabel_default in settings to make it the default.

Emails