Docusign Connect

Hi DocuSign team 👋,I’m integrating Identity Verification (IDV) in our Laravel-based app and connected it with a DocuSign Connect webhook.Everything works fine for regular eSignature events — I successfully receive: recipient-completed envelope-completed envelope-voided, etc. However, I never receive the two Identity Verification events even though they are enabled in my Connect configuration:✅ “Identity Verification Pending”✅ “Identity Verification Completed”Setup details Webhook URL: (public ngrok HTTPS endpoint) Environment: Demo (developer) Using REST API v2.1 Envelope created via API with the following recipient structure:  "recipients": { "signers": [{ "email": ",information removed", "name": "ANKITKUMAR SUTHAR", "recipientId": "1", "routingOrder": "1", "identityVerification": { "workflowId": "9bbb5cce-6c25-42d6-8934-2799d18947ef" } }] } The envelope completes correctly, IDV passes, and I get envelope-completed in my webhook. The webhook itself works fine — verified

Can I access admin dashbaord where we setup webhooks and integration keys from a business plan or do I have to buy a developer plan

We have recently got DocuSign for our company and integrated it with our OneDrive app. The sync between the two keeps slipping. We need signed documents to be saved to the original forlder. Can anyone advise on where this could be going wrong? It just saves to the primary folder in OneDrive. We had it setup initially but it keeps changing. 

I am unable to receive webhooks on my development server from DocuSign.When DocuSign tries to send the webhook, I see the following error:Error - The request was aborted: Could not create SSL/TLS secure channel.

Im using envelope level connect keys and setting the includeHMAC to true in the eventNotification object of the envelope.This works and the x-docusign-signature headers are being sent as part of the call. We are using this with a client and initially the x-docusign-signature headers were coming through. But the x-docusign-signature headers are no longer present. Ive checked with our client and the connect key still exists for that account.Is there any reason or a configuration setting that would stop the headers coming through?

 I am  trying to access and send documents through the Dropbox integration with DocuSign, but we keep encountering the following error:https://na4.docusign.net/plugins/api/RedirectExternalDocService.aspx?status=fail&error=AuthenticateFailed  Details: Integration: DocuSign connected with Dropbox SharePoint Site URL:  App Version: 4.0.3 Server Version: 4.0.0.6 Status: Dropbox is connected successfully, but when we try to prepare an envelope with a Dropbox file, the authentication fails. Has anyone experienced this issue before? How can we fix this AuthenticateFailed error?Any guidance will be highly appreciated.

Hi everyone,Since early 2025, I’ve been encountering a problem with the payload received via DocuSign Connect using API version 2.1 in JSON format.Until recently, I was deserializing the notification using a well-defined C# object like this: public class DocuSignEventNotificationResponse {     public string status { get; set; }     public string envelopeId { get; set; }     public string documentsUri { get; set; }     public string recipientsUri { get; set; }     public Sender sender { get; set; } }public class Sender {     public string userName { get; set; }     public string userId { get; set; }     public string accountId { get; set; }     public string email { get; set; } }However, recently the payload arriving in the DocuSign logs seems to have changed completely. For example, now I receive notifications in this format:{  "event": "envelope-completed",  "apiVersion": "v2.1",  "uri": "/restapi/v2.1/accounts/1e78c******8c2db/envelopes/18*******91dca",  "retryCount": 1,  "configurat

Hi,Currently, I am able to send the DOCX file for signature via DocuSign and the PDF files for review in separate envelopes. But my requirement is to send both files together in a single envelope—one for signature and the others for review. Is there a way to combine them into a single envelope for both signing and review purposes? Both files are attached to the same SharePoint item.

Hi everyone,I'm reaching out because I've encountered an unexpected issue with DocuSign and I'm wondering if anyone else has experienced the same thing.I have an application that has been using DocuSign for over 3 years to handle signature processes. I'm using a demo account, and I've registered an app in the DocuSign developer portal.When a document is signed or declined, DocuSign sends a POST notification (webhook) to my API. For years, the payload I received looked like this, and was successfully deserialized into this C# class: public class DocuSignEventNotificationResponse { public string status { get; set; } public string envelopeId { get; set; } public string documentsUri { get; set; } public string recipientsUri { get; set; } public Sender sender { get; set; } } public class Sender { public string userName { get; set; } public string userId { get; set; } public string accountId { get; set; } public string email { get; set; } } This worked perfectly in my PostNotificationEvent m

Both the prod and developer docusign account have exact identical structure. Can anyone please help? This is blocking a lot of our customers and this is very high priority.this is my prod account envelope request structure → { "emailSubject": "Please review your solar contract", "documents": [ { "documentBase64": "", "name": "Solar Contract", "documentId": "1", "file_extension": "pdf", } ], "recipients": { "signers": [ { "email": "neel@xyz.com", "name": "neel patel", "phone": "(44)", "recipientId": "1", "routingOrder": "1", "clientUserId": "1000", "tabs": {"signHereTabs": [{"xPosition": 199, "yPosition": 176, "pageNumber": 1, "documentId": "1"}]}, } ], "carbonCopies": [{"email": "neel@xyz.com", "name": "neel", "recipientId": "10"}], }, "status": "sent", "eventNot

We have docusign connect setup to receive events and to monitor the recipient authentication status. The authentication method we are currently using is KBA and the RecipientAuthenticationStatus we receive is correct:<RecipientAuthenticationStatus> <IDLookupResult> <Status>Failed</Status> <EventTimestamp>2025-06-30T22:41:25.04Z</EventTimestamp> </IDLookupResult></RecipientAuthenticationStatus>However, when switching to SMS authentication and according to this doc https://www.docusign.net/api/3.0/schema/dsx.xsd, which might be outdatedthere should be PhoneAuthResult under the RecipientAuthenticationStatus. after testing this is not the case and instead i see an empty object with no info:<RecipientAuthenticationStatus />Any ideas how to get the PhoneAuthResult to show up?

I have successfully integrated docusign connect in my development environment, and it is working well.Then I moved to production environment, and it is not working. There is not any option in the docusign production account to configure the webhook.Thanks

What is the cost incurred for using Workday -DocuSign Connect , especially considering Business Pro plan?

Create a Power Automate flow that triggers whenever the status of a DocuSign envelope changes (regardless of the specific status), and automatically sends an email notification to the document owner. The email content should vary based on the new envelope status as follows: If the status is "sent", notify the owner that the document was sent. If the status is "completed", notify the owner that the document was completed. If the status is "declined", notify the owner that the document was declined. If the status is "voided", notify the owner that the document was voided. I'm encountering an issue while creating a Power Automate flow with the "When an envelope status changes" trigger from DocuSign. If I select a specific event like "Sent", the flow only triggers for that particular status. However, my requirement is for the flow to trigger on any envelope status change (e.g., Sent, Completed, Declined, Voided), and then send an appropriate email notification based on the new status

We have created one webhook and in that, we call an API on change of document signed.The API triggers but it returns an error of 500 Internal Server Error.And when we debug the api call then we do not get the document pdf bytes in it and it returns null.

Is there any way to set the localhost in the “URL to Publish” section? I need to test my localhost url and looks like its not possible. Do you recommend any tool to create a fix url  temporary while I’m running my test ? I read about ngrok for example but I’m not sure if its secure.

I am currently trying to set up my DocuSign account so I have on App & key for each of our pre prod environments (Dev,test,staging) I would like to have three different keys, one for each environment. In turn these three different environments will have a connect for each one, how do I specify that a certain app should only use a certain connect, I can add them all into each one, but it gives me tonnes of failed messages 

We have an integration that uses both Connect/Webhooks and the Signing API in the legacy XML Format.  I know it is deprecated and we should rewrite to the new format, but is there an announced end-of-life date? We have limited resources (like everyone) and lots to do, so we’d like to know by when we must get this done.

Can anybody guide me to access legacy jar file - net.docusign.api._3.docusignconnect ?

I have a flow to create envelope, add doc, add recipient, tag (as needed) and send. When I log into DocuSign, I have 2 accounts, a default and a group account for all the appropriate users. Since I need all users to trigger the flow, I changed the connections to all steps to reference the group account number. All step look good EXCEPT Create Envelope. This one gives me the following error: Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'docusign' operation 'GetCustomFields' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: {"errorCode":"USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT","message":"The specified User is not a member of the specified Account."}' I’ve tried creating a new connection and it is still upset. Any help is appreciated. Thanks :)

Hi Team,I have configured the webhook feature in my demo account and include OAuth for integration and security, the webhook attempts to call the API when an event is triggered. However, I got  an error message in the log. Here is the error message: Error: https://dev.api.genpt.com/catalog/debi-service/debi/documentSign/status :: Error - HTTP call to OAuth authorization server failed: HTTP status code = 401, OAuth response = {"fault":{"faultstring":"Invalid access token","detail":{"errorcode":"oauth.v2.InvalidAccessToken"}}}; My question is: What details can I expect in the webhook API call? What should I configure in my service to handle this properly? Can anyone help us with this? Regards,Adarsh

Hello,I am trying to generate a flow in Power Automate that is triggered off when a Docusign envelope changes, however, am running into the following error code: The request failed. Response content: '{"errorCode":"USER_NOT_ACCOUNT_ADMIN","message":" User is not an account administrator."}'.After researching this, it’s my understanding that a DocuSign administrator must enable Docusign Connect before a non-administrator can use the Docusign for Power Automate connector to run a flow when an envelope status changes. I have met with the Docusign administrator for my account and we have tried to follow the instructions linked below but do not have a button for “Enable Connect” in the top righthand corner. We do have the ability to click on the “Add Configuration” button, however, upon trying to add a configuration we receive receive another error message stating that Docusign “needs permission to access resource in your organization that only an admin can grant” (see below). Would greatly

Hi Team,Whether it is possible to change the payload format of our webhook from XML to JSON. Our account is an enterprise demo account, and we are currently unable to locate the configuration option within our webhook settings to make this change.Could you please confirm if this feature is available for enterprise accounts and provide guidance on how to update the payload format if it is?Regards,Adarsh

I’m using DocuSign Connect to send a webhook to Zapier when a document is completed. When I review the output of the webhook sent to Zapier, I do not see the document field values.  My custom connect is set up using REST v2.1 data format, SIM delivery mode, and data included is the following:Custom Fields Documents Attachments Document Fields Recipients Has anyone else had this issue or know a way I can adjust my configuration so that the output includes the document field values?

Hi Team, I am using the DocuSign feature in my current application. Currently, we have two servers, DEV and QA, and I have only one developer (demo) account.What I need is, if I trigger the mail through my DEV server using the integration key, it should trigger the DEV URL in the webhook whenever an event happens for that particular envelope ID. I need the same functionality in the QA server as well, without any conflicts. If I use the same integration key for both DEV and QA with different webhook configurations in the webhook connect feature, what will happen? Also, what is the best/relevant way to approach this scenario? Regards,Adarsh