eSignature API

Web Form In our travel form we use a formula to pull information from the form to act as the email subject.  I find the inconsistent use of underscores.The information being pulled from the form is from the Web Form Field API reference name and that information does not allow spaces:Travel Start DateAPI reference Travel_Start_Datethere are underscores in place of the spaces for the API referenceWhen you use the information in the formula, the underscores need to be removed:[[ECF:Travel Start Date]]When the email comes from Docusign there are underscores where the spaces used to be. Email subject 2026/05/14_Initiator_Firstname_Lastname_Travel_Destination_NameI’m not sure where this development evolved but the inconsistencies of underscore for spaces v

Hello DocuSign Support Team,I am experiencing an issue with pre-filling document generation (DocGen) form fields when creating and sending an envelope via the REST API. Despite trying multiple approaches, the fields are rendering as unresolved placeholders (e.g., {{Agreement Party}}, {{demo_field}}) in the document instead of showing the values passed through the API.---ENVIRONMENT- API Base URL: https://demo.docusign.net/restapi/v2.1/- Template ID: 3cfaca9c-ffd5-4c16-a416-992ca05317b0- Template Name: Final Contract AI- Document Type: .docx (ACE/DocGen format — isAceGenDocument: true)---FIELD DETAILS (from template response)The template contains two DocGen form fields confirmed via GET /templates/{templateId}:1. Field Label: Agreement Party   Internal Name: AgreementParty_displayName_Z2bXg

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

Hi Team,We are facing an intermittent issue while integrating with DocuSign using the Node.js SDK.Issue DescriptionWe are calling the createEnvelope API from our Node.js application. In some cases: The API call times out (60 seconds) on our side However, the envelope is successfully created in DocuSign within ~7–10 seconds A webhook (Connect event) is also received successfully The problem is that the API response is not received by our applicationExpected BehaviorThe createEnvelope API should return a response with envelopeId once the envelope is created.Actual Behavior Envelope gets created successfully Webhook is triggered But the API call results in:

[Posted originally on Partner Innovation Community, but this is probably a better place to post]Hi all — Rafa from Simple Proof here 👋 Quick intro: we're a DocuSign ISV partner. We've built an Extension App that generates cryptographic proofs of completed envelopes and anchors them to the Bitcoin blockchain. In plain terms — when an envelope completes, we hash the final signed PDF and create a tamper-proof timestamp that anyone in the world can independently verify, forever, without trusting us or DocuSign. Our customers include government agencies and election authorit

Hi all,First post here so be patient with me :)I created a template a few pages long with signature and date of signing lines.The workflow is:Fill out form on web app Web app uses form data to replace text in a word file (agreement) and in turn, sends form data (recipient) and document to DocuSign to create envelope. The template is also set in code for use.Intended outcome:Client opens document, clicks to sign and date - job done.Actual outcome:Client opens document, nothing to click - no signature or date fields present.Envelope Inspection:Looking at the document in the created envelope, the signature and date fields are not there (although the template is applied). The document does not show page breaks in this view either.Manual Test:I clicked “Use” on the template, entered recipients and clicked next - signature fields are there

https://support.docusign.c> Document file limit:om/s/articles/DocuSign-Document-and-Envelope-File-Size-Limitations?language=en_US)Hello, I have a question similar to In my envelop, we send the following files which I converted to base64 : ```Size Name299k 69e772f5b28637.57190393.pdf.b64521k 69e772f5cf6a18.49898668-1.pdf.b64521k 69e772f5cf6a18.49898668.pdf.b641.5M 69e772f5f03d22.08961500.pdf.b644.1M 69e772f6b8acf3.84730872.pdf.b641.0M 69e772f7bc72c.pdf.b644.0M

Hi DocuSign Community,I am currently in the planning phase of integrating DocuSign eSignature into our real estate agency platform, which consists of a Laravel-based web portal and a Flutter mobile application (iOS & Android). I have a few questions regarding licensing and API integration that I hope the community or DocuSign team can help clarify seeing the email support only for trial/paid account. Even the chat doesn't work for me no matter how i tried to initialise it.---LICENSING & PLAN QUESTIONS1. We are planning to use a single DocuSign account/license across our platform, where multiple agents will be sending documents to clients for e-signature on a daily basis (after each case submission). Is this allowed under a single license, or does each agent require their own?2. What is the envelope (document) sending limit per month or per year under the Standard or Business Pro plan? If agents are sending documents daily, is there a risk o

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

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?

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?