Developer

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

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 

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?

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.

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"     }]

Environment: Demo / Developer (account-d / demo.docusign.net)Auth: JWT (API integration)Signing notification emails stopped being delivered to recipients around 2026-07-22.The same account delivered emails fine on 2026-07-15 and 2026-07-17 (recipients openedthe email link and signed). Since then, no recipient receives the signing email.What I already verified via the REST API (so this is not ordinary deliverability):- Envelope status = "sent", recipient deliveryMethod = "email", suppressEmails is not set.- Account flags are clean: envelopeSendingBlocked = false, suspensionStatus = "" (not suspended).- Recipient email is correct in the recipients API (no role suffix).- Affects BOTH an internal (account member) AND an external Gmail recipient.- Both mailboxes checked: nothing in Inbox and nothing in Junk/Spam.- The signing UI now shows: "This document is currently flagged as spam ... Not Spam ... Report Abuse".This looks like the demo fraud/spam hold that withholds notification emails wh

Hi DocuSign Team,I am working on integrating DocuSign Web Forms with our application.Currently, we can manually access and extract the submitted Web Form data from the DocuSign interface.I would like to know whether the same Web Form data extraction is possible through REST API.Specifically:Is there any REST API endpoint available to retrieve the submitted Web Form data? Can we retrieve Web Form submission details (field values/data entered by users) using API? If available, what are the required API scopes and permissions needed? Is this supported for DocuSign Developer accounts, or only specific production plans?I checked the Web Forms API documentation and found endpoints for retrieving form configurations and instances:List Web Form Instances Get Web Form InstanceHowever, I would like to confirm whether these APIs provide the actual submitted form field data or only metadata.Any guidance or sample API implementation would be helpful.Thanks.

Hello DocuSign Support,I am currently integrating DocuSign using the API with a developer (demo) account, and I have encountered an issue that is preventing me from completing my integration.Initially, when I sent envelopes from my application using a template, the recipients did not receive any email notifications, even though the API successfully created the envelope and returned a successful response. Surprisingly, the next day, without making any code or configuration changes, the same API calls started working correctly and recipients received the emails as expected.However, the following day, the exact same issue returned again. Once again, without any changes to my code, template, or DocuSign configuration, email notifications stopped being delivered.Currently, the behavior is as follows: The API authentication succeeds. The envelope is created successfully. The envelope status is "sent". The recipients are correctly assigned. No API errors or exceptions are returned.

Hi! I just published a new YouTube video on the three types of Docusign integrations with SalesforceYou will understand the differences between Docusign for Salesforce, Docusign Doc Gen, and Custom Integrations and how each method allows you to create, send, and track documents directly from Salesforce. You can find it here: PS: join me every Wednesday at 9AM PST during a free Q&A session. Click here to register! Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hi DocuSign Community,We are currently integrating the Navigator Agreements List API and had a question regarding Parties filtering support.In the DocuSign UI, we can see a Parties filter that allows selecting multiple parties and applying them together while filtering agreements.However, while reviewing the API documentation, we noticed: The GetAllParties endpoint appears under the CLM API (/v2/{accountId}/parties) The documentation mentions CLM API access is only available for CLM customers with a production account The Agreements List API documentation does not clearly indicate support for filtering by multiple parties We would appreciate clarification on the following: Is a CLM-enabled account required to retrieve Parties data for Navigator agreement filtering? How can we enable or gain access to the Parties API for development/testing purposes? Does the Agreements List API officially support filtering by multiple parties? If supported, what is the correct filter syntax f

 Hi DocuSign Community,We are currently integrating the Navigator Agreements API and had a question regarding agreement status values shown in the DocuSign UI.In the UI, we can see statuses such as: Active Expiring Soon Renewing Soon Inactive Effective Soon However, when calling the Agreements List API (GET /agreements), these status values are not returned in the response, and we also could not find supported filters for them.We would like to understand: How can we retrieve these status values through the API? Is there any recommended approach to implement filtering for these statuses in custom integrations? At the moment, since these statuses are visible in the DocuSign UI but not available in the API response, we are unsure how to accurately display or filter them in our application.

Hi, I'm the founder of a transaction-management SaaSfor residential real estate teams. I'm planning a Docusign integration and need toconfirm go-live eligibility before I invest the build time.The model is a standard ISV Connector / Public integration:- One integration key, Authorization Code Grant (confidential client)- Each user connects THEIR OWN existing Docusign account via OAuth- All envelopes are sent from and billed to the users' own Docusign accounts.  Nothing is billed to my company, and I am not reselling or embedding Docusign.My company is an established LLC with a corporate domain, but it is a smallcompany: fewer than 20 employees and less than one year old. The Partner Programrequirements page lists "established for at least one year and with at least 20employees," which is why I'm asking before building.Three specific questions:1. For a Public integration under the model above, is Docusign Partner Program   membership strictly required to complete Go-Live, or can Go-Live

Overview of my problemI created a standard developer account (on the default "DEVCENTER_DEMO_RESTRICTED_JUNE2025" plan) and I am getting a "RECIPIENT_LIMIT_EXCEEDED" error whenever I try to create an envelope with 2 recipients via the eSignature REST API. I am trying to have two people sign the document - the first signer is me, the second signer is the client which receives an email to sign the document once I have signed the document. Is the restriction I am encountering built into the RESTRICTED plan? How can I increase the per-envelope recipient limit on a sandbox account or change the plan for free, for development testing? I need at least 2 recipients per envelope for a two-signer flow (embedded signer + email signer).Error response{ "errorCode": "RECIPIENT_LIMIT_EXCEEDED", "message": "You have reached the maximum number of recipients permitted for a single transaction in your account." }Querying GET /v2.1/accounts/{id}/settings returns no maximumRecipientsAllowed field. The /bil

We want both the in-person signer and the customer to sign the same document at same time. A single email should be sent containing the document, allowing both parties to complete their signatures on that document on same screen. And in the same document signature of both in-person and customer should appear at same time.Please suggest here.