Power Apps/D365 and DocuSign Integration - Send Envelope on behalf of others - docusignapi

This is my first time posting so apologies if I don't explain things clearly.
I've created a Custom Connector within Power Apps that does an API call to my DocuSign Account. The API call I am currently leveraging is to create DocuSign Envelopes:
/restapi/v2.1/accounts/{accountId}/envelopes
Link to DocuSign API Library: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/?explorer=true
My issue is that I do not know how create Envelopes on behalf of other DocuSign Users while using the API call within my Connector. Since the Custom Connector required me to log into my DocuSign Account, every time I use the Connector the Envelope generated from the API call gets associated to me (I am able to see it within "Drafts" when I log into my DocuSign).
Sorry if this is a bit confusing. My end goal is to use my Custom Connector and its API calls within a Canvas App. However, I want the Envelopes created not to always be associated to my DocuSign account especially if the Canvas App is used by other End Users.
Any help would be much appreciated!
Thanks!
Screenshot of Test call:
Request
Screenshot of Test Call: Response
Screenshot of Envelope within DocuSign Account: Snippet

This is Yara from DocuSign Developer Support.
Since you want to create envelopes on behalf of other DocuSign Users while still using the API call within your connector, you can use the Send On Behalf Of Functionality (SOBO). This functionality allows a single user in an account to authenticate for other members of the account and send fully defined envelopes on their behalf.
Here's a detailed guide on the SOBO functionality: https://developers.docusign.com/docs/esign-soap-api/esign101/auth/send-on-behalf-of/

Related

Get a list of envelopes that are close to expiration via DocuSign API

My company uses DocuSign API to automate document-related tasks.
Via the API, I need to retrieve all envelopes that are expiring soon. Similar to what the DocuSign UI has in the screen below but for all users:
Can somebody point me in the right direction -- which API endpoint/method I need to use to get all envelopes that are about to expire? Is there any way to use DocuSign Connect to trigger a callback from DocuSign for each document that is about to expire?
Thank you!
Add the following to your API call (GET to /envelopes endpoint)
folder_ids=expiring_soon&folder_types=normal,inbox,sentitems&include=recipients,powerform,folders,delegations,workflow&include_purge_information=true&query_budget=10
Remember to also have from_date and to_date parameters
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/liststatuschanges/
Also, the way I found this out for you was by trying it from the web app and recording API logs, Suggest you try that too as it will mean you can find it yourself. https://www.youtube.com/watch?v=YJYTDcc7cZw

Can following be achieved using Docusign APIs?

I'm trying to achieve some requirements via Docusign APIs. Would like to know if it's possible before I start the project.
I've used Docusign app for Salesforce earlier, but now I'm trying to achieve some functionalities through API calls
Ability for a Signed Document sent to a contact (by clicking on a button on contact record) to be attached to the Contact record it was sent from
Ability to write back to the record from a field tagged on the DocuSign envelope
Vinay, this functionality is available using the DocuSign for Salesforce integration. If you would like to write it yourself using APIs, you can start by looking at our Apex toolkit here - https://developers.docusign.com/salesforce/guides/apex-toolkit

DocuSign API Create Envelope

Currently I am using #DocuSignAPI to create envelope in which API required x and y position to add signature from recipients.
So my requirement is like if i upload the document it should be redirect to the Docusign UI where recipient would login and sign the document.
So the thing is instead of creating rest call via API.
I need some api where Docusign is going to handle by its way so i do not need to create UI for that which is very complex to build from my side.
Anyone can help me with is will be really great.
Thanks in advance
Check out this DocuSign recipe: Sign from Your App.
This sample (and many others) are available on the DocuSign Developer Center, along with tons of documentation about various integration scenarios and API reference.

IS there an API option to change who a Docusign envelope is displayed at being sent by?

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

Using DocuSign's CORRECTION functionality as a service in Salesforce via API

DocuSign has a Correcting option (to correct an envelope after it has been sent and before it is signed by the recipient) when you are logged into their site - is there a way to utilize this functionality through SFDC through a web service API? Where we send the unique envelope ID and the changed data to DocuSign, and they in turn revise the doc in the background? The recipient will see the updated document when he accesses the document to sign it.
Yes, you could do this from within an Apex class on SFDC. Don't use a trigger for the class, only a Lightening or force page, since triggered classes have too many restrictions on callouts to other services.

Resources