Edits a SignatureRequest based on the given Template(s) to be signed in an embedded iFrame. Note that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
NOTE: Edit and resend will deduct your signature request quota.
Your API key can be used to make calls to the Dropbox Sign API. See Authentication for more information.
✅ Supported by Try it console (calls sent in test_mode only).
Use template_ids to create a SignatureRequest from one or more templates, in the order in which the template will be used.
Add Signers to your Templated-based Signature Request.
Allows signers to decline to sign a document if true. Defaults to false.
Use files[] to indicate the uploaded file(s) to send for signature.
This endpoint requires either files or file_urls[], but not both.
Use file_urls[] to have Dropbox Sign download the file(s) to send for signature.
This endpoint requires either files or file_urls[], but not both.
Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer’s order number for look up when receiving events for the signature request.
Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.
This allows the requester to specify the types allowed for creating a signature and specify another signing options.
NOTE: If signing_options are not defined in the request, the allowed types will default to those specified in the account settings.
NOTE: If force_advanced_signature_details is set, allowed types has to be defined too.
Whether this is a test, the signature request will not be legally binding if set to true. Defaults to false.
Controls whether auto fill fields can automatically populate a signer’s information during signing.
NOTE: Keep your signer’s information safe by ensuring that the signer on your signature request is the intended party before using this feature.
You can use an Access Token issued through an OAuth flow to send calls to the Dropbox Sign API from your app. The access scopes required by this endpoint are listed in the gray box above. See Authentication for more information. ❌ Not supported by Try it console.
