Recently active topics

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

Hello DocuSign team,We are migrating our eSignature integration from Adobe Sign to DocuSign and have encountered a limitation with automated recipient reminders.Our integration uses hybrid signing. Each signer is created with:A clientUserId deliveryMethod: "email" embeddedRecipientStartURL: "SIGN_AT_DOCUSIGN"This allows recipients to receive the initial signing email while also letting them open an embedded signing session from our application using the Create Recipient View API.We configure envelope reminders through the notification.reminders properties, but understand that automated reminders and expiration notifications may not be sent to this type of embedded/hybrid recipient.Could you please confirm:Is this expected behavior for recipients using clientUserId and embeddedRecipientStartURL: "SIGN_AT_DOCUSIGN"? Is there a supported way to enable automated reminders while retaining both embedded signing and the initial email invitation? Is there an API-supported alternative for perio

Hi there,I’m testing out DocGen for Salesforce and have been really impressed by the tool so far. The process is pretty smooth and easy to use, but I’m wondering about the flexibility of “Document Rules” under the “Upload Documents” step. As I understand it, these are designed to give you some conditional logic for dynamically deciding what documents are generated based on field data in the primary object. However, I’m wondering if there is any way to build rules that reference field data from related (parent or child) objects. In my case, the object I’m using is a junction for multiple related objects, so it doesn’t have all the field data immediately available. This was fine when building the document itself, but it doesn’t seem like I can reference any of those related objects for the purposes of a document rule.For example, my primary object (Contract) is related to the Product object, which contains data about the “type” of document I want to generate. If the type = A, I want to g

Does IAM for Enterprise Core includes integration connector for Salesforce as part of plan?

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

I am sharing this in hopes that it reaches others who may be in a similar situation or just anyone in general. I recently have had some financial issues and have also been working on improving my credit . I was delighted to see some "excellent approval odds" on several personal loan companies in which I applied.  After applying and getting rejected so many times I gave up.  Well to my surprise I received an email from some sheisty sheisters posing as Lending club! WOW I was finally approved!! All this hard work finally paid off?? Being that they were using docu-sign i thought for sure this must be legit. Haha nope but I sure did fall for it.  E- signed these lovely documents which said I'd soon be receiving $3000 electronically straight into my bank account. I just needed to provide every personal detail I could to have my identity stolen 😭 I was so overwhelmed with racing thoughts of excitement over all the debt I could finally pay off and what I'd be able to accomplish that it truly

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?

I am writing to formally raise a complaint regarding the handling of our account and, in particular, the level of service we have received from your sales team.Firstly, the sales representative, Dooa Handy, provided us with information regarding the cost of our renewal which was incorrect. I have the email correspondence to evidence this and am happy to provide this as part of the complaint.Since then, I have been trying to obtain some fairly basic information from Dooa to enable us to make an informed decision about which agreement we wish to take forward. Despite contacting and chasing him on numerous occasions, I have received no response.I have also raised this with his manager, Omar Khaled, but unfortunately this has not resulted in the issue being resolved either.What is particularly frustrating is that our account has now been stopped, despite the fact that we have not signed a new agreement because we are still trying to establish the information we need in order to decide whic

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?

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?

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] ***

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

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?

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

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?  

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

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,