Skip to main content
arrow-left Back to Docusign.com

Docusign Connect

Find answers to your Docusign Docusign Connect (Webhooks) questions.

  • 51 Topics
  • 103 Replies
51 Topics
S
Newcomer
ServiceAccountReactNewcomer
asked in Docusign Connect
Issue with DocuSign API v2.1 payload – notification format changed

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

362
S
Newcomer
S
Newcomer
Sai PasupuletiNewcomer
asked in Docusign Connect
send the DOCX file for signature via DocuSign and the PDF files

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.

263
D
Docusign Employee
S
Newcomer
ServiceAccountReactNewcomer
asked in Docusign Connect
DocuSign – Webhook suddenly incompatible: Has the payload schema changed?

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

510
S
Newcomer
N
Newcomer
neel_patel_73Newcomer
asked in Docusign Connect
My prod docusign account is sending the response in different structure compared to my developer docusign account. Why is that?

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

311
Ivan.Dinkov
Docusign Employee
W
Newcomer
wintonNewcomer
asked in Docusign Connect
RecipientAuthenticationStatus blank in Legacy data format

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?

421
A
Active Voice
B
Newcomer
BIBEKNewcomer
asked in Docusign Connect
Webhook not working in production

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

8510
M
Community Moderator
S
Newcomer
swarajtwNewcomer
asked in Docusign Connect
What is the cost incurred for using Workday -DocuSign Connect , especially considering Business Pro plan?

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

90
S
Newcomer
V
Newcomer
VamsiNewcomer
asked in Docusign Connect
Trigger for Power Automate Flow - DocuSign - When Envelope Status changes

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

711
Alexandre.Augusto
Docusign Employee
C
Newcomer
CRM DeveloperNewcomer
asked in Docusign Connect
The API returns "500 Internal Server Error"

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.

701
T
Docusign Employee
C
New Voice
carlos.torres140New Voice
asked in Docusign Connect
Testing Webhook connect using localHost URL (URL to publish)

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.

903
C
New Voice
D
Newcomer
Dave WDXNewcomer
asked in Docusign Connect
How do I link one of my Apps and Keys to only one of my connects

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 

342
M
Community Moderator
I
Newcomer
IraWhitmanAtEpicorNewcomer
asked in Docusign Connect
Timeframe for elimination of XML format support

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.

201
S
Docusign Employee
G
Newcomer
gajendra12Newcomer
asked in Docusign Connect
Access legacy jar file - net.docusign.api._3.docusignconnect

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

281
I
Docusign Employee
K
Newcomer
KatieLNewcomer
asked in Docusign Connect
Create envelope error: Error response: {"errorCode":"USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT","message"

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 :)

2144
M
Community Moderator
A
Newcomer
adarshNewcomer
asked in Docusign Connect
Can't be able to access the webhook feature properly

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

642
M
Community Moderator
L
Newcomer
LegalOpsNewcomer
asked in Docusign Connect
Error when running PowerAutomate flow that triggers when Docusign envelope changes

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

2262
L
Newcomer
A
Newcomer
adarshNewcomer
asked in Docusign Connect
Webhook payload in XML Format

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

993
C
Community Moderator
L
Newcomer
lk1919Newcomer
asked in Docusign Connect
DocuSign Connect not sending document field values via webhook

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?

731
A
Active Voice
A
Newcomer
adarshNewcomer
asked in Docusign Connect
need clarification regarding docusign webhook feature

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

503
G
Docusign Employee
S
Newcomer
shin jihoNewcomer
asked in Docusign Connect
I tried integration with Onedrive but, Error page is shown

I tried integration with Onedrive but, Error page is shown.I used personal account on microsoft.how can i integration with onedrive on docusign? It’s error page screenshot. 

662
S
Newcomer
T
Newcomer
triSaaS_devNewcomer
asked in Docusign Connect
DocuSign Connect Not Sending Events

We have an application the is integrated with DocuSign via the C# SDK.We allow users of our app to sign into their own DocuSign accounts to create and send envelopes which is then facilitated by the various SDK API calls.The users can successfully create and send envelopes, however if they are signed into their own accounts Connect is not capturing any events to forward to our webhook.If we sign in and use the account that is associated with our integration to send and create envelopes Connect forwards the events to our webhook as expected.Am I missing some settings within our configuration of Connect or are you not able to capture events across accounts?Is there any solution to this instead polling for envelope / recipient status changes? 

1464
R
Newcomer
D
Newcomer
Dennis.W.WatsonNewcomer
asked in Docusign Connect
HMAC Validation

I am writing an app to download documents after being signed to integrate into our in-house application.I am having a little trouble with “public static bool HashIsValid(string secret, string payload, string verify)”In the development environment this works without error.I create a document, sign it and via connect the json and headers are sent to webhook.siteI pick up the json and x-docusign-signature-1.  I place the HMAC from development connect as the secret, the json as the payload, and x-docusign-signature-1 as verify and my json verifies.In production I do the same, I place the HMAC from admin connect as the secret, the json as the payload, and x-docusign-signature-1 as verify, but it always fails.I have also published this application out for testing.  I change connect to use the URL of my application.  I read the HMAC for development, the json and x-docusign-signature-1 are read from what DocuSign sends.  The HMAC is validated and the document is stored in the appropriate direc

561
B
Docusign Employee
A
Newcomer
AllieOlsonNewcomer
asked in Docusign Connect
Docusign Connect Sends Two Events when Reassigning an Envelope

I have an application that I am connecting to DocuSign esignature and connect. I have configured connect event to for recipient signed/completed and reassign. When a recipient signs the envelope it is working fine and sending a recipient-completed action via connect. However, when I reassign via the email sent as part of the envelope - connect sends a recipient-completed event for the initial signatory, immediately followed by a recipient-reassign event. I would expect it to only send the reassign event.  Is there a way to configure it to only send the reassign event in this scenario? Or is it possible in the recipient-completed event to tell whether the recipient actually signed or not?

481
JohnSantos
Valued Contributor
F
Newcomer
Fusion06Newcomer
asked in Docusign Connect
How to use multiple "FROM" address for a single envelope.

We are currently leveraging DocuSign keys within Oracle Integration Cloud (OIC) for a KYC process. In our current setup, the email notifications accompanying envelopes sent to customers display a single "From" address corresponding to the account configured for this process.The challenge arises when we involve multiple departments in our workflows. We have developed separate processes for various stakeholders, including Sales, HR, and others. Each department would like their envelopes to display a unique "From" address specific to their role or function.Could you please confirm if it is possible to configure multiple "From" addresses for envelopes based on the process or department? If so, we would appreciate guidance on the best approach to implement this functionality.

352
A
Active Voice
O
Newcomer
Office_Tech732Newcomer
asked in Docusign Connect
How to Provide DocuSign field names integrating DocuSign connect with Laserfiche?

I'm working on integrating DocuSign connect with Laserfiche I need to Provide DocuSign field names however, these fields, don't exist on my templates for the following data points: Document Name:Document Date:Document Worker:How would I provide field names to collect this data?Do these fields need to be added to each template? If so, is there an automated way to populate these fields and have them hidden? 

261
JohnSantos
Valued Contributor

Badge winners

Show All Badges
Code of Conduct

Docusign Community

Code of Conduct