This resource has a few variations that can be encountered when
using the API.The fields that are part of the base variant represent
the default fields that are always returned when using the
fields
query parameter, additional to the fields specified in the
parameter.example:
trueReminds signers to sign a document on day 3, 8, 13 and 18. Reminders are only sent to outstanding signers.example:
trueDisables the usage of signatures generated by typing (text).example:
2Set the number of days after which the created signature request will automatically expire if not completed. By default, we do not apply any expiration date on signature requests, and the signature request does not expire.example:
https://declined-redirect.comThe uri that a signer will be redirected to after declining to sign a document.example:
Hello! Please sign the document belowMessage to include in sign request email. The field is cleaned through sanitization of specific characters. However, some html tags are allowed. Links included in the message are also converted to hyperlinks in the email. The message may contain the following html tags including a, abbr, acronym, b, blockquote, code, em, i, ul, li, ol, and strong. Be aware that when the text to html ratio is too high, the email may end up in spam filters. Custom styles on these tags are not allowed. If this field is not passed, a default message will be used.example:
Sign Request from AcmeSubject of sign request email. This is cleaned by sign request. If this field is not passed, a default subject will be used.example:
123This can be used to reference an ID in an external system that the sign request is related to.example:
BoxUsed as an optional system name to appear in the signature log next to the signers who have been assigned the embed_url_external_id.example:
trueIndicates if the sender should receive a prepare_url in the response to complete document preparation using the UI.example:
nameName of the signature request.The destination folder to place final, signed document and signing
log. Only
ID and type fields are required. The root folder,
folder ID 0, cannot be used and can also not be null.When this value is not passed in when the signature request, then
we will use a default folder which is either the parent folder of
the first source file in the payload if we have the permission to
upload to that folder or a folder called “My Sign Requests”.When a document contains sign-related tags in the content, you can prefill them using this
prefill_tags by referencing the ‘id’ of the tag as the external_id field of the prefill tag.example:
https://www.example.comWhen specified, the signature request will be redirected to this url when a document is signed.example:
blueForce a specific color for the signature (blue, black, or red).Value is one of blue,black,redArray of signers for the signature request. 35 is the
max number of signers permitted.Note: It may happen that some signers belong to conflicting segments (user groups).
This means that due to the security policies, users are assigned to segments to prevent exchanges or communication that could lead to ethical conflicts.
In such a case, an attempt to send the sign request will result in an error.Read more about segments and ethical walls.
List of files to create a signing document from. This is currently limited to ten files. Only the ID and type fields are required for each file.
example:
123075213-af2c8822-3ef2-4952-8557-52d69c2fe9cbWhen a signature request is created from a template this field will indicate the id of that template.