Developer

I am encountering the following error when attempting to send a document using a static variable in my integration with DocuSign:The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying documents for Envelope ID = 95d29fa2-762b-49c6-a162-44ce4d16cd23Context:I am using a static variable to pass the document to the envelope. The envelope creation process seems to fail because it does not recognize the document as attached. Recipients and subject line are already set, but the error persists.Question:How can I ensure that the document is properly included in the envelope when using a static variable? Are there any specific steps or API parameters required to validate the envelope before sending?Any guidance or best practices would be greatly appreciated.

Hello, I’m using the DocuSign eSignature API to create an envelope draft from a template that uses DocGen and contains a dynamic table. After creating the draft and adding rows to the table programmatically, I attempt to add signature tabs anchored to text placeholders inside the table.The sequence of operations is:Create a draft envelope from a DocuSign template using the Envelopes API (POST /v2.1/accounts/{accountId}/envelopes). Add dynamic table rows via DocGen Form Fields API (PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId}/docGenFormFields). Wait for DocGen rendering to complete. Add signature tabs via Create Recipient Tabs (POST /v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/tabs) using SignHere tabs with AnchorString values matching the placeholders inside the table.The envelope and recipients are created correctly, and the table rows appear as expected. However, the signature tabs are never added, List Tabs (GET /tabs) shows SignHereTabs = 0, a

Hello there,I got stuck when I am trying to integrate docusign-esign node module in my spfx webpart.I’ve created a new spfx webpart I’ve installed docusign-esign module in the working directory. (My webpart package.json has the following entry…   "docusign-esign": "^8.5.0Error When I gulp serve - I am getting the following , one of so many.: 'dist':./node_modules/docusign-esign/src/index.js: Module not found: Error: Can't resolve 'ApiClient' in 'C:\Phani\Custom Development\PembinaApprovalsDashboard\PembinaApprovalsDashboard\node_modules\docusign-esign\src'Did you mean './ApiClient'? On init of my webpart, I’ve the following code.try      {        let dsApiClient = new docusign.ApiClient();        dsApiClient.setOAuthBasePath(this.DOCUSIGN_OAUTH_BASE_PATH);        // Use Buffer.from for DocuSign API compatibility        const privateKeyBuffer = Buffer.from(DOCUSIGN_RSA_PRIVATE_KEY, 'utf8');        const results = await dsApiClient.requestJWTUserToken(          this.DOCUSIGN_INTEGRATION_

Hi everyone,We’re experiencing an issue with the embedded signing flow that recently started occurring (it was working fine until last week).We’re following the official guide for creating a focused signing view:👉 https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/Our backend uses docusign-esign@^8.5.0 to generate the signing URL.We include the following domains in our FRAME_ANCESTORS directive:https://our-domain.com https://demo.docusign.net https://apps-d.docusign.com The generated signing URL opens correctly in a separate browser tab.However, when embedding it inside an <iframe>, the frame fails to load and the browser shows a CSP violation error:Content Security Policy of your site blocks some resources Some resources are blocked because their origin is not listed in your site's CSP. ... Resource Status Directive Source location https://apps.dev.docusign.net/.../1ds-bundle.js.map blocked connect-src (unknown) https://apps-d.docusign.com

Hi I am a new user to Docusign and have sent one document out for signature. A client has signed a contract but the wrong company name is shown in the signature box. I do not think this was a requirement specified when requesting signatures, how do I correct this?

Is it possible to have the API call limit raised from the default of 3000 per hour ?   Is this based on the plan you have wit Docusign ? Can it be raised for a certain number of hours per day  ? Ex: 5pm to 8pm an then it goes back to defaultWhat is the maximum if it is possible for it to be raised ? Are there other stipulations for raising it ?Do the API limits only impact Docusign Retrieve or all aspects of sending envelopes  etc. ?What is the procedure to have it increased ?   support ticket ?  Thank YouNorman

Hi DocuSign Community,I need some guidance on the correct architectural pattern for checking envelope status without violating API rules. Context: I’m a developer using the docusign eSignature product. I have an envelope that requires signatures from two separate recipients. I need to trigger a specific operation in my application, but after both recipients have successfully signed and the envelope is complete, and when only either one of the recipient has signed the contract.  Problem: My initial thought was to call the GET /envelopes/{envelopeId} endpoint to check the recipients' status every time one of them signs. However, these two signatures could easily happen within minutes of each other. This would mean I'd be making multiple GET calls to the same envelope ID in less than the 15-minute window, which I believe violates the API polling rules. My application is already live, and I want to ensure I remain compliant. I have also read this, where there isn’t a specific guideline or

Request Failed: 400 {"error":{"message":"Model is not supported for this request.","code":"model_not_supported","param":"model","type":"invalid_request_error"}}

The big news at Docusign Discover25 was the integration of AI-enabled tools with our Intelligent Agreement Management (IAM) platform. Our Model Context Protocol (MCP) server, now in beta, supports AI-assisted tools including Anthropic Claude, Microsoft Copilot Studio, and GitHub Copilot.We also made an exciting announcement about upcoming IAM availability in ChatGPT, which will enable users and AI agents to create and analyze contracts directly in ChatGPT. Other highlights of the November newsletter:Accelerate development with our open-source micro-frontend system, Docusign 1FE. Read about how our partner NeuraFlash leveraged our extension apps feature to create a flexible, powerful app. Find out how ISVs can efficiently add accounts by cloning via the Docusign Admin API. Automate workflow management using the Maestro API. Centralize webhook event notification management with organization-level Connect. Read our recap of Dreamforce25, where we coded and mingled with Salesforce develope

Hi All,I know you can embed in-person signing on a document,But is it possible to embed in-person signing on a website (specifically a sharepoint site).We have site created where users have to provide in person consent, they will be in an office, office users will add the signers name and email address(and a second signer if required) and we expect the signers to sign in person.Is this possible?Thanks in advance.

Hi everyone,I’m trying to send an envelope using the DocuSign eSignature REST API from an n8n automation workflow, but I’m getting a 400 - UNPROCESSABLE_ENTITY error when using a template.Here’s the full request body I’m sending:{  "emailSubject": "Please sign this document",  "templateId": "b19401de-25af-426b-addc-c290c0ef0753",  "templateRoles": [    {      "email": "abc@gmail.com",      "name": “Group",      "roleName": "BCBA"    }  ],  "status": "sent",  "eventNotification": {    "url": "",    "loggingEnabled": true,    "requireAcknowledgment": true,    "envelopeEvents": [      {        "envelopeEventStatusCode": "Completed",        "includeDocuments": true      }    ]  }} And here’s the error response:400 - {"errorCode":"UNPROCESSABLE_ENTITY","message":"The entity could not be processed."}Request details: Endpoint: https://demo.docusign.net/restapi/v2.1/accounts/a66ffa71-c12f-4cab-b5ae-854d3c378e3f/envelopes Auth type: OAuth2 (Authorization Code grant) Integration tool: n8n

I am having no issues with the development environment; however, in production when I call the apiClient.requestJWTUserToken I’m getting back an error message.  “java.net.UnknownHostException: https”CODE    OAuthToken getToken(String apiClientUrl, String oAuthPath,             String clientId, String userId,             ArrayList<String> scopes, String keyValue) throws IllegalArgumentException, ApiException, IOException {        ApiClient apiClient =this.getApiClient(apiClientUrl, oAuthPath);        return apiClient.requestJWTUserToken(clientId, userId, scopes, keyValue.getBytes(), 3600);    }In dev the apiClient is using apiClientUrl = https://demo.docusign.net/restapithe oAuthPath value is https://account-d.docusign.com In production the apiClient is using apiClientUrl=https://www.docusign.net/restapi/v2.1the oAuthPath value is https://account.docusign.comI have verified the clientid, userid, scopes, and rsaPrivateKey values are correct.I am able to ping account.docusign.com an

We are creating 100 pages of forms and calling Docusign API to create an envelope for user to e-sign from our application. User have already reviewed the document in preview state before proceeding with E-sign. Is there option to E-sign all 100 pages in one click rather than user clicking each signature element in each form?  We want to improve the user experience for the client. Thanks.

I am have a usecase where my template is going to be signed by multiple clients. in those templates, I am prefilling different kinds of information (texts, checkboxes, radio buttons and so on). I have a usecase where I need to upload/prefill a logo. this logo will be different in many cases. and I am trying to figure out a way to generate a document with the corresponding logo. is there a way to do this ?

I’m using the SDK C# and when sending a request Envelopes::GetDocument (link) to get the documents, this fails with error:"errorCode":"COMBINEDDOWNLOAD_UNABLETOGENERATEPDF","message":"Unable to generate combined PDF. Please download the documents as an archive." Odd thing is that we are not requesting combined documents. Asking for combined documents would need the specific keyword “combined”, but we don’t have it or use it. Could the error code be related to something else than combined documents? I have not found any information about this error code.

We’re excited to announce the Docusign for Developers 2025 Q4 release! This release is full of exciting new features and tools to help you design smarter agreement processes and capture powerful agreement insights with AI.We’ll be bringing Docusign’s contract expertise directly into Open AI and ChatGPT We’re excited to share that as of today (announced at Discover!), Docusign’s Intelligent Agreement Management (IAM) platform is available in developer tools like Claude, GitHub Copilot, and Copilot Studio, and will soon be available in consumer and business tools like ChatGPT using the Model Context Protocol (MCP) server in beta.This release introduces new developer tools, IAM APIs and extensions, and cutting-edge agreement AI that helps you streamline your agreements, unlock insights, and provide smoother experiences.Learn more on the blog!Build faster with smarter toolsConnect developer tools like Anthropic Claude and Microsoft GitHub Copilot, and business and consumer tools like ChatG

Hello, We’ve noticed that when multiple emails are sent from DocuSign with the same subject line, Gmail automatically groups them into a single conversation thread. This makes it difficult for our recipients to easily identify or track individual signing requests.Could you please let me know if there’s a way to prevent this behavior by adding unique identifiers so that each message is treated as a separate email in Gmail? The envelopes are created via the API from a PHP application, and I’m using the Email Signing Resource file to define the email subject template.  

I need to build one envelope with three composites: a plain PDF with no signers, a server template with roles mapped to recipients, a flat PDF that overrides a server template’s original doc and maps template roles RoleA → Employee (routing 1) and RoleB → Owner (routing 2). ProblemIn composite #3, the tabs/fields from the server template appear on the wrong document (seem to land on the first doc), and the template for the flat PDF looks “ignored.What am I missing or doing wrong that it showing 3 documents as required but adding only last assigned template’s tab and text to complete envelope [i.e. overlaying on first document only ] and ignoring 2nd server template tabs and fields and not adding 3rd template it’s respective 3rd document ???{ "emailSubject": "Combined Envelope Example", "status": "sent", "compositeTemplates": [ { "compositeTemplateId": "1", "document": { "documentId": "1", "name": "Notice.pdf", "fileExtension": "pdf", "doc

Hello,Could you please explain why email subject > 100 caracters are allowed trhougt Docusin_EmailResource customization but not with method RecipientEmailNotification ? 

Here are some of the latest popular questions that developers asked in the Docusign Community and on Stack Overflow for the month of October 2025.Thread: Salesforce Apex Toolkit cannot override Email subject from Docusign Envelope templatehttps://community.docusign.com/salesforce-apex-toolkit-72/salesforce-apex-toolkit-cannot-override-email-subject-from-docusign-envelope-template-25573Summary: The developer is sending an envelope via email from within Salesforce using the Apex Toolkit. They are trying to specify the subject of the email through their Apex code with the Envelope.withEmail method, but when they test this, their code is not overriding the default email subject.Answer: Although the developer has defined their code correctly, the email subject is not being updated because they are using a template that has recipient email notifications defined on it. The developer needs to update the template definition in eSignature for Salesforce, making sure that the box for Custom email

Hi there,I’m getting the following error when requesting an access token from the authorization code previously generated by Docusign:{ "error": "invalid_grant"}I’ve followed all steps in https://developers.docusign.com/platform/auth/public-authcode-get-token/. I can easily get an authorization code, but when using it to request an access token I get above error. This is the request I do:POST in https://account-d.docusign.com/oauth/token with:code=<code returned as query param in the redirect_uri>grant_type=authorization_codeclient_id=<my integration key in development environment>code_verifier=<my original random string used to calculate the code challenge>I’ve made sure that the code was generated less than 2 minutes before asking for the access token.What am I missing?

Hello,I'm developing an application using the eSignature REST API (via the Node.js SDK) and facing an issue with embedded signing. The `signing_complete` event is not being sent from the DocuSign iFrame to my parent application via `postMessage`.Here is my current setup and what I've tried so far:**Workflow:**1.  **Server-Side (Node.js/SvelteKit):**    *   I create an envelope successfully.    *   I call `envelopesApi.createRecipientView()` to generate a `recipientViewUrl` for an embedded signer.    *   Crucially, I am including `frameAncestors` and `messageOrigins` in the `recipientViewRequest` pointing to my local development origin (`http://localhost:5173`).    ```javascript    // Simplified server-side code    const viewRequest = {        returnUrl: `https://example.com/docusign/return`, // A simple fallback page        authenticationMethod: 'none',        email: user.email,        userName: user.name,        clientUserId: user.id,        // @ts-ignore - Types are missing, but API

Hello,We set up a DocuSign app on our client’s dev account, passed the Go-Live check, and published to production. As the next step, a production user opened the consent link and approved it. We can see the app listed under the user’s Connected Apps.However, our OAuth token request to https://account.docusign.com/oauth/token still returns:{"error":"consent_required"}Note: We also have another production account where this flow works as expected—authentication succeeds—so the issue appears to be specific to this production account. I’m out of ideas on what else to verify and would appreciate any tips or guidance. Thank you.

Thanks to everyone who stopped by the Docusign Developer Lab at Dreamforce! It was great meeting so many of you—developers, admins, and builders—who jumped in to explore building Maestro workflows and using the Maestro API.  We heard from many of you that some of your biggest agreement challenges come from manually processing agreements, which ultimately slows down deals. Docusign Intelligent Agreement Management (IAM) for Sales was introduced to address these challenges, and was recognized ahead of Dreamforce with the Salesforce Partner Innovation Award in the High Technology category.In the Docusign Developer Lab, developers got to experiment with IAM for Sales and learned how building workflows can automate those repetitive steps, especially with the Salesforce extension app.  If you missed the lab or want to keep building, you can grab everything from our GitHub repo. And if you’re heading to Docusign Discover next week, you’ll have another chance to get hands-on with IAM for Sales

Hello,We setup a Docusign app on dev and followed all the steps mentioned in granting administrative consent for JWT Grant Flow. When we migrated our app to Prod, firstly, we don’t see the Organizations Tab that we see on Docusign dev and I get this error when I am trying to get an access token from Docusign.error 400 while reaching https://account.docusign.com/oauth/token: {"error":"consent_required"}I am not sure how to move forward from here because our setup works on Docusign Dev but doesn’t work after going live.