Is there an eSign Rest API available that can be used to disable sending the completed document as an attachment when the workflow is completed for specific envelopes ? I know that there is a settings in the Admin section that can be used to disable sending completed document when the workflow is completed. But this account level setting will work for all the envelopes being sent out from that account. Is there an envelope level eSign Rest API that can be used to achieve the same thing for specific envelopes ?
As you have noted, the Sending account has a setting to determine if completed documents are attached to the "envelope completed" email sent to the recipients. However, there is nothing in the envelope to override the account setting.
I would recommend using the account setting to prevent the completed documents from being attached to the completion emails (because email attachments are not secure), and instead advice signers to use the prompt at the end of signing to save an account that they can log into to securely download the documents at their leisure. It's also worth noting that if the documents in the envelope are too large, attachment may not take place, making it even more important to use a free signer account to securely access envelope documents.
Are you referring to the completed document being attached and sent to the recipients via email? I'm afraid you can't control this setting. It is individual to the recipient's account and only they can change the behaviour for this
Related
In certain circumstances we would like to automate the forwarding of completed Docusign contracts to certain new recipients, possibly adding another page. Is there a way to do that with the REST API, or does that have to be done manually?
The short answer is Yes.
In DocuSign-speak, "completed" means that the envelope (transaction) has reached its final stage. No more changes, it's frozen and saved in the DocuSign platform.
Also, note that virtually anything you can do via the DocuSign web app can also be done programmatically via one of DocuSign's APIs.
So you have two options:
Send the first envelope to someone else as a new envelope
After the first envelope is complete, your API program could analyse it to see if it needs some additional recipients. If so, your API program could start a new envelope transaction that includes the completed (signed) document, possibly the first envelope's certificate of completion, along with the new documents to be signed (or not) and new recipients.
You could include the first set of documents (from the first envelope) either as supplemental documents to the new envelope or as regular documents within the new envelope. To obtain the documents from the first envelope, your application would download them from DocuSign and then upload them for the new envelope.
A live "supplemental" documents example.
A envelope is optionally sent to additional recipients
An alternative is to have one envelope and optionally programmatically send it to additional signers with, perhaps, additional documents for the new signers.
This might be a bit trickier to program with the DocuSign eSign APIs but is certainly doable.
After the last "original" signer has completed signing, you can pause the workflow.
Once the workflow is paused, your application can again analyse the document to see if more recipients need to sign, an additional document needs to be added, etc. Then your API program uses the API to update the envelope as needed, including adding additional recipients (who may or may not be signers). This is called "correcting" the envelope. Then your program resumes the envelope's workflow.
Your program should be notified that the envelope has paused by using the Connect webhook feature, either at the account or envelope level.
If you have more questions about this answer, please open new questions on StackOverflow. Make each question as specific as you can. Thank you.
I am trying to implement embedded signing in our application. I followed the steps as mentioned in the guide - https://developers.docusign.com/esign-rest-api/guides/concepts/embedding
I am able to create the envelope, generate the recipient signing URL, use that URL to sign and complete the document. But I haven't received the completed signed document to the email that I mentioned as the Signer.
Is there any additional properties that I need to specify to receive the document signed via the recipient signing URL?
What is the other way to receive the signed document in this case, Can I use webhook to receive the completed document?
Yes, webhook is the better approach for this.
in Embedded signing there are no emails going to the signer. That's the purpose. Embedding it in your app unlike remote signing where emails are sent.
Your app can receive a webhook notification from connect and retrieve the complete document.
https://developers.docusign.com/esign-rest-api/code-examples/webhook-status provide some examples. There are other resources about how to use DocuSign Connect webhook.
There's an option for this in the esignature admin tool., Send completion emails to embedded signers
That setting is account-wide. So if your application is used by people in multiple accounts, you'll need to set it for each account.
I am using Remote Signing with the DocuSign api, but I want to know how to determine what action the recipient took (i.e. they signed, declined to sign, viewed, etc). How do I do this?
You want the status of the envelopes you sent?
Best technique is to create a webhook and have DocuSign call your server when the envelope's status changes.
You can create DocuSign notification message subscriptions at either the account level or at the individual envelope level.
See this blog entry for more info. Ask additional questions on StackOverflow if you have any difficulties.
createSender creates a URL, which I would like to use to let the sender preview the document before it's send out. Hence the documents are created using templates and and the API.
The link which is created would lead me out of my UI. Does the user need to sign in? Future plan is to have many user's, which have no DocuSign account.
For embedded sending Your app will have to authenticate the user. If you are doing a Service Integration then your Api account will be used as the sender.
Once the sending url is generated using the createSenderView api, there is no authentication required to access the URL.
You also have an option to build a User Application using the docusign Api where your App can support sending from multiple accounts.
The createSenderView requires that the person is a DocuSign user (with their own account and password).
Only DocuSign users can send. We charge for sending, not for signing or receiving.
What exactly do you want to preview? (And why?)
the documents themselves? Use the EnvelopeDocuments resource. You can also preview the thumbnails of the documents.
the documents with the "fields" ("tabs") that indicate where people will sign? I'm not sure that is do-able.
or the recipients and their routing order? Use EnvelopeRecipients: list method.
Added
Another solution is to use a dummy certified delivery "recipient". Add this recipient as the first recipient. This will block the envelope from proceeding on the recipient routing.
Then get the envelope's documents to show as a preview.
Then, if ok, alter the envelope's recipients to remove the certified delivery recipient. The envelope will then continue on with the first "real" recipient.
We would like to prevent our Sales Rep(secondary signers) from receiving the completed/signed email with the signed documents as attachments. Only our external customers should be receiving the email.
Wondering if this is possible through the API or within the admin console setting.
We are using SOAP API by the way.
Thanks in advance.
It's not possible to exclude specific (remote) recipients from receiving the "envelope completed" email from DocuSign. ("Embedded/Captive" recipients won't receive any emails from DocuSign by default -- but this isn't the scenario you're asking about.)
Additionally, whether or not the "envelope completed" email from DocuSign contains the signed/completed documents as attachments is controlled via an account-level setting (located in Preferences >> Features within the DocuSign web console):
Since this is an account-level setting, it's not possible to control this behavior (i.e., whether or documents are attached to the "envelope completed" email) on a per-envelope basis, let alone on a per-recipient basis for a specific envelope -- it's either enabled or disabled for the entire account (at any given point in time).
Keep in mind that even if you disable this setting at the Account-level (so that documents are never attached to "envelope completed" emails), all recipients will still be able to access the completed documents via the link in the "envelope completed" email (which displays the completed documents in the DocuSign web console), in addition to being given the opportunity to print and/or save the documents during their signing session. So, it's not like you're preventing a recipient's access to completed documents merely by not having the documents attached to the 'envelope completed' email.