eSignature API

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. 

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.

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 

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.

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.

Hi Team,We need to send an envelop to an in person Signer using template Id. But as per DocuSign documentation the sample payload does not have field for template Id.How to send an envelope to an in person signer | Docusign

Hi team,I'm building a JWT Grant integration on my demo/developer account and I'm hittingRECIPIENT_LIMIT_EXCEEDED as soon as I create an envelope with more than 1–2 recipients.My real flow needs 3 recipients per envelope (signer → approver → carbon-copy), and itfails at the create-envelope call.Account details:- Account name: **Information removed**- Account ID: **Information removed**- Plan: DEVCENTER_DEMO_RESTRICTED_JUNE2025- Environment: Demo (account-d.docusign.com / demo.docusign.net)- Auth: JWT Grant (Authorization Code consent already granted)Evidence it's the plan's cumulative recipient cap and not my payload:- Single-recipient envelopes send successfully.- A 3-recipient envelope returns HTTP 400 RECIPIENT_LIMIT_EXCEEDED.- billingPeriodEnvelopesSent: 0, billingPeriodEnvelopesAllowed: unlimited,  envelopeSendingBlocked: false, suspensionStatus: (none).Could you please remove or raise the recipient limitation on this demo account so I cantest multi-recipient signing flows? Happy

Looking into the possibility/ability of voiding envelopes without an email notification going out to the recipients. Poking around maybe it’s doable via the “notifyuser” tag? Any tips and sample requests would be greatly appreciated

I'm building an embedded signing flow (JWT auth, envelopes created via the eSignature REST API). One of my documents is the IRS Form W-9. The SSN area is a "comb" field — nine small printed boxes (3 + 2 + 4, with a printed hyphen between each group).My goal: let the signer type their full 9-digit SSN into a single field, and have each digit appear centered in its own printed box on the final signed document.Important constraint: for privacy, the SSN must be typed by the signer inside DocuSign — I cannot collect it on my server and pre-fill the tab value.What I've already tried:A single Text tab over the SSN row → the number renders in one spot and doesn't line up with the printed boxes. The native SSN tab → same single-position rendering, and its dashes overlap the form's own printed dashes. Three Text tabs (one per group, 3/2/4) and nine single-character Text tabs, in Courier at a size where each glyph is one cell wide → these do align each digit to its cell, but the signer has to typ

Overview For those familiar with Docusign’s API Rules and Limits, you’re probably already aware of some of the error messages that Docusign returns when using our various APIs. These typically exist in the form of response headers, HTTP response status codes, or specific error messages contextually related to your current activities. If, for example, you had previously run into hourly limits, you may already be aware of Ratelimit-Remaining or Hourly / Burst limits, among others. Recently, we have redesigned several commonly encountered API error messages to be more intuitive and customer-friendly. Historically, many of these messages were overly technical, ambiguous, or lacked clear next steps, often leading to confusion, increased support tickets, and slower issue resolution. In addition to message improvements, we have updated select HTTP status codes to better align with standard API conventions:Changed from 429 → 400 for cumulative recipient limit errors (RECIPIENT_LIMIT_EXCEEDED)

Hi everyone,I’m creating and sending envelopes from an Azure Function using the DocuSign eSignature REST API on the demo environment. The envelope is created successfully and looks correct in DocuSign, but recipients never get the signing email.What happensMy API creates a draft envelope, adds a document, adds 2 signers, adds tabs, then updates the envelope status to sent. DocuSign returns an envelope ID with no error. In DocuSign Manage: Envelope status is Sent Both recipients show Needs to Sign Both show Sent on the same time Signing order is 1 for both (they should get the email at the same time) Email addresses on the recipients are correct Neither recipient receives the DocuSign email. If I click Resend in DocuSign, still no email is received.So from the UI it looks like the envelope was sent, but no notification email is actually delivered.  SetupEnvironment: DocuSign demo (account-d.docusign.com / demo.docusign.net) Auth: JWT (signature + impersonation) 2 signers, both remo

Can both Customer & Salesperson sign the same document, but the email will be received by only Salesperson. 

I'm using the DocuSign REST API with C# (.NET) and have the following business requirement.ScenarioA single envelope is sent to 5 signers simultaneously (no routing order). After 48 hours: 3 signers have completed signing. 2 signers have not signed yet (their status is Sent or Delivered). RequirementInstead of voiding the envelope, I would like to:Remove the 2 pending (unsigned) recipients. Keep the 3 completed signatures. Allow the envelope to transition to Completed. Download a valid completed document without a VOID watermark.QuestionsIs there any supported REST API endpoint that allows removing or excluding pending recipients and then completing the envelope? Can the Update Recipients API (or any other API) be used to convert pending signers to another recipient type (for example, Carbon Copy) so that the envelope can complete? If this scenario is not supported by the DocuSign REST API, what is the recommended approach to implement this business requirement?Any guidance or recomme

I'm configuring reminder notifications using the DocuSign eSignature API. I know it's possible to configure the reminder delay and reminder frequency in days.However, my requirement is to have reminder emails sent at a specific time of day (for example, every reminder should be sent around 2:00 PM).Is there any way to specify the hour or time of day for reminder emails through the DocuSign API, or are reminders only configurable using day-based intervals?If this isn't supported, are there any recommended workarounds to achieve reminders at a fixed time each day?Thanks in advance!

I am using the POST /restapi/v2.1/accounts/{accountId}/envelopes endpoint with multipart/form-data to create envelopes.The request payload is shown below:--AAAContent-Type: application/jsonContent-Disposition: form-data{ "documents": [ { "documentId": "1", "fileExtension": "txt", "name": "test1.txt", "order": "1" } ], "emailBlurb": "this is a test", "emailSubject": "test", "eventNotification": { "envelopeEvents": [ { "envelopeEventStatusCode": "Completed" }, { "envelopeEventStatusCode": "Declined" }, { "envelopeEventStatusCode": "Voided" } ], "requireAcknowledgment": "true", "signMessageWithX509Cert": "true", "url": "dummyurl", "useSoapInterface": "false" }, "notification": { "useAccountDefaults": "true" }, "recipients": { "recipientCount

Hello Everyone,When we create the envelope by default expiry be after 120 days. We tried to extend expiry of an envelope by adding number days to the expireAfter method but it still not updating, let me know the process to add new expiry day to the envelope. May I know that we can extend the expiration of an envelope by using developer account or not else we need any subscription to extend the expiration of an envelope.And also, please let me know I need to configure any setting in the developer account from my end.Thanks and RegardsCharan Balam

Hello,>Working with the C# SDK<Using composite templates, i successfully created an envelope with 4 documents and 4 recipients (yay !)Document #2 is defined as display=”inline” and i added some tabs (SignHere, Text, DateSigned...) for recipient #1 and recipient #4 : works like a charm. Now my problem is with document #1, which is a supplemental document (display=”modal”). The goal is to set this document as “View and accept” only for recipient #4. Following the documentation I created a View tab and an Approve tab like this :Approve approveTab = new Approve() { DocumentId = "1", RecipientId = "4" };View viewTab = new View() { DocumentId = "1", RecipientId = "4", RequiredRead = "false", Required = "true", PageNumber = "1" };and added them with the others tabs on the recipient #4 (NB : others tabs work fine!) Problem is the supplemental document stays in “optionnal” and no action is required on it. What am I missing ? Regards 

Goodmorning,  I am wondering if there are any API endpoints I can configure to that would allow me to fill in fields on a templated document. For context, I’m working on configuring a solution for a business that takes information from a form and automatically drafts an agreement in a Docusign template. Right now I’m using the Docusign MCP server within Claude and I don’t think there is capabilities to do this since i can’t see any of my fields being populated. I made sure that the fields are not locked and are set for visibility on the template.  Is anyone doing something similar?

Hi, I’m using the DocuSign .NET SDK CreateEnvelope API to send envelopes with multiple documents, recipients, and tabs.am noticing a delay between making the API call and receiving the EnvelopeSummary response, and I would like to understand if this is expected behavior.What is the typical/expected response time for envelope creation? Are there recommended best practices to improve performance and reduce API response time?

Hi community,I have a Power Automate flow that creates and sends a DocuSign envelope. The flow was working previously but is now failing on the Login action with a 404 - Resource not found error.Questions:Has anyone seen a 404 on the Login action specifically? Could this be related to a DocuSign API endpoint change or deprecation? Is the Login action URL environment-sensitive and could it be hitting the wrong endpoint?Error details:json{ "statusCode": 404, "message": "Resource not found"}