Developer

I’m currently integrating with the DocuSign eSignature REST API (v2.1) and facing an issue when creating envelopes using composite templates.What I’m Trying to Do Create an envelope using a server template The server template already contains one or more documents At runtime, upload multiple additional attachment documents (PDFs) Use compositeTemplates (serverTemplates + inlineTemplates) for this purpose IssueWhen the server template contains documents, I’m unable to upload multiple additional attachment files via composite templates. Additional documents are ignored / not added to the envelope If the server template has no documents, multiple attachments work as expected Expected BehaviorAll documents should be included in the envelope: Template documents Multiple runtime attachment documents Actual Behavior Multiple attachments cannot be added when the template already has documents Questions Is this a known limitation of composite templates? Is there a recommended workar

Description:I'm unable to authenticate using JWT Grant with my promoted integration key in production. I receive an issuer_not_found error despite having the integration key properly configured.Configuration:Integration key was created in developer account and promoted to production using DocuSign's go-live process Generated new RSA key pair in production User Application setting: Yes Authentication Method: Authorization Code Grant Redirect URI: http://localhost:8080/callbackError:When attempting JWT authentication, I receive:{"error":"invalid_grant","error_description":"issuer_not_found"}Steps Attempted:Tried granting individual consent via multiple authorization URLs (both account.docusign.com and account-d.docusign.com) All consent URLs fail with "The client id provided is not registered with Docusign" Verified all User ID, Account ID, and Integration Key values match between production account and application configuration Confirmed RSA key pair is properly configured Attempted

Following this instruction : https://support.docusign.com/s/document-item?language=en_US&bundleId=als1679428547895&topicId=kyy1679958874136.html&_LANG=enusI was able to create a word document using DocuSign Add-on , and then uploaded to Docusign as template.In MS Word it looks like this :I created an app in C# that uses DocuSign.eSign.dll 8.0.2 version and cannot set values to those "sender field data".Any idea how to do it ?These is what I tried so far : Tried upgrading the library to 8.6.0 to use : envelopeDefinition.PrefillTabs (failed)using TextCustomField like this (failed) : envelopeDefinition.CustomFields = new CustomFields{ TextCustomFields = new List<TextCustomField> { new TextCustomField { Name = "EventName", // Field name WITHOUT braces Required = "false", Show = "true", Value = "PARTY" } }}; using CompositeTemplates (Failed) :  envelopeDefinition.CompositeTemplates = new List<Co

👋 For teams implementing account maintenance workflows in fintech:Do “simple” account updates still turn into custom logic, edge cases, and manual exception handling?If those requests mean repetitive data entry across fragmented systems, slow compliance checks, or frustrated customers, you’re definitely not alone. Our newest Developer Center use case breaks down how developers can modernize account maintenance with secure, scalable self-service workflows—without sacrificing compliance.Key takeaways: Orchestrate self-service and assisted flows in a single process using Workflow Builder (formerly Maestro) workflows Capture structured, validated data with Web Forms to reduce rework and errors Apply policy-driven IDV, KYC, and AML checks only when needed Integrate cleanly with CRMs, core banking systems, and internal services using extension apps Maintain a centralized, auditable record of every update across systems This use case walks through how tools like Workflow Builder (for

Hello,I first created a developer account with my work’s email, then i realized that i do not have access to the advanced signing methods that i have to test.I have a user in my company’s production environment, but it shares the same logs with my developer account, that is not linked to the company, so when i log in the developer realm using my work email, i do not have access to the advanced features. Is there a way i could associate my developer account with my company ?Thank youMathieu

Hi, I am sending a DocuSign email from Apex and using the Salesforce Email Template to generate the Email Body. I am using Messaging.renderStoredEmailTemplate to get the HTML body, and when I check the result using System.debug the HTML content is correctly generated and present. However, after the email is sent, the email body is completely blank. Relevant Code:Messaging.SingleEmailMessage renderResult = Messaging.renderStoredEmailTemplate( opportunityEmailTemplateId, opportunityId_i, myContact.Id);String opportunityOfferEmailContent = renderResult.getHtmlBody();myEnvelope = myEnvelope.withEmail( opportunityOfferEmailSubject, //Subject opportunityOfferEmailContent //Email Body);myEnvelope = dfsle.EnvelopeService.sendEnvelope( myEnvelope, true);How do I resolve this? Kind RegardsWilly

Hi, I work as an Integration Engineer for Unit4 and we’ve developed an integration between our ERPx platform and Docusign for document e-signing. We are now introducing some changes in the integration and we noticed an apparent difference on the signer consent process. We used to have a ‘consent_required’ error (HTTP response status 400) when requesting an OAuth token for the signer and we used it to identify that a given signer hadn’t yet given their consent. Currently it seems that all the signer consent process is dealt exclusively on Docusign UI. Can you please confirm if Docusign introduced any changes at the signer consent processing level? Thanks in advance

I have submitted and signed the Docusign API Go Live Form that is linked to the ‘Submit verification form’ button. I would like to know if I need to do anything else aside from wait until the manual Go Live review finishes. My dashboard status did not change status which is making me unsure. And how long might the Go Live process take on average? Thanks 

Hello, I have an issue concerning the simplified view, it would seem that it doesn’t support HTML, or just partly ?When sending an envelope via docusign API, i am sending HTML through the “emailBlurb”, that html is well rendered on the email side. But it is not on the docusign simplified preview pageOn the email side: On the simplified welcome view, many spaces generated, images doesnt work. I was wondering if it was possible to disable the simplified view, or to remove the html from this page.  Thank you for your help ! Steven Truong

Core ProblemMy organization has implemented Docusign-Connect to send completed envelope to our Laserfiche storage system. This Works as intended for envelopes with a single template however multi-template envelopes additional templates do not express retrain their Envelope Custom fields metadata correctly when transferred to Laserfiche, and instead assume the Envelope Custom Field data of the initial template.  Current DesignEach Template has 4 key pieces of metadataTemplate Category: This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field.  Template Sub-Category:  This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field. Recipient Account Number: This is currently a Custom Document Field on each template  Completed File name: This is correctly separating into multiple files based on template pdf file name.  Design LimitationsR

We are using Docusign JS library for embedded signing experience. In chrome browser, when we load the url, it is adding iframe in DOM and then opens modal to accept terms.In edge browser, it just hangs and never open the modal to accept terms with exceptions below.   

I am working on converting a bunch of hand written forms to DocuSign.  Our system uses the DocuSign API and connects to it using the C# .NET SDK.This works well for most fields and anchor tags but, recently, we have started adding fields like checkboxes and radio buttons.  However, it appears that radio buttons do not have any sort of measurement associated with them in their class (no scale, no width/height, etc.).  The only size related field I can find is fontsize, but changing that does not appear to change the size of the radio button.Is there any way to change the size of a radio button for a form submitted through the DocuSign API?

Hello,I'm reaching out because my Go Live request was recently declined, and I'm unsure why — no feedback or rejection reason was provided.About Our IntegrationWe're building a B2B SaaS platform (Getmany.com) that requires customers to sign commitment agreements.  The Go Live form was declined by Drew Martin, but I received:- No email explaining the issue- No checklist of what failed- No comments or next steps I'd appreciate any help with:1. Visibility - Is there somewhere I can view the rejection reason?2. Common Issues - What typically causes silent rejections? Or it’s normal?3. Checklist - What should I verify before resubmitting? I did more than 80 tests.4. Escalation - Can someone from DocuSign review my submission?I'm ready to fix whatever is needed - I just need to know what it is.Thank you for any guidance you can offer.Kyrylo Kozak 

Hi, I’ve created a Connect configuration with the following settings:Trigger Events > Envelope Events > Envelope Signed/Completed!-->Include Data:Documents Attachments Document Fields!-->But when the contract signing process is complete, I receive a payload into my webkook with the following structure:!-->​​​​​​​{ event: 'envelope-completed', envelopeId: '68ce2953-4fa5-8d2f-8094-cde7fc130d3b', status: 'completed', documents: [ { documentId: '1', name: 'InvestmentContract_50b40cd2-f529-4584-892d-926b40447143' }, { documentId: 'certificate', name: 'Summary' } ], completedDateTime: '2026-01-13T16:15:14.87Z', createdDateTime: '2026-01-13T16:13:53.8Z'}The PDFBytes is not included in the payload. I need to get the signed PDF and save it in a safe storage for my system. Is my configuration wrong? Are there any other ways of getting the singed PDF? Best regards,José Compadre Junior

I’m trying to use the simple send.sig.request script to send signature requests, but it is not at all clear how to get the access token. The JWT seems like overkill as I don’t need to impersonate everyone, just access as a single user, but I don’t want to deal with popping up web pages and whatnot for consent - it just needs to send the request. The instructions say to setup a redirect uri, but it’s not at all clear what the uri is supposed to do when whatever redirects to it…Thanks for any help...

Hi DocuSign Community,I recently submitted a Go Live request for a DocuSign API integration, and it was declined, but I did not receive any explanation, comments, or guidance on what needs to be fixed or updated.This has left me a bit stuck, so I’m hoping someone here (or a moderator) can point me in the right direction.Integration Details Authentication: JWT Signing method: Embedded Signing (Recipient View) Webhooks: DocuSign Connect for envelope completion Status: Fully working and tested in Demo Use case: Users sign a required agreement before account activation What I’m Confused About I never received: An email A checklist Or any rejection reason explaining why the Go Live form was declined I’m not sure whether the issue is related to: Redirect URLs Branding / consent screens JWT configuration Webhook configuration Or something else entirely My Questions Is there a way to see the rejection reason for a Go Live submission? Are there

Hello,We are using IAL2 compliance identity verification and want to customize email body when sending documents to customers. I am sending my template in emailblurb property within envelope definition. But somehow it is overrriding and sending me some default email. Can you please help me here? Do we have any restrictions on email body if we are using IAL2 IDV ? Thanks!

Hello,I’m using a DocuSign template that is sent via the API and pre-filled with dynamic values (for example: full_name, date_from, date_to, price, etc.).The values are populated correctly using Text tabs (via tabLabel), however I’m running into a layout issue:The text fields have large visible gaps, because the text tab has a fixed width. Since the data is dynamic (names, dates, values can be longer or shorter), I can’t reliably determine how wide the field should be ahead of time.My questions are: Is there any way for a DocuSign text field to automatically resize (shrink/grow horizontally) based on the value that is injected? If not, is there a recommended best practice for handling dynamic inline values in legal documents without creating large spacing gaps? Are anchor-based tabs, replace text, or any other technique supported that avoids fixed-width spacing issues? The goal is to keep the document visually clean and professional regardless of the length of the injected value.Th

Hi everyone,I’m running into an issue where I cannot retrieve the actual comment data from an envelope using the primary Get Envelope endpoint, even when including all relevant parameters.The Goal: I want to retrieve the contents of commentThreadTabs (specifically the comments array) in a single request to avoid making multiple calls per envelope.The Problem: When calling GET /v2.1/accounts/{accountId}/envelopes/{envelopeId} with the following query parameters: ?include=workflow,documents,custom_fields,recipients,tabs,prefill_tabsThe response returns the commentThreadTabs object, but the comments array inside it is always empty.Observations: If I use the specific GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}/tabs endpoint, the comments are populated correctly. However, the documentation for the main Get Envelope endpoint implies that include=tabs should return the full tab schema, which includes the comment threads. Questions: Is it by design that the c

Long story short, I had an embedded E-Signature set up and working without issue last month. Now it only works on my staging server and not on my local. Locally I’m receiving the screenshotted error in my console along with many more. I’ve been trying to work through it with google and other posts be am getting no where and falling behind on my development schedule. Any assistance would be greatly appreciated.Thanks,Andrew

I'm getting USER_AUTHENTICATION_FAILED errors when creating envelopes via the API in production, even though JWT token generation and get_user_info() succeed.Setup:Production account: eSignature Business Pro Authentication: JWT (Service Integration with RSA keypair) Integration Key SDK: docusign-esign PythonWhat Works:JWT token generation succeedsget_user_info() returns account detailsAdmin consent grantedWhat Fails:EnvelopesApi.create_envelope() returns: Error: (400) Bad Request errorCode: USER_AUTHENTICATION_FAILED message: "One or both of Username and Password are invalid." Trace-Token:Code flow:Get JWT token via request_jwt_user_token() Call get_user_info() to get account_id and base_uri Set base_path to account.base_uri + '/restapi' Set Authorization header with Bearer token Call create_envelope() with account_id → fails with USER_AUTHENTICATION_FAILED Question: Is there a production account permission or configuration needed beyond what's shown in the Apps and Keys settings?

RecipientViewRequest viewRequest = new RecipientViewRequest();viewRequest.setReturnUrl(redirectUri); My redirectUri is 'http://localhost:8089/callback'and after user do sign and click finish in loaded iframe - below call fails'http://localhost:8089/callback?event=signing_complete'with error 'The connection is blocked because it was initiated by a public page to connect to devices or servers on your local network.' What this error means and how to resolve this issue. Please help

Hoping someone can help,My company has been using eSignature API in our application for a couple of years. As part of our DocuSign implementation we periodically check for envelopes that have been updated using a request with the following format:GET https://na4.docusign.net/restapi/v2.1/accounts/[accountid]/envelopes/status?from_date=2025-09-06T23:25:57Z&from_to_status=changedGenerally this works fine, but we’re getting 408 - Request timed out - responses in some cases and I can’t see any obvious reason why. Any ideas?Some other things to note:This may be related to the fact that this is uses the na4 data centre. Similar requests made to ca or eu work without any issues (in the eu region myself) According to our logs, it’s generally only a few seconds between the call being made and the response being returned We use the JSON Web Token grant methodKind regards,Poppy

We are currently using DocuSign API integration, where the recipient security setting is configured as None at the envelope level. However, this configuration is being overridden by the account-level authentication settings.While attempting to disable the account-level recipient authentication, we observed that the Save button is disabled, preventing any changes from being applied. 

Hi, I have a weird behaviour I do not understand. I’m using the envlope-API to create an envelope based on a template (/restapi/v2.1/accounts/{{accountId}}/envelopes). My destination is the development tenant. For this API Call I use the following request body { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email": "Some.Name@test.com", "name": "Some Name", "roleName": "signer", "tabs": { "companyTabs": [ { "value": "test Company 1", "tabLabel": "atb.docusignFields.label-company <id>", "locked": "true" }, { "value": "test Company 2", "tabLabel": "atb.docusignFields.label-company <id>", "locked": "true" } ] } } ], "status": "