Unanswered questions

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

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?

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,A signer for our company needs to sign numerous contracts weekly and their inbox is suffering. Does your company have a workaround or solution for this scenario?  It looks DocuSign does not currently have a built-in feature to send a single consolidated weekly notification to a signer for all envelopes pending their signature rather than sending individual emails every time an envelope lands in their queue. . Thanks!

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,

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?

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?  

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,

Account is suspended due to non-payment of invoice.  The Administrator is no longer here and DocuSign will not let me know who the second administrator is.  I’ve guessed multiple people, but all incorrect guesses.  I can pay the invoice, but DocuSign will not let me.  I have to find out who the second administrator is.  Seems like a flaw with the DocuSign account system.  People come and go all the time and someone may not think or have time to reassign their administrator rights before they leave.  Any suggestions? 

I have a question about what is considered to be “best practice” for the use of service accounts connecting to integrations.  Our company is starting to request more external application integrations with DocuSign.  The few are connected currently each have their own service account created and given an exception to bypass SSO with admin privileges. I see this becoming more of a burden since accounts require an email address and a mailbox must be configured to receive external mail for verification of any edits to that DS account registered to the email address.On the flip side, I also feel that it is less secure to have 1 service account for connecting all integrations.How is this being managed elsewhere?  Thanks for any feedback!

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 =

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

We are migrating an existing DocuSign SOAP integration from legacy authentication to App Password authentication and need clarification on one specific scenario.Our current SOAP authentication flow is:1. The user enters their DocuSign credential in our application.2. We authenticate using `credential.asmx`.3. We call `GetEncryptedPassword()` on `accountmanagement.asmx`.4. We store the DocuSign-issued encrypted password returned by `GetEncryptedPassword()`.5. Subsequent SOAP calls (`api.asmx`) authenticate using the `[IntegratorKey]email` username format and that encrypted password through WS-Security / `X-DocuSign-Authentication`.We have tested replacing the user's regular DocuSign password with an **App Password**. The initial authentication and `GetEncryptedPassword()` call succeed.We need confirmation on the following two questions:**1. If `GetEncryptedPassword()` is called after authenticating with an App Password, are subsequent SOAP API calls using the returned encrypted password

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

Hi,After mapping signature fields in the forms in Keystone to Docusign, we are able to submit forms from Keystone to Docusign without having to check the Suspend On Start checkbox in keystone before submitting to avoid the SOAP error. The form automatically submits, but only the primary gets notified. The joint does not get notified. Has any one else faced this issue?

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 ?

We recently downgraded to the free plan. We understand that support is only available via chat for free plan users, but the chat support option appears to be disabled and we’re unable to click the button. Are we still able to get support under the free plan?

We have a 120 day expiration period on all our envelopes, but one client is saying the link they receive has expired despite it being within the 120 days.They are the second signer of the envelope before it comes back to us; is this anything to do with it? Is there a certain time period between the first signer completing their section that the second signer has to complete their section or the link will expire?

Finally figured out how to delete my docusign account, but I had to create this account on community site to find out how to delete the other account. ***[Removed - Inappropriate Language] ***

The question relates to a Management of Change Request and Approval Document. It steps through 21 numbered sections in order. Once a section is signed it is completed but there are subsequent sections requiring minimal entry then the document progresses to the next section 5 and 6 need to be signed and dated by 2 separate individuals then later section 7 has an event date added (I’ll probably sign that as well) section 17 has a group of stakeholders (including two of the previous signatories) review the proposal, sign on the progress to date and accept/reject the proposal Section 18 is authorisation to implement the change based on the recommendation/acceptance from section17 section 19 subsequently has 3 dates added to existing fields section 21 is post change review whixch is completed, signed and dated by yet another signatory CompletedThankfuk for any assistance. RegardsDarryl

am building a multi-tenant SaaS product and I want to make sure I pick the correct integration type before I promote my integration key.Setup:- One integration key, eSignature REST API, Authorization Code Grant, confidential client- Each customer connects THEIR OWN existing Docusign account via OAuth consent- Envelopes are created in, sent from, and billed to that customer's account- No reselling, no billing through my company, no embedded signing ceremony in my UIWhat the docs say, as I read them: "private custom integration" is for customers building an app for their own use, while "public integration" is for apps used by multiple Docusign customers and requires Docusign Partner Program membership to go live.My questions:1. Does my setup count as a public integration, or does private custom cover it, given that every account involved belongs to the customer and not to me?2. If it is public, is Partner Program membership enforced at go-live even when there is no reselling and no embed

Ao tentar baixa o envelope o mesmo não baixa, - erro apresentado,  {"errorCode":"COMBINEDDOWNLOAD_UNABLETOGENERATEPDF","message":"Unable to generate combined PDF. Please download the documents as an archive."}segue numero do envelope - *information removed due to PII*

We are currently integrating Workday with DocuSign for document generation and electronic signing. We would like to clarify how documents/envelopes originating from Workday are stored and managed within DocuSign.Could you please help clarify the following:When a document is generated from Workday and sent to a recipient through DocuSign, is a copy of the document/envelope stored within our DocuSign account? If yes, where can the envelope and its associated documents be viewed in the DocuSign portal? Who will be able to view these Workday-originated envelopes by default? The Workday user who initiated the transaction? The DocuSign integration/service account? DocuSign administrators? Other DocuSign users within the same account? Can a DocuSign administrator automatically view or download the documents contained in these envelopes, or would Shared Access / another permission need to be explicitly configured? If the envelope is owned by a Workday integration/service account, can anoth

I am trying to access my DocuSign account but am not receiving emails. They are not blocked or going into junk/spam for my hotmail address but this is an issue because apparently my pension provider is trying to send me emails via Docusign and I’m not receiving them and I can’t log into my account because I can't receive the access code supposedly sent to my email address

I created a digital signature but the document that needs my signature does not use the signature I created.  How can I force the document that needs my signature to use the signature I created?