v1
latestSwagger 2.02026-08-063530171.1 KBForward a SignRequest to a different signer by email
Request body
Email of the signer that forwards the SignRequest.
Email of the new signer to forward this SignRequest to.
A reason why this SignRequest is forwarded (optional), this will be visible to all parties involved
Response
Updated SignRequest instance
Email of user sending the SignRequest (must be a validated email)
Name to be used in the From email header, e.g. {from_email_name} <no-reply@signrequest.com>
Have the sender of a SignRequest prepare the document before sending the request out, see: prepare using the web interface
URL at which SignRequest will redirect to when a document is signed
URL at which SignRequest will redirect to when a document is declined
Disable uploading/adding of attachments
Disable usage of signatures generated by typing (text)
Disable adding of text
Disable adding of dates
Disable all SignRequest status emails as well as the email that contains the signed documents
Disable usage of uploaded signatures (images)
Force specific color for the signature
Disables storing timestamp proof hashes in blockchain integrations.
When true a text message verification is needed before the signer can see the document
Subject of SignRequest email
Message to include in SignRequest email, may contain the following html tags: a, abbr, acronym, b, blockquote, code, em, i, ul, li, ol, and strong
m: only me, mo: me and others, o: only others
Automatically remind signers to sign a document, see: automatic reminders