Docusign Connect

I'm getting a 404 The URL provided does not resolve to a resource when POSTing to create an envelope from a Spring Boot app using RestTemplate.My URL is built like this:javaString url = baseUrl + accountId + "/envelopes";// baseUrl = https://na4.docusign.net/restapi/v2.1/I'm sending a POST with a Bearer token and a JSON envelope body containing a base64 PDF document.What I've tried: confirmed the access token is generated successfully, confirmed the account ID is correct.Question: Is my endpoint path correct? Do I need an accounts/ segment, and how do I confirm the correct base_uri for my account's region?Environment: Java 17, Spring Boot, DocuSign eSignature REST API v2.1.

Hello.When using the "Add documents to an envelope" action, I get the error message “Flow run failed. Action 'Add_documents_to_an_envelope' failed: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.”I get this with both docx and pdf documents. Wrapping the ContentBytes in the base64 function did not resolve the problem. The Inputs and Outputs of the action are attached.Has anyone had the problem and knows how to fix it?Many thanks*** attachment removed due to sensitive information

Hi,I was talking to our sys admin about some cloud flare blocking that has since been resolved, but he asked me to ask you about this image I am attaching. Can you give us some information about this screen shot ? Thank you,maggie  

We have a published webform - "id":"3527eec7-2c68-43f0-aca9-9eb51c4e7a16","accountId":"d09a0de1-8019-4bf8-a56c-46916ffdf531". When users complete it, is it possible to have it trigger Connect to send a webhook request? I don't see anything related to WebForms in the list of possible triggers for Connect - maybe it is not supported or maybe it is under a different name? Thank you!

Hi Community,We have an integration where Ironclad sends agreements to DocuSign eSignature for signature. Now we want to sync back signatory details from DocuSign into Ironclad (as metadata) for reporting purposes.Goal: After the envelope is sent (and as it progresses), we want to fetch and store in Ironclad fields such as:Who has signed Who is still pending Whether the countersigner has signed or not Optionally: signing timestamps, routing order, declined/voided statusThanks!👪 Docusign Community Leaderboard Top 5 contributor💹 Ranked #3 in the Reply Royalty category in DocuSign Community Wrapped 2024🤝Let’s LinkedIn and roll: Pawan Gangwani - EY | LinkedIn

Core ProblemMy organization has implemented Docusign-Connect to send completed envelope to our Laserfiche storage system. This Works as intended for envelopes with a single template however multi-template envelopes additional templates do not express retrain their Envelope Custom fields metadata correctly when transferred to Laserfiche, and instead assume the Envelope Custom Field data of the initial template.  Current DesignEach Template has 4 key pieces of metadataTemplate Category: This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field.  Template Sub-Category:  This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field. Recipient Account Number: This is currently a Custom Document Field on each template  Completed File name: This is correctly separating into multiple files based on template pdf file name.  Design LimitationsR

I recently used docusign connect in my application and i had this doubt, Are the events for an envelope queued before sending them in the order of occurring. lets say i had 3 levels and the final recipient just receives a copy, no signing action. Now two events will occur right, recipient delivered, recipient completed which will happen so quick, now will this 2 events triggered in parallel, or will it happen one after another. that is only after recipient delivered event gets a 100 response will recipient completed event sent?

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.