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

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

Related

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

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/

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

How to check Expiration for Envelope

I'm using the DocuSign API 3.0. We are not including the notificationField. It has always used the default settings setup in the Admin for DocuSign. How can I confirm the expiration on an envelope?
The SOAP API Doesn't appear to have a way to get Reminder and Expiration settings for an active envelope. You could log in to the web console, Correct an envelope and view them there.
For the REST API, There's a post about this on the DocuSign Developer Blog: An API call to the Envelopes::getNotificationSettings method will do it.
GET /v2/accounts/{accountId}/envelopes/{envelopeId}/notification returns the relevant information.

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.

Docusign login advice

In my testing, I used a web proxy to get thru the firewall here so I could send envelopes. Now I will no longer be using the proxy. Do I need to log in for each web request ( like getting the templates, creating an envelope, etc )? The way we will use docusign is like this: a client consultant will see 3 documents that need to be sent to user X. So they will create an envelope with the 3 documents and send it out. They only need to connect to Docusign for a few rest calls and then they're done. The client consultants will connect to Docusign a few times a day, maybe no times a day if there are no documents to send. I'm assuming that I should go out and see if I can connect to Docusign without a problem before attempting to send out an envelope. What workflow are other people using in similar situations? Thanks for any advice.
I think a short answer here is that every API call you make requires a form of authentication provided, whether it is username/password or an oauth token passed in the appropriate x-header in your API request. I doubt your proxy was adding this on your behalf, so IMO I do not see what you will be gaining/losing by removing the proxy.

Resources