Developer

I have Docusign integrated with Salesforce. Currently, I have a DocuGen Template created and I can click a Salesforce button to generate a document from an Opportunity, complete with various merge fields. I have a use case where I’d like to help automate workflows by having a Salesforce Flow (with Invocable Apex assistance, if necessary) take a given Opportunity, generate the ContentDocument, and then attach the ContentVersion as an email along with a Salesforce Email template and send it to a Contact. I can see how to generate a Docusign Envelope through Apex (really great documentation btw), but I don’t want an entire envelope. I just want to generate the doc itself, and send that raw doc attached to a templated email to the designated Contact for review. I cannot find any documentation about how to use the DocuGen features to use the Template and merge fields to generate the doc so that I can use it as an attachment. Any help is appreciated. Thanks!

In my Salesforce org, I’ve installed the eSignature app. I’ve successfully configured and activated the app user, and I’ve also created an envelope. Now, I want to send a PDF file as an attachment to the client using that envelope. This should be done automatically through Apex, triggered after a specific action. The email should include the DocuSign envelope and attach related documents from the record. What I need to know is: how can I use Apex to send an email to the customer, using the existing envelope and attaching the related existing documents?Note:Is this possible to implement? Can it be done using only Apex, or with Flow, or both?

Hi, if anyone could help with this, that would be awesome. I’m facing the following issue: I create an instance of the webform in the backend, then send the form URL and instance token to the frontend. If I clear the browser data and try to render the form using the form URL and instance token, it works. If I refresh the page without creating a new webform instance and try to re-render using the same URL and token, it also works. The problem starts when I create a new webform instance — for example, when the user changes some data — and then try to re-render it. In this case, the form tries to load, but it shows a “Something went wrong” message. When checking the network tab, the returned error is: “Session invalid.”it is only going to render again if i clear browser data. Has anyone faced this before?Do you have any idea what might be causing this or how I could fix it?  

What’s the difference between embedded signing and embedded sending?

Hi DocuSign Team,I'm trying to create a developer account, but the sign-up process doesn’t complete and no error message is shown.Steps I’ve already tried: Used different devices and browsers Switched to different networks Cleared browser cache and cookies Despite these attempts, I’m still unable to proceed. Could you please assist me with this issue? Thank you, 

HiI'm using the PHP SDK for esigning, working all great, we have all kinda of different dynamic fields, checkboxes, radio fields, text fields, etc. working great, but now the client has asked us for the following:Whenever the client has signed the PDF and the signed the PDF is returned either by mail or the webhook, the PDF only contains the filled in values, so the checked checkboxes, selected radio boxes for example, leaving a white gap where the user made no choice. Is it possible to make DocuSign render all elements?How the signed pdf is now (user selected no):How we would like to have it:  

I’m programmatically adding CheckboxGroup and RadioGroup fields to a 2-page PDF using the DocuSign REST API (SDK version 5.5.0). During signing, the signer can interact with the checkboxes and radio buttons without any issues.✅ During signing: Checkboxes can be selected Radio buttons can be chosen ❌ Issue after signing: In the final completed PDF, the selected fields show an "X" mark instead of the expected checkmark (✔) for checkboxes or filled circles for radio buttons. 🔧 Details: Using DocuSign eSignature API SDK Version: 5.5.0 Fields are added via CheckboxGroup and RadioGroup Environment: Developer Sandbox (demo.docusign.net)   ❓My question:How can I ensure that the final, signed PDF displays: ✔ checkmarks for selected checkboxes, and ● filled circles for selected radio buttons?

Hello,I’m trying to create a DocuSign developer sandbox account, but I'm unable to complete the process. The browser seems to hang during the registration, and nothing progresses beyond a certain point.When I inspect the browser console, I see the following errors:_app-573f798ac9f1a077.js:1 Logger failed attempting to post telemetry data to server Error: Error sending data to Kazmon. Status = 0 at W.n.onerror (_app-573f798ac9f1a077.js:1:221602)   telemetry-s.docusign.net/api/v1/TelemetryWrapper:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT Could you please assist me in resolving this issue? 

Using the Docusign eSignature API, I’m able to send envelopes w/o any issues. I am not setting the expiration date when sending the envelope, but do have a setting on my account with a value of 3 days. My question is, is there a way to get the value of the expiration date (or days that the expiration date is configured for) when the envelope is created, without an additional request being sent via the API to retrieve the envelope details or to get the value from my account?I’m trying to avoid bumping up against any rate limits.

Hi, Please help us with the below error in the screenshot. This happens when selecting the client account for promoting the app to production. 

I’m getting the following permissions policy error when using DocuSign JS on my website. I’ve updated the page headers to set the correct Permissions Policy.{ key: 'Permissions-Policy', value: `geolocation=(self "https://apps-d.docusign.com")`} [Violation] Permissions policy violation: Geolocation access has been blocked because of a permissions policy applied to the current document. See https://goo.gl/EuHzyv for more details.(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2ready @ signing_iframeless_mobile.6672.js?cs=cfe5a6fc98b421a49266:2(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2(anonymous) @ signing_iframeless_mobile.js?cs=d822fccc2:2(anonymous) @ signing_iframeless_mobile.5132.js?cs=36825c07c67f2dd22f3b:2cu @ signing_iframeless_mobile.172.js?cs=539be489332502f5e410:2Ns @ signing_iframeless_mobile.172.js?cs=539

I have a use case below. What do you advise in regards to the best workflow. Im particularly interested in when to use Webform and Powerform in this case.Use Case:I want the below to be the beginning of a Maestro workflow, automating a full contract lifecycle:David completes a form via a shared link and uploads three attachments within the completion. The form data auto-populates a contract template. The contract is then routed to John (internal user), who completes the remaining fields not included in the original form. David’s is able to see all the entries inputted by David, and ideally can edit them, and receives the attachments. Once John finishes the form, the fully completed contract triggers the generation of: An Executive Summary (static template) A Business Terms Summary (static template) One of four Contract Agreements (all dynamic templates with conditional content). As to which one is populated, this depends on which entity is indicated in the form. All generated docume

Here are some of the latest popular questions that developers asked on Docusign Community in the month of July 2025. Thread: Is there a way to realign transformed PDF fields based on original PDF alignment?https://community.docusign.com/esignature-api-63/is-there-a-way-to-re-align-transformed-pdf-fields-based-on-original-pdf-alignment-24757Summary: The developer is using PDF form field transformation to convert PDF AcroForm fields into Docusign tabs. They’ve noticed that the text in these new tabs is always left-aligned, while some of the tabs on the original PDF were center-aligned. They want to know if it’s possible to realign these new tabs to match the alignment in the original document.Answer: Docusign eSignature always left-aligns all tabs and fields. Currently, there's no option to change their alignment to right or center, whether they were added manually or transformed. If you want to change where the text in a tab appears, you would need to reposition the tab itself. Thread:

We built an integration with DocuSign SOAP APIs in 2012 and a few of our clients are still using them. We are hitting the end points https://demo.docusign.net/api/3.0/dsapi.asmxhttps://na2.docusign.net/api/3.0/dsapi.asmxhttps://www.docusign.net/api/3.0/dsapi.asmxto create envelopes for our clients. Recently, we noticed that whenever we add the custom tags for the recipients, they are automatically are required, even if when have not specified the customtabrequired property to true. Whenever we require the custom tag, we specify the two properties to true.CustomTabRequired = trueCustomTabRequireSpecified = trueCan you please let us know what else we need to specify and why all of a sudden these custom tags are required?Thanks

Hi everyone,Since early 2025, I’ve been encountering a problem with the payload received via DocuSign Connect using API version 2.1 in JSON format.Until recently, I was deserializing the notification using a well-defined C# object like this: public class DocuSignEventNotificationResponse {     public string status { get; set; }     public string envelopeId { get; set; }     public string documentsUri { get; set; }     public string recipientsUri { get; set; }     public Sender sender { get; set; } }public class Sender {     public string userName { get; set; }     public string userId { get; set; }     public string accountId { get; set; }     public string email { get; set; } }However, recently the payload arriving in the DocuSign logs seems to have changed completely. For example, now I receive notifications in this format:{  "event": "envelope-completed",  "apiVersion": "v2.1",  "uri": "/restapi/v2.1/accounts/1e78c******8c2db/envelopes/18*******91dca",  "retryCount": 1,  "configurat

The template below is currently configured to display a voided envelope when the email address is updated. At present, the content is static. Have a requirement to display different text based on either a flag / custom field when making a call to v2.1/accounts/xxxxx/envelopes/xxxxx/recipients?resend_envelope=true How can I pass a custom field and make this template conditionally display text based on that custom field? Appreciate your support!

Hi,Currently, I am able to send the DOCX file for signature via DocuSign and the PDF files for review in separate envelopes. But my requirement is to send both files together in a single envelope—one for signature and the others for review. Is there a way to combine them into a single envelope for both signing and review purposes? Both files are attached to the same SharePoint item.

Hello,I’d like to integrate JWT authentication to access the DocuSign API from my server.I understand that, on first use, I need to accept a consent request by visiting a URL like:https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature impersonation&client_id=CLIENT_ID&redirect_uri=https://www.docusign.comMy question is:Once I’ve granted this consent, is it valid indefinitely as long as I don’t change the client_id? Or do I need to repeat this consent step periodically (e.g., when the token expires or per session)?Thanks for your help!

Hello,I am trying to create a developer account. But it didn't let me create in a first step. it just does nothing when clicking on button can you please look into it . the details i am trying to signup is as followsit gives me error in the console Failed to load resource: net::ERR_NETWORK_CHANGEDIs someone facing the same issue?

I'm building a DocuSign integration using the v2.1 REST API. I create an envelope with multiple recipients and documents, and then open the embedded sender view using: POST https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/views/sender{ "returnUrl": "https://myapp/return", "viewAccess": "envelope", "status": "sent" }My goal: let the sender adjust Document Visibility settings before sending the envelope in the preview screen—uncheck/check visibility for a recipient.Go to: Prepare → Advanced Options → enable "Recipients must be signers to view signed documents" → click Next.Under Documents → Document Visibility, uncheck a recipient for a document and hit Done.Error appears: "Document visibility changes could not be saved. Please try again"Then, if I try Send, I get: "The access token provided is expired, revoked or malformed"However, if I remove the "viewAccess": "envelope" field from my sender view request, visibility changes save correctly.I

I am using a free DocuSign developer account and encountering the following error when trying to send an envelope:“The recipient limit on the envelope has been exceeded. The cumulative recipient limit has been exceeded.”I am unsure about the exact recipient limits for free developer accounts. In my case, the number of recipients per envelope is relatively small (2-3), yet this error still occurs. Could you please clarify what the exact recipient limits are for free developer accounts? Also, are there any ways to resolve or work around this issue?

Hi,I have completed go-live process for my app on dev environment and status shows "App is live".But I can not find the apps on production environment, it still shows "No Integration Keys found".Thanks. 

Hi everyone,I'm reaching out because I've encountered an unexpected issue with DocuSign and I'm wondering if anyone else has experienced the same thing.I have an application that has been using DocuSign for over 3 years to handle signature processes. I'm using a demo account, and I've registered an app in the DocuSign developer portal.When a document is signed or declined, DocuSign sends a POST notification (webhook) to my API. For years, the payload I received looked like this, and was successfully deserialized into this C# class: public class DocuSignEventNotificationResponse { public string status { get; set; } public string envelopeId { get; set; } public string documentsUri { get; set; } public string recipientsUri { get; set; } public Sender sender { get; set; } } public class Sender { public string userName { get; set; } public string userId { get; set; } public string accountId { get; set; } public string email { get; set; } } This worked perfectly in my PostNotificationEvent m