Developer

Hi everyone, Has anyone encountered this error when trying to connect DocuSign Demo/Sandbox to Zapier? We’re trying to set up this workflow:Client signs DocuSign agreement → Zapier detects the signed envelope → Kajabi grants the client access.However, when we select Demo/Sandbox in Zapier and try to connect our DocuSign account, the OAuth login fails with:Connection Failed — OAuth Failed: Cannot read properties of undefined (reading 'account_id') We’ve already tried logging in again and also tested the Production option in Zapier. Production connects successfully, but it searches the Production environment, so it cannot find our test envelopes that are in Demo/Sandbox and returns:No envelope found We specifically need to connect to the Demo/Sandbox environment for testing.Has anyone experienced this account_id OAuth error before? If so, what was causing it and how did you solve it? We’re wondering if it could be related to the Demo account's primary/default eSignature account, account

Hello, we are working on a project to make the DocuSign solution available to our Group Treasury.We have some questions for you and need specific answers due to the confidentiality of our activities and clients. Could you please help us answer the questions below:When data is collected by DocuSign, can they be anonymized? Where are they stored? How long is the data collected by DocuSign (accounts, identity documents, photos, videos, etc.) retained? After how long is the data (accounts, identity documents, photos, videos, etc.) deleted ? For example, for a user who leaves the group and therefore will no longer be able to access his account. Can we have a RACI matrix of access to different types of data? What are the different levels of access depending on the position/responsibility? For example: access to logs, signed documents, videos, identity documents. This is related to the previous question Describe the steps in the procedure for signing a complete document with video verificatio

We have a public integration built and tested in the demo environment. Each user connects their own Docusign account via OAuth; envelopes are sent from and billed to the users' own accounts. We are not reselling or embedding Docusign.We cannot submit the Partner Program application. The form at partners.docusign.com/s/join-now fails every time with "Failed to Insert record — List has no rows for assignment to SObject". Latest attempt: 2026-08-10, English-only ASCII input, corporate email domain, clean incognito session with extensions disabled. No field-level error is shown, so this appears to be an uncaught QueryException rather than a validation error.Question：Is there an alternative way to submit the application, or could a Partner Onboarding rep set us up directly? I can provide the exact submission timestamp and email address for the Apex debug log.

Hi,I'm experiencing an issue in the DocuSign sandbox (demo) environment where invitation emails for API-created envelopes stopped delivering around July 30, 2026. The audit log confirms the invitations are being queued, but no email arrives at any recipient address.Environment:Demo/Sandbox: account-d.docusign.com SDK: DocuSign .NET SDK v11.0.1 (REST API v2.1) Auth: JWT server-to-server (User ID:*information removed due to PII)

We are a Salesforce ISV partner using DocuSign SOAP API for last 10+ years. I understand there are tons of resources available and we would like to make sure we are on the right track for the migration. To give some context, we have our own logic to create PDF, manages DocuSign custom tags, send to recipients. This is working till date, however, once the document is sent, it is not tracked back into Salesforce. We are getting below errorErrorCode = INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, Fields = , Extended = .; SalesForceIntegration failed, dsfs__DocuSign_Recipient_Status__c failed, message: Unable to insert into dsfs__DocuSign_Recipient_Status__c,We believe this is related to legacy dsfs package. So the ask is 2 foldsIs there an article for ISV vendors on how to switch to REST? Once Document is sent via REST, will any customer using the new app “DAL” able to track the status back into Salesforce? 

We are using the ListStatusChangesAsync API to retrieve DocuSign envelopes for multiple account numbers. For each account number, a separate API request is sent to fetch the related envelope details, including documents and custom fields. All requests are executed in parallel, and the responses are combined into a single result set.We have observed that the loading time increases as the number of account numbers increases. We would like to understand the following:Does DocuSign apply any throttling or delays when multiple API requests are executed simultaneously? Is there a recommended limit for concurrent API requests? Does retrieving additional information, such as documents and custom fields, significantly affect performance? Is there a more efficient approach for retrieving envelopes associated with multiple account numbers?Any suggestions or best practices would be greatly appreciated.

Two years ago, I created a DocuSign developer account and an application within it. I now need to log in to rotate the keys.Unfortunately, the Gmail address linked to my account was deleted long ago during a switch of work accounts and cannot be recovered.Logging back into DocuSign now requires entering a verification code sent to that old Gmail address.How can I regain access to my account? Can anyone help? I hope the support team can assist me with this.Thanks in advance.

Hi All,We have a custom integration that sends envelopes using the DocuSign eSignature API. To retrieve the signed documents, we use an envelope-level Connect webhook with a unique identifier in the webhook URL for each envelope. We also assign a unique DocumentID to each document in the envelope so we can reconcile the completed documents with the corresponding document in our lead application.We have encountered an issue when users copy an envelope from the DocuSign web UI. This causes two main issues :The copied envelope resets the DocumentID values to the default sequence (1, 2, 3, etc.), so we can no longer map the completed documents back to the original documents in our application. The envelope-level Connect configuration including the unique webhook URL is also copied. As a result, our application receives unexpected webhook notifications for the copied envelope. Since the copied envelope was created directly from the DocuSign UI rather than through our integration, our lead a

We are using the ListStatusChangesAsync API to retrieve DocuSign envelopes for multiple account numbers by passing the account number as a custom field.var tasks = accountNumbers.Select(async accountNumber =>{ var options = new EnvelopesApi.ListStatusChangesOptions { customField = $"Account Number={accountNumber}", fromDate = DateTime.UtcNow .AddDays(-Convert.ToInt32(envelopeRequest.EnvelopeDay)) .ToString("MM/dd/yyyy"), include = "documents,custom_fields" }; return await envelopesApi.ListStatusChangesAsync(accountId, options);});For each account number, a separate API request is sent to retrieve the related envelope details, including documents and custom fields. All requests are executed in parallel, and the responses are combined into a single result set.We have observed that the loading time increases as the number of account numbers increases. In the production environment, some users may have more than 10 account numbers,

Let’s says I use this envelope endpoint to return a list of envelopes that I’m interested in:GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}For each envelope, how can I find the next steps required to progress the envelope to a completed status or closer to that status.  Should I get the recipients result for the envelope and check the status of the signers?   Should I do that for the agents,  carbonCopies, editors, witnesses, etc?  Is there some api call that can do that?

The Docusign-esign-java libary released a new version (6.7.0) last on 7/1/2026; however, it still uses a version of com.fasterxml.jackson.core (2.17.1) that has a vulnerability (CVE GHSA-72hv-8253-57qq).  This vulnerability was fixed in version 2.18.6 and 2.21.1.  When can we expect docusign-esign-java to be updated to use a jackson.core version with the fix?This is the entry in my pom.xml        <dependency>            <groupId>com.docusign</groupId>            <artifactId>docusign-esign-java</artifactId>            <version>6.7.0</version>            <classifier>shaded</classifier>        </dependency>If I remove the shaded classifier then the application throws an error (java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/util/ISO8601DateFormat) when it tries to create a  com.docusign.esign.client.ApiClient 

Hi Team,I am implementing the DocuSign Payments feature using the C# .NET SDK and would appreciate some guidance.My requirement is to:Upload a PDF document through my ASP.NET Core Web API. Create a new envelope programmatically (without using an existing envelope ID). Add a signer. Add a Payment Item field to the envelope. Configure a payment amount. Send the envelope so that the signer is prompted to make the payment during the signing process.I have reviewed the Payments documentation and several community posts, but I could not find a complete REST API or C# SDK example that demonstrates how to create the Payment Item field programmatically.Could someone please clarify the following?Which REST API endpoint or .NET SDK classes should be used to add a Payment Item field while creating an envelope? Is the Payment Item field represented as a Formula Tab with a paymentDetails object, or is there another recommended approach? Is there a complete C# (.NET) example that uploads a PDF, creat

I'm getting a 404 The URL provided does not resolve to a resource when POSTing to create an envelope from a Spring Boot app using RestTemplate.My URL is built like this:javaString url = baseUrl + accountId + "/envelopes";// baseUrl = https://na4.docusign.net/restapi/v2.1/I'm sending a POST with a Bearer token and a JSON envelope body containing a base64 PDF document.What I've tried: confirmed the access token is generated successfully, confirmed the account ID is correct.Question: Is my endpoint path correct? Do I need an accounts/ segment, and how do I confirm the correct base_uri for my account's region?Environment: Java 17, Spring Boot, DocuSign eSignature REST API v2.1.

Goal: Embed signing in our web app via an iframe with a working change language function.When we render the signing URL in our webpage, in an iframe, and then we try to change the language as in the screenshot below:  We get  apps.docusign.com refused to connect error message Front-end logs shows also:Framing 'https://apps.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://apps.docusign.com". The request has been blocked.Have anyone faced this issue before, and is there a workaround to make this change of language function actually work in embedded signing?Account type: developer/demo. Thanks!

Hi,Using Docusign JS to render the focused view version of document signing I have an issue where the document is stuck loading after signing and pressing submit.This only occurs if I perform the 2FA within the same opened window.For example, if I 2FA, close the document and re-open it (I am already verified and not re-prompted for 2FA) then sign the document and press submit the sessionEnd event is triggered and the page closes as expected.It temporarily says submitting, and then the <div data-qa=”embedded-nav-container”> is replaced with <div data-qa=”embedded-document-loading”> and it is indefinite.The JS console only contains this error, but given it works when not doing the 2FA flow immediately prior to signing I don’t suspect this is the issue.`Framing 'https://apps-d.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://apps-d.docusign.com". The request has been blocked.`Any help would be appreciated and happy to pro

JWT GrantI am new to Docusing and was going through the documentation. I stumbled upon the Authorization Grant of the Platform 101 docs, and read the above excerpt. Can anyone clarify what does this mean If you use a single login for all users in your integration, you should use JWT Grant.  Using single login for all of the integration users mean what? Does that all follow the same login/signup method or the same credentials?

I am on the Basic API plan which provides 40 envelopes per month. My issue is that since I have started this plan, I have been getting Envelope Limit Reached notices in error. Last month it cut me off after 1 envelope (and the whole month I was trying to get support to fix the case to no avail), and once the new month reset, it cut me off after 5 envelopes. The Support team has been absolutely useless the entire time. I have probably contacted them over 25 times, and get different answers and that the “internal” team, or “engineering” team is taking a look. But it never gets fixed. I am at my end here and will probably move to PandaDoc or another provider soon if this doesn’t gets fixed quickly. 

Hi, I wanted to reach out to the customer support from my developer account, but I was not able to start a conversation with a chat because the action simply does nothing. I tried other browsers, another device, incognito, still nothing. When I log in with my trial account, I am redirected to using the chat again, which is not working. I have no way of contacting support now.  

Hi ​@TCarpenter   ​@KimmyK @JohnSantos ,I have been facing an issue where there are two connectors created by me.For one the environment columns is Production and the other as DevelopmentHowever, I am unable to differentiate when to use https://account.docusign.com/oauth/auth and when to use https://account-d.docusign.com/oauth/authThe same request for a connector in Production works with account-d but with https://account.docusign.com/oauth/auth It gives an error“Something went wrongThe redirect URI is not registered properly with Docusign”But the same redirect uri works with account-d and same clientId, scope, redirectUrl combinationAlso, I have been facing another issue where getting a response errorcode: 400 BAD_REQUEST, message: <400,{"error":"invalid_grant","error_description":"unauthorized_client"}Although this connector is also in the Environment “Production” with the same configuration as the earlier Production Connector mentioned above.Thanks for the help.

I am using a DocuSign Developer (Demo) account and created a Web Form in the same account.I am able to access and edit the Web Form from the UI using: https://apps-d.docusign.com/send/forms/edit/{formId}I am authenticating using JWT OAuth, and the access token is generated successfully.However, when I try to call the Web Forms API, I consistently receive 404 Not Found.GET Request GET https://apps-d.docusign.com/api/webforms/v1.1/accounts/{accountId}/forms/{formId}POST Request POST https://apps-d.docusign.com/api/webforms/v1.1/accounts/{accountId}/forms/{formId}/instancesBoth requests return 404 Not Found.I have verified:The account ID is correct. The form ID is taken from the Web Form edit URL. JWT authentication is successful. The Web Form was created in the same developer account.My questions are:Are these the correct Web Forms API endpoints? Is the Web Forms REST API available for all Developer (Demo) accounts? Does the Web Forms API require additional account enablement or OAuth sc

I would like to use the API to automatically sign a document without the user having to receive an email, go to the site, sign and complete the process there.  I am wondering if it’s possible to sign the document with a previously created signature and prepopulate some of the specific fields on the document.

We are unable to use checkbox in the payload as it not recognizable inside the Oracle Integration Cloud iPaaS "checkboxTabs":[     {       "tabLabel": "Terms_And_Conditions",      "selected": "true"     },     {       "tabLabel": "Newsletter_OptIn",      "selected": "false"     }]