Developer

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

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.  

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.

When I call a get request to listInstances,I receive 11 instances for my webform.But when I go to data report for my webform, there are actually 21 instances, but I am not getting all of them via API.Anyone encountered this issue? Is there something I am missing? 

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,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!

I am creating webforms, and the process is fine, even though there seem to be some field limitations.  I would like to add some formatting using Markdown language, but none of the tags work.  This seems like HTML and I am familiar with using that.  I add the tags, when then I view or publish the forms, I just see the tags as if they were regular text.  Suggestions? 

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

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 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?  

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

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?

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