Use this when you already have the document: a contract, a quote, a consent form. Nothing needs to come from a form response. If the document should be filled from a response, use a template instead.
Before you start
- Your plan includes signing, and you have not used up this month's allowance. See Plans and allowances. You can prepare a request without either; you just cannot send it.
- Your own email address is confirmed, or the workspace has a verified sending domain. Signers are invited by email, so a request cannot be sent without it.
- You are an editor or an administrator of the workspace.
Steps
- Open Documents and choose New signing request.
- Document. Choose a PDF. It can be up to 20 MB and 100 pages. Formspring checks the file before it can be sent. A file with a password is refused. A file that carries scripts, launch actions or embedded files is quarantined and can never be sent: save a clean copy (print to PDF works) and upload that instead. While the file is checked you can leave the page; the document stays in your library.
- Recipients. Add each person's name and email address. Add a person as a signer, or as a copy who only receives the completed files. Put people in an order if one has to sign before another: see Signing order.
- Fields. Click a page to place a field, assign it to a recipient and choose its type (signature, initials, name, date, checkbox, text). Drag it into place, or type the page and the position if you prefer the keyboard. Every signer needs at least one signature field. Mark a field as required where it is.
- Settings. Choose the deadline (30 days from sending unless you change it, up to 365), whether signers may ask you to hand the request on, and the title.
- Review. Preview the document as each signer will see it. Check the summary: who sends, which version, how many fields, who signs and who gets a copy, the deadline, and what the request uses of your allowance. Anything that blocks sending is listed with the step that fixes it.
- Choose Send for signature.
What happens when you send
Sending freezes the package, so nothing in it can be changed afterwards, reserves one request from your allowance, and queues the invitations for the people whose turn it is. The request page shows each recipient's delivery state separately from the state of the request. It does not say a recipient received or read the mail until the mail service reports it, and an opened email is never treated as review.
Pressing Send for signature twice, or retrying a failed call, sends one request and uses the allowance once.
If something goes wrong
| What you see | What to do |
|---|---|
| The document is quarantined or refused | Upload a clean copy. A quarantined file can never be sent. |
| A signer has no signature field | Add one on the Fields step. |
| Two fields overlap or sit outside the page | Move one. The editor shows which. |
| The allowance is used up | Wait for next month or change plan. Prepared drafts are kept. |
| Sending is paused for the workspace | A complaint paused new requests. Existing records and requests are untouched. Contact support. |
| The request changed while you were reviewing | Reload and review the current version. Nothing was sent with the old one. |
A draft that is not ready stays a draft. It is removed only under the retention rules for drafts: see Retention.
For developers
POST /api/v1/documents/upload uploads the PDF, POST /api/v1/documents/{document}/requests creates the draft, PUT /api/v1/signing-requests/{id}/fields places the fields, GET /api/v1/signing-requests/{id}/readiness lists what blocks sending, and POST /api/v1/signing-requests/{id}/send sends it. Send with expected_version (the version you last read) and an Idempotency-Key header, so a retry sends once. See Electronic signing.
