Create Box Sign request
Creates a signature request. This involves preparing a document for signing and sending the signature request to signers.
Authorizations
Body
Creates a Box Sign request object.
Array 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.
Message 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, 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.
"Hello! Please sign the document below"
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.
10The bare basic representation of a file, the minimal amount of fields returned when using the fields query parameter.
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".
Response
Returns a Box Sign request object.
A Box Sign request object.
Message 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, 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.
"Hello! Please sign the document below"
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.
The bare basic representation of a file, the minimal amount of fields returned when using the fields query parameter.
The destination folder to place final, signed document and signing log.
When this value was not passed in when the signature request was created, 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".
