I'm using the DocuSign REST API (from a developer demo account) to send a document to an e-mail address that already has a DocuSign account (free account). The user gets the DocuSign notification in their e-mail but not in their DocuSign web interface .........Am I doing something wrong ? Is there a specific API that I have to use so that the documents go into the users' DocuSign web interface ( if the user has an account associated with the e-mail address ).
Cheers !
My request is the following:
--b2cb90e7^M
Content-Type: application/json^M
Content-Disposition: form-data^M
^M
{"status":"sent","emailBlurb":"Please review and sign this report.","emailSubject":"Patient Report","documents":[{"documentId":"1","name":"TEST006.pdf"}],"recipients":{"signers":[{"recipientId":1,"name":"Some Name","email":"somename#company.com","tabs":{"signHereTabs":[{"xPosition":42,"yPosition":42,"documentId":1,"pageNumber":1}]}},{"recipientId":2,"name":"Some Name","email":"some.name#gmail.com","tabs":{"signHereTabs":[{"xPosition":42,"yPosition":42,"documentId":1,"pageNumber":1}]}}]}}^M
--b2cb90e7^M
Content-Type: application/pdf^M
Content-Disposition: file; filename="TEST006.pdf"; documentId=1^M
^M
etc.
Do I understand correctly that your scenario is as follows?
The Envelope is being created/sent via API in the DocuSign Demo environment (http://demo.docusign.net).
The DocuSign account owned by the recipient of the Envelope is a "Free Trial" account. (It's a "Free Trial" account if it's accessed via either http://www.docusign.net or http://na2.docusign.net -- this is the DocuSign Production environment.)
If that's your scenario, then the reason that the Envelope's never showing up in the recipient's DocuSign Inbox (within their "Free Trial" account) is because an Envelope that's sent from the DocuSign Demo environment will never be delivered to a DocuSign user's Inbox in the DocuSign Production environment -- and "Free Trial" accounts technically reside in the DocuSign Production environment.
If you want to test the scenario of sending an Envelope via API in the Demo environment and have it arrive in a user's DocuSign Inbox, then that user account will need to exist in the DocuSign Demo environment as well. You can either add that user as a new user within the same account that you're API calls are using, or create that user under an altogether separate DocuSign account by simply creating another "DocuSign Developer account" via the DocuSign Dev Center.
Related
I signed a document using docusign API as a recipient but I am not able to see any completed documents in my docusign account. I can access the signed document through the mail I received from docusign after signing. Is there any way to view it in the completed documents dashboard in docusign ?
This happens when there's no exact match between the full name + email that was used when you were sent a document to what is in your account.
In order for DocuSign to know when someone send you an envelope that it should go to your account, the full name (case sensitive!) as well as the email must match exactly to what is in the DocuSign account. Even then, you need to log into DocuSign to associate the envelope you received with your account.
I am trying to integrate Docusign API into my web application. I tried using Envelope Views where I am redirected to either login page or the signing page. But I would like to redirect to Add Recipients page from within my web application where the user can add the recipients, prepare the document and send it to the signer. Is there any method as such exposed from Docusign API?
Re: But I would like to redirect to Add Recipients page from within my web application where the user can add the recipients, prepare the document and send it to the signer.
Is there any method as such exposed from DocuSign API?
Yes, the EnvelopeViews::createSender view enables your application to open the Sender's view of the envelope on the DocuSign web site. The user can then add recipients, tabs, etc.
Here is a code example that shows you how this works. You can download and run the code example in many languages.
Information Security Notice
This method, EnvelopeViews::createSender, provides full access to the sender's user account. When you use this view, the sender has full access to the user account. If the sender user account has administrative privileges, then this method also provides administrator access.
If your use case needs to enable a sender to update a draft envelope before it is sent, then either:
Configure each sender to have their own individual user account to use this API method.
Enhance your API integration so that this method is not needed. Your integration can create the tabs, recipients and other envelope settings as needed.
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.
When using the Docusign API (in my case, via the Sandbox/demo env), in the signing view at the top of the screen it displays the name & company of the user account that was used to authenticate with the API.
However, because this is embedded signing from my app, I would have thought we'd only have one user account - for the app. So I want to change what appears at the top there - the information on the sender of the envelope. Either to be the user account that exists in my app that created the envelope, or just to state what company sent the document.
Are there options on the API to do this? I can't see any reference to anything like this in the envelopeDefinition JSON structure in the REST API docs.
You can use the DocuSign SOBO - Send On Behalf Of Functionality
The Send On Behalf Of feature permits automated sending through the API by one account user on behalf of another account user.
More information here
The DocuSign account created is by an individual, but when using the DocuSign API to generate an envelope from a template and sending to a receiver, the name and email address of the account holder shows up instead of the company the user works for.
Is there a way to show company name and official company email instead of the account user's name/email?
The name and email address corresponding to the sending DocuSign user account will always be shown on/for sent envelopes. That being said, there's an easy way to achieve what you describe:
Create another "user" (i.e., membership) within the same DocuSign account -- this will represent the "system sender" user account -- i.e., the user account that you'll specify when sending envelopes with the API.
When creating the new "user", set name and email address to the values that you want to see/use for envelopes you send via the API.
Make sure to grant the new "user" the appropriate API-related settings (under the DocuSign API heading when viewing User Permissions).
Use the "system sender user" credentials to send envelopes via the API.
Keep in mind that when using this "system sender" user to send envelopes via the API, that user will be considered the sender of each envelope sent using that account's credentials -- which means that only that user's credentials can be used via the DocuSign web console to access the DocuSign envelope for viewing/correcting/etc. Other members of that same DocuSign account won't be able to access the envelope via the DocuSign web console unless you explicitly grant 'folder sharing' rights between users.