Developer

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

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?

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

Hi Team, Today we found docusign iframe was not loaded, it even worked yesterday, no changes applied in our side.When I opened the signing URL  in the browser, which starts with “https://demo.docusign.net/signing/mtredeem/v1”.I cannot find our domain in “content-security-policy” response header, and confirm our domain has been added into the FrameAncestors whie calling CreateRecipientView API. Is their any update for demo site? Thanks,Fei

Hi DocuSign Community!I'm experiencing an issue with displaying base64-encoded images in HTML templates used for embedded signing via the eSignature API.I'm using HTML templates with <img> tags that contain base64-encoded images in the src attribute (using data: URLs). The images display perfectly when viewing the HTML in a standard web browser, but they disappear when the document is embedded using the DocuSignJS SDK for signing.Technical Details:API Used: DocuSign eSignature API with embedded signingSDK: DocuSignJS SDK (https://js.docusign.com/bundle.js)Image Format: Base64-encoded images using data:image/[format];base64,[data] syntaxImplementation: HTML templates with embedded <img> tags Are there any known limitations or specific requirements for displaying base64-encoded images in HTML templates when using embedded signing? Is there an alternative approach I should consider for including images in signable HTML documents?Documentations references:Envelope creationEmbed

I have a strange misalignment of signer records when I am setting up one signer as a host and another signer as an inPersonSigner using API.  The result of a setup is the signerName is used along side of a host email when it is showing “Hosted By” and also in one of the flow dialogs when it is saying that “Name1, pass control of the session to Name1”, where Name1 is the inPersonSigner signerName. I am submitting clientUserId for both host and inperson signer, otherwise I could not match the inPerson signer while generating a RecipientView. I see that it aligns the names correctly if I remove clientUserId from inPersonSigner record, but it breaks the mapping for RecipientView. Is there any possible work around for this?

Hello everyone,I’ve got some questions regarding the export of events, generated by employees to a company’s SIEM. As a security team’s representative, I’m interested in enhancing the monitoring and security of this system in my company, so I want to know if it’s possible to export this events to SIEM systemOur company has eSignature Business Pro Edition Plan and I have read the DocuSign has a Docusign Monitor, which can detect potential threats and it also has a pre-built alerts and SIEM integration capabilities, but unfortunately our plan doesn’t have this DocuSign Monitor. Are there any other ways to export the event logs to our SIEM system? Thanks everyone in advance.

We have been successfully using the API end-point since around March 2024 with a custom built plugin in WordPress Gravity Forms on our USA server. The custom plugin uses the composer package docusign/esign-client ^6.10 behind the scenes. In mid august we migrated our setup to new server in the EU. Since migrating to a fully patched ubuntu 24.04 server (no java or log4j), using a LAMP stack, all of our API calls get HTTP 444 with the vague error message “The custom error module does not recognize this error.”If we run “curl -v  https://na4.docusign.net/restapi”  on the cli from the new server we receive this response: < HTTP/1.1 444 < Content-Type: text/html< Vary: Origin< X-Content-Type-Options: nosniff< X-DocuSign-TraceToken: c247ca85-1505-4838-9d76-693daec3245d< X-DocuSign-Node: SE101FE106< Date: Wed, 08 Oct 2025 17:14:15 GMT< Content-Length: 54< Strict-Transport-Security: max-age=31536000; includeSubDomains< * Connection #0 to host na4.docusign.net left

​Hello,​I am trying to achieve a specific email notification workflow with the eSignature REST API, but I'm running into an issue.​My Goal:​I have an envelope with one embedded signer (clientUserId) and several CC recipients (carbonCopies). My desiredworkflow is:​The CC recipients should receive NO email when the envelope is sent.​After the embedded signer completes the signing, both the embedded signer and all CC recipients should receive the final "Completed" notification email.​What I've Tried:​I have tried two approaches, but both have failed:​Attempt 1: Using routingOrderI set routingOrder: 1 for the signer and routingOrder: 2 for the carbonCopies.​Result: The CC recipients still receive an email immediately when the envelope is sent. This email contains a "live view" link to the in-process document.​Attempt 2: Using suppressEmailsI kept routingOrder: 2 for the CCs and added "suppressEmails": "true".​Result: This successfully stops the initial email to the CCs. However, it also st