eSignature API

When a document gets voided due to the expiration date, I assume the webhook sends out an event to the listener telling the doc has been voided, but I am not receiving any voided event. I am receiving all the other events just not any voided or expired events. Can someone tell me how to configure the voided\canceled\expired documents?

Hello everyone,I’m currently working on an integration with the DocuSign API using JWT authentication. When I try to call the API, I get the following error:❌ [send-docusign-signature] DocuSign rejects JWT signature - public/private key mismatch or missing consentHere’s what I’ve already checked: The private key in my code is the one generated when I created the app. The public key has been uploaded correctly in my DocuSign integration settings. My Integration Key (client_id) is correct. I suspect the issue might either be a key mismatch or the fact that the user consent has not yet been granted. My questions are: How can I confirm whether the issue is due to missing user consent versus a key mismatch? What is the exact procedure to generate the consent URL and have the user approve it in the demo/sandbox environment? Are there best practices for managing the lifecycle of keys (rotation, updates) to avoid this type of error? Thanks a lot for your help 🙏 

I'm learning how to use SOAP UI. Does Docusign provide a WSDL (Web Service Description Language) file or some documentation for REST API?

Hi,I'm encountering an issue when using the compositeTemplates feature to create an envelope from a template that contains multiple documents.When retrieving this template via the EnvelopeTemplates:list endpoint, only the first document is returned in the response - the remaining documents are omitted.This behavior is different from what I observe in the DocuSign web UI. If I simulate the same process (e.g., by creating an empty envelope and applying the templates), all documents are present as expected.Is this a known limitation of the EnvelopeTemplates:list API? Or am I missing something in the way the template is structured or retrieved? Thanks in advance for any help or clarification.

I am using embedded signing with my API and every day I send documents to sign to many recipients. All the documents I send need to be signed again by our company but it is not viable to do it one by one so I would like to know if there is any way to sign several documents easily. The way it would be done it is that we put our company the last in the recipients order to sign of each document, and then, instead of signing all one by one, sign all at once (of the ones alredy signed by the previous recipients to sign). Thank you.

How to enable live video and screen sharing options for DocuSign Notary in a demo (developer) accountI want to check DocuSign Notary in my developer (demo) account, and I can see the Notary option there.However, while testing, I found that the live video recording and screen sharing features are not available. I need to test and demonstrate the full RON workflow before moving to production.How can I enable the video session and recording features in my demo account, or is there any alternative to achieve the same?

Please explain the process for setting up Remote Online Notarization (RON) with DocuSign Notary in a Developer Account, including configuration and prerequisites.

We have noticed a few errors in our system where the response for the EnvelopeLocks:get endpoint (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopelocks/get/) does not contain the lockToken field.The docs dont seem to have any point which indicates this as expected behaviour.Wanted to know if there is some nuance I am missing?btw we get all the other data about the lock in the response, its just the lockToken that is not there: { lockedByApp: "-", lockedByUser: { uri: "--------------", userId: "--------------------", userName: "------------------" }, lockedUntilDateTime: "--------------------", lockType: "------"} 

I wanted to ask if there are there any APIs available for the following tasks?1. Fetching the total number of documents that have not been signed bythe recipients, or to provide the status of all the documents?2. Fetching the total number of envelopes that are in a pending or failed state?3. Fetching logs or metrics data for Docusign CLM and eSignature thatwould contain latency (duration) and reliability (http status code)information for APIs being called, CLM Workflow Execution Stages orEnvelopes Processing Stages along with their statuses?4. Fetching the start to end time of all the CLM workflows?

Hi everyone,I’ve heard that DocuSign uses Onfido in some of its identity verification workflows.My question is:Is it possible to pass existing Onfido verification data (photo of the document & video with face) directly to DocuSign in the background, so that the user can generate a Qualified Electronic Signature (QES) without going through the identity verification process again?If yes, could someone share documentation or examples showing how to integrate this, ideally via API?Thanks in advance!

How can I implement notary using DocuSign video conferencing? Can you please provide the code implementation for Remote Online Notarization?Can you please help me

Hi everyone,We're using the DocuSign API to send legal agreements (Unilateral Undertaking and Customer Supply Agreement) via our platform. The envelope is generated using the primary user's profile — it includes their name, address, and other key details. That user is assigned as the signer and receives the envelope via email.However, in many cases the property has two owners, and we need both individuals to sign the same document — even though it’s initially triggered and sent using just one user's profile and email.Our goals: The primary user receives the envelope and signs as normal. The same envelope should allow a second person (co-owner) to sign. This may either be: Another signer using the same email address, or A second signer added by the first signer at the time of signing (if possible). Our questions: What’s the best way to set up the envelope via the API to allow two signers, if we only have the primary signer’s email at the time of sending? Can both recipien

With SOAP API, I can send envelope up to 35 MB most of the time. If it’s more than 35 MB, DocuSign returns error REQUEST_ENTITY_TOO_LARGE. However, I had a case where envelope contains a 17 MB PDF, with 2 supplement files (10 MB and 14 MB). The envelope was sent successfully. Why?WIth REST API, the limit is 25 MB. If envelope sent is more than 25 MB, DocuSign returns error request is too large. Sent envelope with 30 MB PDF and error returned is:REQUEST_ENTITY_TOO_LARGE - The request size of 41625837 bytes exceeded the maximum size of 35651584 bytesFile size is 30,487 KB. The maximum size limit is not 35 MB. Should the limits be different between SOAP and REST? I’m trying to figure out whether the issue is on our server.

I am creating an integration with my App using the .NET SDK. My App is written in VB.NET, and I have installed the package “DocuSign.eSign.dll” V 8.3.0 (latest). I have downloaded the C# JWTConsole example and tried that - everything works great! - I get the emails, I can sign, I see the envelope in the dashboard, status is “sent” etc… all good. This example is also using the DocuSign.eSign.dll package.My main project is in VB.NET, so I convert (using the Telerik C# to VB converter) the C# code, and paste that in to my project… with a little bit of tweaking here and there I can get it all “working” - insomuch as I can run it, I get no errors, I can log in to the Docusign dashboard where I can see the envelope with a status of “sent”, I even get webhooks from DocuSign with status of “envelope_sent” and “client_sent” - but I get no Signer email - I have checked that the email address is correct. I can click RESEND on the dashboard, but I still get no email.What could I be doing wrong? -

I need to go live my app , my develope Integration Key is “8c174c81-7390-446b-a128-814fef95c028”，And it was declined wihout any reason.How can I get the reason?

I'm trying to set up JWT Grant authentication in the DocuSign sandbox, but I'm constantly running into an invalid_grant / issuer_not_found error, even though I have successfully completed the consent process.My Configuration Environment: Development (account-d.docusign.com) Integration Key: 1b490ae4-97d1-4b5b-a4d4-cee9998fdf03 API Account ID: 73228f49-0509-4526-ac11-20a1025960e3 User ID (the user who granted consent): 80a3a400-b695-4fbf-9809-7cf4538d9419 Problem DescriptionMy server-side application (a Firebase Cloud Function on Node.js) is using the official docusign-esign library to call requestJWTUserToken. In response, I receive a 400 Bad Request error with the following body:{ "error": "invalid_grant", "error_description": "issuer_not_found"}What I've Already Tried Verified all IDs: I have repeatedly checked the Integration Key, API Account ID, and User ID against the details on the "Apps and Keys" page. They are correct. Verified the endpoint: My code is using account-d

Hi,I've been trying to create a DocuSign developer account, but no matter which email I use, the registration process doesn't complete. I even tested the process with an existing email, expecting an error message indicating that the account already exists, but instead, the "Get Started" button stays in a submit state and nothing happens—no error message or confirmation.At this point, I'm unsure if the registration form is working correctly. I have attempted the process with five different emails and have also tried the following troubleshooting steps:Clearing cookies and cache Using a private/incognito window Trying a VPN Using a mobile device on a different networkDespite these efforts, the issue persists. Could someone please assist me in resolving this?Thank you.

Well, when I create the envelope with status “sent”, usually I got the “create” envelope email, from DocuSign, but never the one to sign it. So I signed the document from the DocuSign page and then I got the “complete” email, but no the email that request the signature.Even from the DocuSign dashboard I select the envelope and hit the “resend” button and still not getting the email. I checked the the email address is correct. Is there a setting that I need to change?

Hi all,I'm currently working on integrating DocuSign into my C# application. One of the features I’d like to implement is Signing Groups. While I can see that the DocuSign REST API does support Signing Groups (as referenced in the official documentation), it appears that the DocuSign.eSign.dll NuGet package does not expose equivalent functionality.Could someone confirm if this functionality is currently missing from the NuGet library, or if there’s an alternative way to access Signing Group features through the SDK that I might have overlooked?Thank you!

In my Salesforce org, I’ve installed the eSignature app. I’ve successfully configured and activated the app user, and I’ve also created an envelope. Now, I want to send a PDF file as an attachment to the client using that envelope. This should be done automatically through Apex, triggered after a specific action. The email should include the DocuSign envelope and attach related documents from the record. What I need to know is: how can I use Apex to send an email to the customer, using the existing envelope and attaching the related existing documents?Note:Is this possible to implement? Can it be done using only Apex, or with Flow, or both?

HiI'm using the PHP SDK for esigning, working all great, we have all kinda of different dynamic fields, checkboxes, radio fields, text fields, etc. working great, but now the client has asked us for the following:Whenever the client has signed the PDF and the signed the PDF is returned either by mail or the webhook, the PDF only contains the filled in values, so the checked checkboxes, selected radio boxes for example, leaving a white gap where the user made no choice. Is it possible to make DocuSign render all elements?How the signed pdf is now (user selected no):How we would like to have it:  

I’m programmatically adding CheckboxGroup and RadioGroup fields to a 2-page PDF using the DocuSign REST API (SDK version 5.5.0). During signing, the signer can interact with the checkboxes and radio buttons without any issues.✅ During signing: Checkboxes can be selected Radio buttons can be chosen ❌ Issue after signing: In the final completed PDF, the selected fields show an "X" mark instead of the expected checkmark (✔) for checkboxes or filled circles for radio buttons. 🔧 Details: Using DocuSign eSignature API SDK Version: 5.5.0 Fields are added via CheckboxGroup and RadioGroup Environment: Developer Sandbox (demo.docusign.net)   ❓My question:How can I ensure that the final, signed PDF displays: ✔ checkmarks for selected checkboxes, and ● filled circles for selected radio buttons?

Using the Docusign eSignature API, I’m able to send envelopes w/o any issues. I am not setting the expiration date when sending the envelope, but do have a setting on my account with a value of 3 days. My question is, is there a way to get the value of the expiration date (or days that the expiration date is configured for) when the envelope is created, without an additional request being sent via the API to retrieve the envelope details or to get the value from my account?I’m trying to avoid bumping up against any rate limits.

We built an integration with DocuSign SOAP APIs in 2012 and a few of our clients are still using them. We are hitting the end points https://demo.docusign.net/api/3.0/dsapi.asmxhttps://na2.docusign.net/api/3.0/dsapi.asmxhttps://www.docusign.net/api/3.0/dsapi.asmxto create envelopes for our clients. Recently, we noticed that whenever we add the custom tags for the recipients, they are automatically are required, even if when have not specified the customtabrequired property to true. Whenever we require the custom tag, we specify the two properties to true.CustomTabRequired = trueCustomTabRequireSpecified = trueCan you please let us know what else we need to specify and why all of a sudden these custom tags are required?Thanks

The template below is currently configured to display a voided envelope when the email address is updated. At present, the content is static. Have a requirement to display different text based on either a flag / custom field when making a call to v2.1/accounts/xxxxx/envelopes/xxxxx/recipients?resend_envelope=true How can I pass a custom field and make this template conditionally display text based on that custom field? Appreciate your support!