Shyam :
One issue which I have found, the response which is sent from Webhook to our own custom API, which will receive request from webhook does not match\nFor e.g.argument webhook sends json payload , so make sure you have same object which is supported by your api from docusign connect\n// this is C# code\npublic async Task Post([FromBody] JObject envelopeData)\nTo test locally, you can use ngrock, which will create local server but you will be able to debug",
2022-01-07T07:08:14
Larry K :
\nEnsure that your server (the "listener") has an https URL that is visible (callable) from the public internet. Best way to confirm this: implement a GET function at a URL such as https://your-server.com/hello. It should reply with "hello" when called. Then try entering that URL on your mobile phone.\nLook at DocuSign's Connect error log to see what it says.\nTo assure yourself that DocuSign is sending notification messages, first use https://webhook.site to get a test webhook listener URL, and configure DocuSign to use it.\nIf you feel that the messages are being sent to your server but are not being received by your software, check your web server's logs. For example, if you're including documents in your notifications, the notifications will be very large and may exceed your web server's default configuration limits.\n",
2022-01-06T20:55:28