Safer E-Signatures

Each signer can now only fill in the fields their signature request asks them to fill in, and the signing form shows every other field read-only, as the PDF will print it: other signers' values, combined fields with their full text, and images from URLs. Signed PDFs always come out flattened, with no editable form fields.

What signers see is what the PDF prints

• DocSpring saves only the fields a signer was asked to fill in. Values for any other field are ignored, whatever the signing page sends.
• Images that you send as URLs are downloaded when you create the submission. The signer sees that copy and the PDF prints the same one, so the image can't change after signing.
• Two signers finishing at the same time now always produce one signed PDF.

API changes

• The API rejects signature and initials values in the data of a submission with signature requests: only the signer signs.
• On a public template, only the template's own account can choose signers, replace the HTML, set a password, an expiry or editable, or override what a field prints. Other accounts can still create submissions.
• The signature request events API only takes send_request events, and a completed, declined or expired signature request takes no more changes from the API. Events you post are shown in the audit trail as reported by your account.
• Test API tokens can't create tokens or events for a live signature request.
• A submission with signature requests can't be reprocessed, and a published template version's PDF can't be replaced.
• API v2 refuses a signature request whose template has a formula or a show/hide rule that uses another signer's fields.
• With "Include submission data" turned off, webhooks also leave out each signer's values, IP address and user agent.

Signing links expire

• A signing link opens the form for 24 hours, or 7 days for a token you create for an email. If the signer opens it in time, they have 7 more days to finish in that page. After that, the page asks them to get a new link from you.
• Links you created before this change expire the same way, counted from when you created them.
• Signing pages ask search engines not to index them, and don't send their address to other sites.

Signature Requests JS 3.0.0

Data Requests JS is now Signature Requests JS 3.0.0, with new names for its function and options. Pages that load 2.x keep working on the sites in Embed Domains.

• A live signature request only opens on the sites in the template's Embed Domains setting, and the browser enforces it, whichever version opens it. The domainVerification option is gone, and in 2.x it no longer lets a live signature request open on another site. A test signature request opens on any site.
• onError always gets an object with an error code and a message, including when the browser won't show the form (frame_blocked), the link has expired (token_expired) or the PDF failed.
• setField, submitForm, defaultFormData and staticFormData are gone: send the values when you create the submission.

Read more in the Signature Requests JS changelog, Create Signature Requests and Embedded Signature Requests.