Back to Docusign.com
Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of February 2025. To make sure we see your questions on Stack Overflow, use the tag docusignapi.
Thread: Webhook payload in XML Format
https://community.docusign.com/docusign-connect-69/webhook-payload-in-xml-format-22548
Summary: The developer is using webhooks with Docusign Connect. They want to change the payload format of their webhook object from XML to JSON.
Answer: Once a custom Connect configuration has been created, it’s not possible to change the format of the object. It is possible to define multiple custom configurations in an account, so the developer needs to create a new configuration and select REST v2.1 for the data format. All other values can be copied from the original configuration, and once the new object is created, the original configuration with XML format can be disabled.
Thread: Why is my envelope created from a template via API remaining in "created" status instead of being sent?
Summary: The developer is trying to use the Node.js SDK to create an envelope from a template and send it via the eSignature REST API. When they create the envelope, they see a status of "created" but the envelope is never sent, despite defining the status as "sent" in their envelope definition JSON.
Answer: The default status for an envelope is "created", which indicates that the envelope is in draft state but has not actually been sent. In this case, the developer has defined the envelope in a JSON object, but has not actually created the EnvelopeDefinition object, which needs to be included in the API call through the SDK. To do this, they need to add the following line to their code:
let env = new docusign.EnvelopeDefinition();
Then, they can define the properties of the envelope in this EnvelopeDefinition object and set the envelope status to "sent". Step 2 of our guide How to request a signature by email using a template provides an example of how to do this with the Node.js SDK.
Thread: Docusign Connect Event for Browser Closed or Timeout
https://stackoverflow.com/questions/79455697/docusign-connect-event-for-browser-closed-or-timeout
Summary: The developer is building an integration with embedded signing using focused view. They are also using Docusign Connect to receive callbacks when the envelope has been completed, voided, or declined. On top of these events, they want to know if they can use Connect to track when a user views an envelope but takes no action or the browser times out.
Answer: The events that the developer wants to subscribe to cannot be tracked through Connect. However, they can use Docusign JS to track a variety of events related to the envelope embedded in the browser. The blog post From the Trenches: Real-time updates in an embedded signing workflow details these events, including the cancel and session_timeout events that could be used to accomplish what the developer is looking to do.
