eSignature API

It is quite important to allow closing vulnerabilities, could one please review and accept this pull request https://github.com/docusign/docusign-esign-php-client/pull/253 to allow make our system safer and also make your system safer since it’s related to the communication between the two.

Hi DocuSign team,I'm stuck in a loop trying to enable SMS and WhatsApp delivery on my developer sandbox account. I've been advised to open a support case, but support.docusign.com won't authenticate me. What I need:  Enable SMS and WhatsApp delivery on account 7ba44489-edcb-4415-9dd9-3632e018480c.What I've tried:  1. Viewed a post on this community with the same request. The reply     redirected me to open a support case.  2. https://support.docusign.com → Log in     - Tried "eSignature and IAM Applications" category → password       rejected every attempt (same credentials that work on       apps-d.docusign.com and developers.docusign.com).     - Tried "Docusign Partner" category → same rejection.  3. Attempted to sign in at developers.docusign.com and navigate     to a support form from there — no developer-specific case     portal is exposed afte

I have a template that has a single signer that is a signing group. I need to create an envelope from this template using API calls.  The API requires an email and ends up creating a new signer in addition to the signing group that’s in the template. Is there a way to create the envelope so it only has the signing group as the single recipient?

Hello,I’m currently integrating DocuSign into my ERP system using the API, and I’m working with a developer (demo) account.For several weeks, everything was working perfectly:Envelopes were successfully created via the API They were sent without any issues Recipients were receiving the email notifications and could sign documents normallyHowever, starting about a week ago, the behavior changed unexpectedly.Now:The API still works correctly (no errors returned) Envelopes are created and sent successfully Recipients are correctly assigned But no recipient receives any email notification at allTo troubleshoot, I have tried:Sending to multiple types of email addresses (personal, professional, temporary emails) Recreating a completely new developer account → it worked once for a single envelope, then the same issue occurred again

We would like to integrate an Aadhaar-based e-Signature API into our application, where as developers we can send a PDF document and allow the end user to complete Aadhaar e-sign on it.Could you please provide guidance on the following: How to use the Aadhaar e-Sign API for uploading and sending a PDF for signature The complete integration steps and workflow involved How the end-user authentication (Aadhaar OTP/biometric) is handled in the process Steps to configure and enable this feature in a demo/sandbox account for testing Any required API credentials, documentation, or prerequisites to get started We are currently in the initial integration phase and would like to test the functionality in a demo environment before moving to production.Kindly share the relevant documentation, API references, and onboarding steps.Thank you.

Hello.i’m working with a microservice API to connect my applications with Docusign APIs.I have an issue that my client web application are not alowed send document to my API for business rules reasons.There is any option to upload the document within a empty envelope over a presigned URL, that my API generates in Docusign APIs and then my web client just upload the document directaly?I have searched over API documentation but didnt found anything

Is it possible to set reminders and different reminder frequencies for each user? In other words, so that all the envelopes sent by a user have different reminders and frequencies. ¿Es posible establecer recordatorios y frecuencias de recordatorios diferenciadas por usuario? Es decir, para que todos los sobres que envíe un usuario tengan unos recordatorios y frecuencia diferenciados. Would it be possible to include in the API the option to choose the reminder frequency for each envelope? ¿sería posible incluir en la API la posibilidad de elegir la frecuencia de recordatorios por sobre? Is it possible to include in the API the ability to send copies without requiring a signature? In other words, in Docusign we can decide whether the person receives only a copy or, conversely, must sign—would this be possible in the

I want to create an envelope that would contain multiple documents using envelopes endpoint of docusign api. Here is the main requirement Sending multiple documents in a single envelope Once all the signatures are captured for all documents receiving the webhook callback Confirming that: All signed documents are returned Currently we are creating a single document per envelope and while creation we send custom field with a documentId. This field is returned in the webhook call from Docusign which help help us with downstream process. If we are able to receive multiple signed documents in a single webhook call, is there a way to have the unique identifier for each document in the response from webhook?

Hello, I’m currently trying to understand the eSignature API (I’m new to docusign). Our UseCase is to create a template for a document we want to send out to customers for signature This template should contain “variables” that needs to be pre-filled before sending out to the signee (e. g. a Customer ID or Name) Sending should work via API.I created a template with several variables (I just put random variables for testing inside, they do not make sense) Within my API Call I am able to send out an envelope with the help of a template by { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email":

Hi Team,We have a requirement where, based on a field update in Salesforce, we need to automatically void a DocuSign contract that has already been sent to the customer.I am new to DocuSign development and need guidance on the following:How to create a DocuSign Developer Account How to use DocuSign APIs to void an envelope that is already sent Best approach to integrate Salesforce with DocuSign so that, when a Salesforce field value changes, the related DocuSign envelope is automatically voided Any recommended best practices or sample implementations for this use caseIf anyone has experience with DocuSign + Salesforce integration or has implemented a similar scenario, your help or pointers would be greatly appreciated.Thanks in advance!

i am not seeing anything after successful login. tried multiple browsers incognitoconsole shows Uncaught TypeError: Cannot read properties of null (reading 'insertAdjacentHTML')Understand this error6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - WARN  2026-04-06T14:44:05.334Z Invalid eventBatchSize undefined, defaulting to 10e.consoleLog @ 6fe1b3b2-d77a1ad56503e866a7ae.js:1Understand this warning6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - WARN  2026-04-06T14:44:05.334Z Invalid eventFlushInterval undefined, defaulting to 1000e.consoleLog @ 6fe1b3b2-d77a1ad56503e866a7ae.js:1Understand this warning6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:05.445Z DatafileManager: Updating datafile from response6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:05.445Z PROJECT_CONFIG: Skipping JSON schema validation.6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:

Hi everyone, Via our DocuSign integration/ API, using recipients[].signers[].emailNotification.emailBody, we would like to customize the email message sent to each signer on a per-envelope basis as follows: - Embed protected images in that email message using CID (Content-ID). Is this approach supported by the DocuSign API? If not, we would greatly appreciate any suggestions or recommended approaches to achieve this functionality.Thanks!

Hi,I have a working DocuSign integration in the demo environment using JWT authentication and templates.When trying to move to production, I get the error:"These accounts don't support API integrations".I have already contacted sales multiple times but received no response.We are ready to go live and need API access enabled for our production account.What is the fastest way to enable this?Thanks in advance.

Hi everyone,I’m currently using the DocuSign eSignature API to create an envelope via Composite Templates. My setup involves two recipients with no signing order (parallel routing).To ensure tabs are visible to both parties, I have set the shared property to true for each tab within the inlineTemplates for the signers.The Problem: When the signing URL is opened, the shared tabs are appearing with a solid white background. I was expecting them to be transparent so they blend seamlessly with the document's underlying layout.My Questions: Is there a specific property I need to adjust / include to force transparency for shared tabs? Has anyone found a workaround to fix this? Any insights from the community would be helpful!Thank you,Quoc

Hello,>Working with the C# SDK<Using composite templates, i successfully created an envelope with 4 documents and 4 recipients (yay !)Document #2 is defined as display=”inline” and i added some tabs (SignHere, Text, DateSigned...) for recipient #1 and recipient #4 : works like a charm. Now my problem is with document #1, which is a supplemental document (display=”modal”). The goal is to set this document as “View and accept” only for recipient #4. Following the documentation I created a View tab and an Approve tab like this :Approve approveTab = new Approve() { DocumentId = "1", RecipientId = "4" };View viewTab = new View() { DocumentId = "1", RecipientId = "4", RequiredRead = "false", Required = "true", PageNumber = "1" };

I want to send multiple PDFs in a single envelope with defined signature positions. I need the signer to be able to sign at least one document and complete the signing process, while keeping the envelope active so they can return later to sign the remaining documents. Additionally, I want to receive a callback (webhook) each time the user signs a document. Is this possible using DocuSign, or should I send each PDF in separate envelopes?

Is it possible to send an envelope using the eSignature API and set up an automatic signature for a recipient, so that no human action is required from that recipient?

I am using Java for my development. Is there a way to allow the signer to choose where to place their signature? I tried leaving out the tabs field within the signer, but in that case it considers the signature as not required, or it even allows the user to "bypass" it by filling in other fields (company, date, etc.).In my case, I would like to keep only the signature option active (the person's name), and also ensure that the process is only actually completed once the signature has been provided.

We have users who have collected large numbers of envelopes and they are interested in that legacy form data. Can an admin account be set up via API to pull that existing form data and write data labels and collected data content into a file?  Or would the sending account have to be set up as the API user who pulls this data? It seems like the admin account should be able to, since it can be set to see into any account and manually pull form data from each envelope. Going forward, I see Agreement Actions could be useful for *future* data. https://support.docusign.com/s/document-item?language=en_US&bundleId=pik1583277475390&topicId=tkx1648575795345.html&_LANG=enusThis question pertains to *existing* da

I got this issue when trying to get access token. So I don’t know how to get code challenge and its method. I tried to search around them but nothing is suitable for my issue. It also tell me bout CODE_VERIFIER, and I’m stucking with how to get these values and solve my problem. Can anyone help me to resolve this issue?https://{{hostenv}}/oauth/token{ "error": "invalid_request", "error_description": "code challenge and code challenge method required"} 

We have built a Salesforce automation. When the initial contract is sent to the client and later some changes are made, we generate a second contract.At the time of generating the second contract, we update the initial contract envelope status to Void. However, we are not receiving any void notification emails. Also, we are still receiving reminder emails for the initial contract.I think the API call is not being triggered in DocuSign.Can someone advise me on how to resolve this issue?

I recently added version 6.0.0, and when trying to implement the envelope creation, the class EnvelopeHelpers cannot be found. <dependency> <groupId>com.docusign</groupId> <artifactId>docusign-esign-java</artifactId> <version>6.0.0</version></dependency>

We have org admin permissions but we are unable to create user with status as ‘Active’ using this POST request https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/users

Hi all,I’m stuck with a DocuSign JWT Grant issue and would appreciate help from anyone who has seen this before.ProblemCalling the token endpoint consistently returns:{ "error": "invalid_grant", "error_description": "user_not_found"}Token RequestPOST https://account-d.docusign.com/oauth/tokenContent-Type: application/x-www-form-urlencodedgrant_type=urn:ietf:params:oauth:grant-type:jwt-bearerassertion=<signed_jwt>JWT Details alg: RS256 iss (Integration Key):0a09f94b-xxxx-xxxx-xxxx-722da7e2846a sub (User ID):3af994a5-xxxx-xxxx-xxxx-adf23dce0cd3 aud: account-d.docusign.com scope

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