We have bulk send feature on Docusign by which we can send the document to mulitple envelopes which would be signed by many from the list. So each of them would be getting their own copy of the document to sign. So, is it possible to download the document as the receipent(s) signed it. We can download the document with mulitple users and single sign document once it is completed by registering the webhook. Is it possible to get this in same way for bulk send also? Can we get the document one by one as the receipents from the list signs that ?
Thanks in advance!
Bulk Send generates multiple envelopes, each envelope for a CSV row, so DocuSign Connect will help you getting notified for each envelope.
Using DocuSign Connect, you can subscribe to Recipient Level Trigger events - For instace Recipient Signed/Completed, once any recipient signs the envelope then you will receive the notification from the DocuSign, on receiving the notification you can call DS API to download the document or you can include documents in the DocuSign Connect message itself if the document is not very big.
Related
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.
We have some documents which has DocuSign Envelope ID on top of documents. So is there any API present which help us to extract the values like 'date of sign', 'who signed it' etc. from the documents.
(Note - These documents are processed by others we have only there documents.)
Any help would be appreciated.
No. The DocuSign API only allows you to pull data from envelopes you already have access to. In this case, I would recommend reaching out to a party on the envelope to request they provide the Certificate of Completion.
I have a checkbox list of locations on my powerform and I'd like to implement logic that sends a copy of the signed powerform to the location based on the users selection. Is such conditional logic possible? Would this be something that could be done using the API perhaps?
It's not possible to have DocuSign automatically send the completed/signed document(s) to specific locations. However, you could achieve the same end result by doing the following:
Configure DocuSign Connect to subscribe to the "Envelope Complete" notification and specify that you want the notification to contain the document(s) as well (in addition to the form data, recipient data, etc. that it contains by default).
Design your listener application (where DocuSign Connect will send HTTP notifications each time an Envelope is Completed) to parse the payload of each request received and use the form data to determine where the Completed document(s) need to be sent. Then, programmatically extract the documents from the payload of that request and send them to the correct location(s).
In other words, you create a simple (listener) application and configure DocuSign Connect to send an HTTP notification to that application's endpoint each time an Envelope is completed. The body of each notification that your listener application receives from DocuSign Connect will contain info about Envelope Status, Recipients, Form Data, and also the document bytes (provided that you've configured DocuSign Connect to include the documents in the notifications it sends). Your listener app then has all the info it requires in order to send the completed document to the location that the user/signer specified on the form.
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.
I have a client that would like to send out batches of contracts for signatures (hundreds at a time). They would also like to use email for the recipients to log into docusign and sign. Only problem is that many of the recipients on these docs are the same couple of people, and thus, would end up with a flooded inbox after every contract batch.
Does DocuSign have a different email correspondence option? Maybe one that would send out 1 email if recipients have documents they need to take action on? This would be something that we need to control when creating and sending the envelopes because many of these users would be logging in for the first time when they sign their first document, and probably wouldn't know how to configure their settings appropriately.
Whenever an envelope is sent, the recipient will receive an email notification from Docusign. Sender will not be able to disable these notifications to the recipient.
Recipients can control the notifications they receive using the Manage Notifications page