Help Forums

We have recently noticed amongst multiple document signature cases that the candidate is not putting a physical signature on the document and instead the system shows a blue "Completed".The system describes that they signed using mobile, although we have do not add mobile authentication options to the signature flow process.We tested the system and after clicking "Finish", the system no longer asks the candidate to add a signature. Is there a way to restrict the system so that candidate would have to add a signature and how?

We’re building an integration where envelopes are created via the DocuSign API (through Make.com). The goal is to customise the Completed confirmation emails (subject and body).I reached out to DocuSign Support, but I’ve been bounced around and still don’t have a clear answer. So I’m putting this out here:🔹 Which plan level unlocks the Branding feature so we can create and reference brandId values?🔹 Once branding is enabled, can we use:PUT /restapi/v2.1/accounts/{accountId}/brands/{brandId}/resources/emailwith a custom XML resource file (including <completedSubject> and <completedBody>) to fully customise those confirmation emails?🔹 Can HTML and placeholders (like signer name or envelope ID) be used inside those tags?🔹 If we specify {brandId} when sending envelope

DocuSign has any feature that can automatically remove users or integrate them for this?

Hi DocuSign team 👋,I’m integrating Identity Verification (IDV) in our Laravel-based app and connected it with a DocuSign Connect webhook.Everything works fine for regular eSignature events — I successfully receive: recipient-completed envelope-completed envelope-voided, etc. However, I never receive the two Identity Verification events even though they are enabled in my Connect configuration:✅ “Identity Verification Pending”✅ “Identity Verification Completed”Setup details Webhook URL: (public ngrok HTTPS endpoint) Environment: Demo (developer) Using REST API v2.1 Envelope created via API with the following recipient structure:  

We’re excited to announce a new way to build with Docusign using the Model Context Protocol (MCP) Server. MCP acts as a bridge between Docusign and large language models (LLMs), enabling natural language interactions with Docusign’s agreement and workflow capabilities.With MCP, you can connect Docusign’s APIs and tools to AI-assisted environments and use conversational prompts to automate or explore actions. For example: “Give me a quick summary of my active agreements.”“Generate an access token for my demo account.”“Trigger the NDA approval workflow in Maestro.” This is the same technology that powers Docusign’s new integration with ChatG

Set the ExpireEnabled, ExpireAfter and ExpireDateTime using Docusign SDK 8 for C# and its not taking the values. Key points :Using Docusing SDK 8 with C# Using developer accountI’m creating the envelope from a template.I changed the expiration days in docuSign settingsThese are the lines of code :   // Get the envelope definition after configuration var envelopeDefinition = config.GetEnvelopeDefinition(); // Set the envelope status to "sent". The signer will get an email from DocuSign envelopeDefinition.Status = "sent"; // Set expiration date envelopeDefinition.ExpireEnabled = "true"; // Enable expiration envelopeDefinition.ExpireDateTime = DateTimeOffset.UtcNow.AddDays(14).ToString(); envel

I would like to ask for some guidance or assistance on the below.We bought E-signature Standard Licenses for 90 users. The usage shows we are within limit. But users are getting this Envelope Allowance exceeded error.I know the envelopes are shared across our plan so we should not be receiving this error.We have already opened a case to DocuSign support but it’s more than 20 days and we still don’t get any resolution.Any help would be appreciated.  

Hello!We have a signing group that needs to be able to print and sign documents, but it appears that print and sign is disabled for signing groups. I have been unable to find a good explanation as to why, or how we can re-enable it. Is there a way to adjust this setting, and if not, what workarounds have others used? The best we’ve found so far is for signing group members to “assign to someone else” and assign it to themselves because then they can print and sign, but that creates excess clicks, emails, and a Docusign error screen to boot. Thank you for any help!

Hello, I am a realtor with RPA Real Estate. I currently use Authentisign as my signing service, they use blue and yellow for the different signature fields, making it very easy to tell apart. I heard many good things about DocuSign, which is why I decided to try out the trial and possibly make the switch. my only issue so far is the colors of the signature fields. they are pastel green and pastel blue, which look very similar and are very hard to tell apart, is there a way to change this? if not, I would like to suggest using different colors that are easier to tell apart, or giving the option to choose your color for each signer would be most ideal. Thank you so much!

Hi all,I have a workflow and I need to split a document and I need to specify the page number to save into a new file.How I can find out the total number of pages in a document so I can exclude the last 2 pages?Thank you in advance.

I am encountering the following error when attempting to send a document using a static variable in my integration with DocuSign:The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying documents for Envelope ID = 95d29fa2-762b-49c6-a162-44ce4d16cd23Context:I am using a static variable to pass the document to the envelope. The envelope creation process seems to fail because it does not recognize the document as attached. Recipients and subject line are already set, but the error persists.Question:How can I ensure that the document is properly included in the envelope when using a static variable? Are there any specific steps or API parameters required to validate the envelope before sending?Any guidance or best practices would be greatly appreciated.

Hello there,I got stuck when I am trying to integrate docusign-esign node module in my spfx webpart.I’ve created a new spfx webpart I’ve installed docusign-esign module in the working directory. (My webpart package.json has the following entry…   "docusign-esign": "^8.5.0Error When I gulp serve - I am getting the following , one of so many.: 'dist':./node_modules/docusign-esign/src/index.js: Module not found: Error: Can't resolve 'ApiClient' in 'C:\Phani\Custom Development\PembinaApprovalsDashboard\PembinaApprovalsDashboard\node_modules\docusign-esign\src'Did you mean './ApiClient'? On init of my webpart, I’ve the following code.try      {        let dsApiClient = new docusign.ApiClient();        dsApiClient.setOAuthBasePath(this.DOCUSIGN_OA

Hi everyone,I’m trying to find a way to prevent users from having multiple active sessions in DocuSign — for example, being logged in simultaneously from multiple browsers or devices.I’m looking for something like: A setting to allow only one active session per user, or A way to automatically terminate previous sessions when a new login occurs. I’ve already checked the Organization Security and Session settings in the Admin Console, but I couldn’t find an option specifically for this.So my question is, Is there a way (via the Admin Console or API) to enforce single-session login for users?Thanks in advance!Chris

We’re inviting our customers in procurement to share how Docusign is supporting your workflows. What processes are you streamlining, which integrations are critical, and where do you see opportunities for improvement? Your insights will help us better understand real-world use cases and guide future enhancements.

I received a docusign document from my employer, and this was the first time I had to do the signature digitally.For that I needed an identification process with a dispatcher, where even the first 2 attempt was cancelled by the dispatcher due to technical issues. On third try we finally could start the identification, but at the end the dispatcher told me that she has technical issues so I shall call them again.However since then I stuck at the 1. Identification step with the message:“This identification for this Transaction Number has already been completed and cannot be restarted.”How can I proceed to the Sign documents step?

Hi everyone,We’re experiencing an issue with the embedded signing flow that recently started occurring (it was working fine until last week).We’re following the official guide for creating a focused signing view:👉 https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/Our backend uses docusign-esign@^8.5.0 to generate the signing URL.We include the following domains in our FRAME_ANCESTORS directive:https://our-domain.com https://demo.docusign.net https://apps-d.docusign.com The generated signing URL opens correctly in a separate browser tab.However, when embedding it inside an <iframe>, the frame fails to load and the browser

Hi allIs there a way to create a recipient template that saves recipient details and signing order for a specific company?We frequently send envelopes to the same company with the same recipients and signing order. It would save a lot of time if we could save this setup as a reusable template, so we don’t have to manually enter the same information each time.What We’re Looking For:Ability to predefine recipient names, emails, and signing order Option to select this recipient template when sending new envelopes Ideally, this would work independently or alongside existing document templatesHas anyone found a workaround or is this something DocuSign is planning to support?

Hello, We are experiencing issues with Docusign connection to Dynamics 365 CRM dropping off and requiring manual intervention to connect the 2 again, typically after a period of time where users are noticing documents are not sending. It’s not very often but often enough that it’s becoming a bit annoying for all involved when it happens. I have not seen any reason for the connection dropping, no passwords are changed and re-connecting is simply going to the Docusign settings in CRM and pressing “Connect”What we really need is some form of alert to us to tell us when the connection has been lost so that we can avoid delays, is there any way to implement this?

Hi Team,After signing the document upon clicking finish , a pop up window appears to share the document with required ones as shown below. Our customer doesn't need this. Is there anyway to suppress this. Please suggest.  Thanks

Hi I am a new user to Docusign and have sent one document out for signature. A client has signed a contract but the wrong company name is shown in the signature box. I do not think this was a requirement specified when requesting signatures, how do I correct this?

Is it possible to have the API call limit raised from the default of 3000 per hour ?   Is this based on the plan you have wit Docusign ? Can it be raised for a certain number of hours per day  ? Ex: 5pm to 8pm an then it goes back to defaultWhat is the maximum if it is possible for it to be raised ? Are there other stipulations for raising it ?Do the API limits only impact Docusign Retrieve or all aspects of sending envelopes  etc. ?What is the procedure to have it increased ?   support ticket ?  Thank YouNorman

Hi Docusign Community,I need some guidance on the correct architectural pattern for checking envelope status without violating API rules. Context: I’m a developer using the Docusign eSignature product. I have an envelope that requires signatures from two separate recipients. I need to trigger a specific operation in my application, but after both recipients have successfully signed and the envelope is complete, and when only either one of the recipient has signed the contract.  Problem: My initial thought was to call the GET /envelopes/{envelopeId} endpoint to check the recipients' status every time one of them signs. However, these two signatures could easily happen within minutes of each other. This would mean I'd be making multiple GET calls to the same envelope ID in less than the 15-minute window, which I believe violates the API polling rules. My application is already live,

HiHow would I go about sending a document to the PA of a director who will then forward to the director for signing?To whom should I address the email?

Request Failed: 400 {"error":{"message":"Model is not supported for this request.","code":"model_not_supported","param":"model","type":"invalid_request_error"}}

The big news at Docusign Discover25 was the integration of AI-enabled tools with our Intelligent Agreement Management (IAM) platform. Our Model Context Protocol (MCP) server, now in beta, supports AI-assisted tools including Anthropic Claude, Microsoft Copilot Studio, and GitHub Copilot.We also made an exciting announcement about upcoming IAM availability in ChatGPT, which will enable users and AI agents to create and analyze contracts directly in ChatGPT. Other highlights of the November newsletter:Accelerate development with our open-source micro-frontend system, Docusign 1FE.