Developer

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

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

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)

I have created an Integration Key in my DocuSign Demo account and would like to promote it to the Production environment.Could you please let me know the steps involved? Also, while creating the Integration Key, it asks me to select an Integration Type. Which option should I choose?I have attached a screenshot for reference.Are there any prerequisites or approval requirements that must be completed before the Integration Key can be used in the Production environment? Do we need to purchase a DocuSign Production plan or subscription before an Integration Key can be promoted and used in Production?  

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

Hello.When using the "Add documents to an envelope" action, I get the error message “Flow run failed. Action 'Add_documents_to_an_envelope' failed: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.”I get this with both docx and pdf documents. Wrapping the ContentBytes in the base64 function did not resolve the problem. The Inputs and Outputs of the action are attached.Has anyone had the problem and knows how to fix it?Many thanks*** attachment removed due to sensitive information

Hello,I'm going through the Go-Live process for a private custom integration and have a few questions before resubmitting:1. Corporate email requirementThe production Admin account is currently registered with a @gmail address. Is it mandatory that the Admin account itself be registered with a corporate email domain, or is it sufficient that the person filling out the verification form uses a corporate email — even if the DocuSign account is linked to a @gmail address?2. Plan eligibilityIs a specific DocuSign plan required to complete the Go-Live process for a private custom integration using JWT authentication? If so, which plans are supported?3. Signing the formIs it mandatory to complete the identity verification step (document photo + selfie) during the Go-Live form, or can the process be approved without it?

Hi team,My Quote object can have multiple related Orders (child relationship). I only want to show the latest Order's OrderNumber in my Gen template — not all of them.Is this possible, and if yes, how do I set it up?Note: Refer to the screenshot.Thanks!

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

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

Hi DocuSign Community,We are testing the Navigator Agreements List API and wanted to confirm whether combining $search and $filter is currently supported.Request:GET /v1/accounts/{accountId}/agreements?$search=sample&$filter=status eq 'completed'Response:{"title": "Bad Request","status": 400,"detail": "The $search and $filter query parameters cannot be combined in the same request. Use $search for full-text search or $filter for structured filtering."}Observations: $search works correctly when used alone $filter works correctly when used alone Combining both returns 400 Bad Request However, in the DocuSign completed documents experience/UI, searching and filtering together appears to work correctly and returns expected results.We would like to confirm: Is this a current limitation of the Navigator Agreements List API? Is there any supported workaround to achieve combined search + filtering? Is support for combining $search and $filter planned for a future API version? Any c

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 

Subject: Embedded Template Edit View: PUT .../documents/{documentId}/tabs returns 401 AUTHORIZATION_INVALID_TOKEN when UPDATING an existing prefill tab — but POST (add) worksEnvironment: eSignature REST API v2.1, Demo (account-d.docusign.com / demo.docusign.net, editor host apps-d.docusign.com).Use case: We embed the Template Edit View in our web app (in an <iframe>) so users can tag/adjust fields on a template.How we create the edit view (server side)POST /restapi/v2.1/accounts/{accountId}/templates/{templateId}/views/editAuthorization: Bearer <JWT-grant app token, scope: "signature impersonation">{ "returnUrl": "https://<our-return-page>", "viewAccess": "template", "frameAncestors": ["https://<our-app-origin>"], "settings": { "startingScreen": "Tagger" }}The returned url (a .../managed_token/v1/redeem?slt=... link) is set as the <iframe src>. The redeem redirects to apps-d.docusign.com/send/prepare-template/{templateId}/add-fields, and the embedded e

Hi! I just published a new YouTube video to help you choose the right Docusign plan based on your agreement complexity and envelope volume. You’ll learn the difference between manual and automated sends, when different plans may make sense, and why mapping your workflow before buying can help you avoid costly overages and unnecessary implementation problems. Watch the full tutorial here:  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

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 trying to create a connection to DocuSign (not demo) within PowerAutomate. This has previously worked for the account I am using. It stopped working and so I am trying to reconnect.When I create a new connection I get this: I have revoked the previous “Connected Apps” thing so that when I login it asks me to authenticate. Which I do.I have tried from an in-private browser (both Edge and Chrome)I saw another post that suggested it was related to their “web security gateway” so I’ve tried from home on my personal laptop and I get the same.Any assistance on what to try next would be most appreciated

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

I’m trying to request a phone call and it’s not working. I need to talk to support! I will not be renewing if it’s this hard to get support.

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?