Unanswered questions

Hello, when I send a document to be signed the original text starts to fade. After sending a few times for signatures you can hardly read the original text. Signatures seem fine but the original text is almost not legible. Any ideas on how to fix this. Thank you

We use DocuSign for contracts.  These contract swill have multiple multi-page documents within.  We’d like to have the ability to have page numbers add after the documents get combined in DocuSign for approvals. This would allow the approvers to see a total page count of the entire envelope.

Hi, I'm building an integration against a developer demo account and I've run into RECIPIENT_LIMIT_EXCEEDED. I'd like to understand the limit before deciding how to move forward.The account is on the plan DEVCENTER_DEMO_RESTRICTED_JUNE2025, which I got from GET /restapi/v2.1/accounts/{accountId}/billing_plan. It was created a couple of days ago and sent around 19 envelopes, mostly with 4 to 6 recipients each. Now every send fails with:{"errorCode":"RECIPIENT_LIMIT_EXCEEDED","message":"You have reached the maximum number of recipients permitted for a single transaction in your account. Please ask your administrator to increase your limit."}It is not a per envelope problem. I reproduced it with a direct API call creating an envelope with a single recipient and "status": "sent", both as a signer and as a certified delivery, and both return the same 400. Envelopes sent earlier that same day went through fine, so it looks like a cumulative allowance rather than a per envelope cap.Three ques

Hi there, i sent an envelope with some documents for signing. 5/6 people have signed and the 6th person does not need to sign (he doesnt have any signing fields however he was still selected as "needs to sign") I do not have a "manage" tab or a "correct" option. What can i do to remove him? I am the owner of the account so have all of the correct permissions

Occasionally I get an Invalide Date error message in Docusign after entering a valid DOB on Date field in Docusign webform.We do noth ave any special case or extra logic on date field, Just a standard Date.Note:- Most of the time looks good but happened few times and our QA engineer also observed few times. Anybody know why?  

Been using an esig  version for 15 days. Seems like a nice robust product but it also seems buggy. Today I began to receive the error Max ricipients per envelope transaction. I only have 3 recipients configured to receive so I do not understand. Is there a different reason and if so how can I correct it so that I can continue to eval? we like the product but onve we purchase it we go live so these  showstoppers must understood now. I have uploaded the error. Any suggestions can also be emailed to  T*************@*****.com **attachment removed as it contains PII**

Hello, On our company we are in the process of transitioning from accessing the documents using a general account where everyone can see everything to a single sign-on perspective.The way we work is that we are separated into teams (markets) and we want people from the same team to have full visibility of envelopes and templates. This way, if someone is on holidays or leave, the other can access and manage their documents.When it comes to Templates, this goal is easier to be achieved as we created groups and templates are visible within the users inside the group.Now with Envelopes, we are having more difficulties. We tried the Shared Envelopes option but then if we need to search for a specific envelope, we need to do that for each person that we have access to - not ideal.Imagine a scenario where we have employees A, B and C. Ideally:> they are part of a group with shared visibility. If employee D joins, they are put on the same group> they can see each others templates and env

Is there any capability to….Proved AI Summary provided with signature request to signee that has information on what their signing 

I have a client who disputes a docusign Certificate of Completion.  He believes the person who created the envelope also signed it as the recipient without his permission.  I have the Certificate and some of the metadata from Docusign's response to my subpoena, but I need an expert to help me understand what I am looking at, draft additional subpoena's and deposition questions and perhaps testify at trial depending on what we discover.

Within DocuSign CLM, we would like to begin reporting more detail around errors or even successes at the signature step.  Example:  we do see a failed notification and can see that on the workflow status report, but we need to know why it failed (cancelled, expired, etc.) but am not seeing a way to produce that as an attribute.  Any recommendations or ideas?

While reviewing DocuSign integrations, I identified some important file size limitations that impact both the DocuSign eSignature REST API and the DocuSign Power Automate Connector. REST API LimitationsThe total envelope size (all documents combined) cannot exceed 200 MB.Each document must be less than 50 MB.For standard API uploads, individual document upload requests are subject to API size limits and large documents may require chunked upload methods.Envelopes are limited to 130 unique documents.Large or complex documents may fail during DocuSign's PDF conversion process, especially when conversion exceeds processing thresholds. Power Automate Limitations The DocuSign Power Automate connector has a known limitation where API gateway timeout errors may occur for documents larger than approximately 12 MB and/or envelopes containing more than 1,500 pages.

I have a Word template that I populate programmatically using C# and the Open XML SDK. The generated DOCX looks correct when I open it in Microsoft Word. However, when I upload the same DOCX directly to DocuSign and open the document for signing, I notice extra spacing between some characters in two paragraphs. The character spacing appears normal in Microsoft Word but changes when the document is displayed in DocuSign. I have added the screenshot for your reference First image: The generated Word document opened in Microsoft Word, where the character spacing appears normal.Second image: The same document opened in DocuSign for signing, where extra spacing between some characters is visible.I have also verified the font and character-spacing settings in the Word document, and they appear to be normal. Additionally, if I convert the generated DOCX to PDF using Microsoft Word and then upload the PDF to DocuSign, the spacing issue does not occur.Could you please help me understand why thi

Hello Developers, I’m Hudson. In our integration, we create templates (name, description, upload document, add recipients, add fields, save). From the template list we copy the unique templateId from the history screen. When sending envelopes in bulk, we currently paste that templateId into a custom field (TEMPLATE_ID) and then use EnvelopesApi.listStatusChanges with options.setCustomField("TEMPLATE_ID=...") to filter envelopes. This works fine — we can import only the envelopes created from that template.However, if we don’t add the custom field at envelope creation, the envelope JSON does not expose the templateId directly. We can fetch envelopes, but we cannot tell which template they were created from.Code snippet (current approach): EnvelopesApi.ListStatusChangesOptions options = envelopesApi.new ListStatusChangesOptions();options.setFromDate(fromDate);options.setFromToStatus("sent,delivered");options.setCustomField("TEMPLATE_ID=" + templateId);EnvelopesInformation envelopesInfo =

hi all,Anyone on this community attempted to use Salesforce flow and flows ability now to make http callouts and use this to make call to DocuSign?CheersBrett 

I used one of my envelopes to create a web form.  Within the web form, I changed the name of the form.  That appears correctly in the published web form, and the signed form.  However, in the “completion” email to the signer, the old form name is used in the “All parties have completed...” area.  Is this a bug?

After our Go-Live Form was approved, JWT Grant authentication to https://account.docusign.com/oauth/token consistently fails with:{"error": "invalid_request"}No error_description is returned. The identical code and request structure work without any issue against the demo environment (account-d.docusign.com).Setup:Integration Key: 9711fda1-8ceb-44d8-bb4f-1f8c54e29956 Production API Account ID: a0f9faaf-32b6-43cf-b88c-f5d5cf726596 Auth method: JWT Grant, scopes signature impersonationWhat I've already verified/ruled out:RSA keypair is registered under the app in the production account (freshly generated, single key registered, no stale/duplicate keys) User consent has been granted — visited the /oauth/auth consent URL logged in as the impersonated user, clicked Allow, and the redirect returned a valid authorization code Integration Key, impersonated User ID, and API Account ID all match exactly what's shown in production under Settings → Apps and Keys JWT payload (iss, sub, aud, scope,

I am requesting cancellation of my DocuSign free trial before it expires. I have attempted to cancel through Admin > Plans and Billing, but the DocuSign billing page returns ERR_HTTP2_PROTOCOL_ERROR. I also cannot access the Support portal because my trial account is not being allowed to log in.Please treat this message as my formal request to cancel the trial and prevent any paid subscription or charge from occurring. Please confirm cancellation in writing.

The documentation for the documentsearchtask API states that the response for a collection of documents will include a Next/Previous href to support pagination (assuming there are more results).This was working for us until early August. Then the “Next” href disappeared.I’m unable to get the Next in the response. Interestingly, if I use the limit and offset (eg, limit=10, offset=20) I do get a Previous in the response.https://developers.docusign.com/docs/clm-api/reference/tasks/documentsearchtasks/post/Is anyone else having this problem? It feels like something has changed in the response.Or can someone help with how to structure the API call so that a Next appears in the response?

Hello DocuSign team,I have a DocuSign developer account and am evaluating the CFR Part 11 signing experience for an API integration.Could you please advise whether it is possible to provision a CFR Part 11-enabled demo account, or enable the module for my existing developer account, for testing purposes? In particular, I need to test the required Reason for Signing flow and its behavior in embedded/API-driven signing.Please let me know the process, any eligibility requirements, and whether this requires a paid evaluation or a production subscription.Thank you

When trying to download the envelope, it fails - error message displayed.{"errorCode":"COMBINEDDOWNLOAD_UNABLETOGENERATEPDF","message":"Não foi possível gerar PDF combinado. Por favor, baixe os documentos como um arquivo."}Bug IM-39704?

Hey,I am developing an app that prefills all my data in a PDF and I want to send that PDF through my Docusign account to my customers to sign.I have the developer account and app in demo mode - all works fine.I am trying to get it to my live Docusign account, however it is a part of an organization - they pay for our company envelopes, so technically I’m probably not the admin (when I login I see the organization name under my name). So when I click “Select Go-Live account” from my demo account I am prompted to login and then I see this: Select Production AccountSelect an eligible production account to manage this integration key.Select an eligible production account to manage this integration key.You can't select this account because you aren't an administrator for it. Select a different account, or ask an administrator for this account to login. Learn more“CURRENT ORGANIZATION”, Inc - XXXXXXX So is there a way to finish this - the organisation is quite big and I doubt they will deal

Does Docusign have a REST API that will retrieve a record of customer acceptance of the ERSD when signing a document?  Are you able to utilize the API to bring in this data with option to save it on your core credit union platform ?  Can you provide any links to the documentation regarding the API and its uses ?

I’m using the DocuSign C# SDK to generate a Recipient View URL and load it inside an <iframe> in my application.The code and integration configuration are essentially the same, but I’m seeing different behavior depending on the demo account:Demo Account A: The Recipient View URL initially loads correctly inside the iframe and displays the authentication/verification process. However, after the authorization code is entered, the flow fails and the next page cannot be loaded inside the iframe due to X-Frame-Options / Content-Security-Policy (frame-ancestors). Demo Account B: The exact same implementation works correctly, including the step after entering the authorization code.So, the issue does not occur when the Recipient View URL is initially loaded. The iframe successfully loads the authentication flow. The problem happens after the authorization code is entered, when DocuSign redirects/loads the next page. The browser error is related to the page not being allowed to be displa

Hi ​ ​@JohnSantos ​@marieelia I am now able to send documents successfully via the REST API.However, I am not receiving the envelope status updates such as Sent, Completed, Declined, etc.I have installed the DocuSign Salesforce package, and I would like to create/update the status records in the following Salesforce object:dfsle__EnvelopeStatus__cI am currently getting the following error from DocuSign DAL: {"result": "SUCCESS","error": null,"data": {"status": "Ignored","message": "Not a Salesforce/DAL Envelope","requestId": "b29bd402-9739-4fb1-a03f-03f77150fc23"}}Could you please help me understand why the REST API-created envelope is not being recognized as a Salesforce/DAL envelope and what configuration or changes are required to have the status records created in dfsle__EnvelopeStatus__c?Thank you.

Hello DocuSign Support Team,We are currently integrating with the DocuSign eSignature REST API v2.1 and have a question regarding the following endpoint:GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}In our application, we use this endpoint to retrieve information about previously created envelopes. However, we have identified some cases where the request fails with errors that are not currently mapped in our application.One specific scenario we are investigating is related to the age of the envelope/signature. We have cases where the document was signed more than three months ago, and when we try to retrieve the envelope using the endpoint above, the request fails.Could you please confirm whether DocuSign has any retention, expiration, or API access limitation for envelopes or signatures older than three months?Additionally, we would like to know where we can find the official documentation for the possible errors returned by this endpoint, including the errorCode, HTTP status,