Developer

Here are some useful links for JavaScript resources when developing with Docusign:SDKs:The following SDKs are open sources and each of their npm packages can be found on npm.orghttps://github.com/docusign/docusign-esign-node-client https://github.com/docusign/docusign-click-node-client https://github.com/docusign/docusign-webforms-node-client https://github.com/docusign/docusign-rooms-node-client https://github.com/docusign/docusign-monitor-node-client https://github.com/docusign/docusign-admin-node-clientSample appsSample apps showcase full featured working apps that are designed to demonstrate various features and how they can be used in a hypothetical application focused on different industries and use cases. The following sample apps repos are written in JavaScript:https://github.com/docusign/sample-app-maestro-node https://github.com/docusign/sample-app-navigator-node https://github.com/docusign/sample-app-embeddedsending-node https://github.com/docusign/sample-app-telecom-nodejs

Hello,I’m encountering an issue while trying to create a developer account for the email xxx@ABC.com (not the actual email). When I visit the DocuSign Developer Sandbox page and click the “Get Started” button, nothing happens — the page doesn't load or display anything.I’ve already successfully created an account for yyy@ABC.com, and it worked fine. Could you clarify if there are any specific requirements for the email address in order to proceed?Additionally, upon inspecting the page (F12), I can see a request being sent, and here is the response Any guidance you can provide would be greatly appreciated.Thank you for your help!Best regards,Mickael

Hi everyone,I’m reaching out for your help regarding an issue we're experiencing with our DocuSign integration with HighQ. The integration is authorized and generally works, but we encounter problems when sending certain documents for signature.Issue:Some documents trigger the error message:“The server has encountered an issue while processing this request.”This happens regardless of the method we use to send the document.Key Details:There’s no clear pattern linking the problematic documents. Interestingly, if I upload two identical copies of the same document, one may trigger the error while the other sends successfully.Has anyone encountered a similar issue? Are there any specific troubleshooting steps we can take on the DocuSign side to identify the root cause?Thanks in advance for your support!  

Learn how you can help shape the future of Docusign for Developers with our new public roadmap, see how LaborEdge is revolutionizing healthcare staffing compliance with Docusign, explore upcoming events, expert dev tips and more!Check it out. https://developers.docusign.com/newsletter/2025/february/  

I'm participating in a hackathon and building a project using Docusign's ID verification functionality. However, the API only seems to offer phone authentication as an option. Does anyone know why this might be happening and how I can enable other ID verification methods? Any guidance would be greatly appreciated!

Hi! I just published a new YouTube video explaining how to use Docusign approve and decline buttons to create efficient approval workflows.You’ll learn how to:Add approve/decline buttons to templates to create approval processes. Configure signing orders so documents are routed correctly. Workarounds if you don’t want to waste your envelopes with these buttons!Transform your approval processes with these techniques! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hi DocuSign Community,I'm having trouble sending an envelope via the DocuSign API using a template. I have verified that my template is set up correctly (it works as expected when I create and send an envelope manually from the console). However, when I create an envelope using the API, the envelope is created with a status of "created" (i.e., a draft) rather than "sent".Here’s my setup: Template Details: Template ID: templateId The template contains two recipient roles: one with the role name "provider" and one with "site". The template has required fields and signature tabs already configured. Envelope Definition (API Payload): const envelopeDefinition = { templateId: 'templateId', templateRoles: [ { email: 'provider@ajay.com', name: 'Ajay Parashar', recipientId: '1', routingOrder: '1', roleName: 'provider' // matches template role (case-sensitive) }, { email: 'site1@ajay.com',

I have a Zap setup to pull info/file from Monday.com and then send it via DocuSign. It was working for a while and then all of a sudden over the last 5 days, its stopped and is throwing errors. The latest one I cannot figure out because the sending account is a full admin thus security shouldn't be an issue. I cannot find anywhere in the DocuSign settings for “display” or 'signermustacknowledge'.  Error: Could not create signature request: ACCOUNT_LACKS_PERMISSIONS: This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document Offer of Employment. (Offer of Employment = the Template we use in DocuSign) The error you're encountering indicates that your DocuSign account lacks the necessary permissions to set certain properties, specifically 'display' or 'signermustacknowledge', on the document "Offer of Employment". This typically happens when the account used in the Zap does not have the required permission

Hello,I tried to delete personal data at the development environment. Given account has been closed for few days, using following request:curl --request POST 'https://api-d.docusign.net/management/v2/data_redaction/accounts/8d2d3601-24f5-xxx-xxx-d9acac3d26d2/user' --header 'Authorization:AzMzE3In0....' --header 'Content-Type: application/json' --data-raw '{ "user_id": "91585e2f-xxxx-4a44-bf16-xxxxxxxxxxxxx"}'but i get internal error response:{"error":"internal_server_error","reference_id":"dbb84fb9-3bed-40fd-b708-63112cc15e2b"}Is this functionality temporarily unavailable? Do I need to fulfill any other prerequisites besides closing account?

Our elastic template has the following settings: However, when we look at the certificate of completion, we see that “Must view” and “Must read” are marked as FALSE:How can we make sure the certificate shows accurate information?

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of January 2025. To make sure we see your questions on Stack Overflow, use the tag docusignapi.Thread: Send one carbon copy (CC) in bulk requesthttps://community.docusign.com/esignature-api-63/send-one-carbon-copy-cc-in-bulk-request-22345Summary:  The developer is bulk sending envelopes through the eSignature REST API. Each of the envelopes has a different signer recipient, but they want to add a carbon copy (CC) recipient that will receive a single notification for all of the bulk envelopes. If 20 envelopes are sent, they want the CC recipient to be copied once instead of having the CC recipient receive 20 email notifications.Answer: Unfortunately, what the developer is looking to do is not possible. With bulk sending, each envelope is treated as an independent object, so the CC recipient will be notified for each one independently.Thread: SenderView - Do I create

Does DocuSign API support TLS1.3?

Hi There, We are trying to implement a read-only field in a DocuSign webform that is preset when the form URL is sent from our CRM system. However, when the read-only field is preset from a CRM system, it seems that it can’t be configured as a read-only field. The system throws an error at the beginning of the webform and also after you submit it. When you configure a read-only field that is not getting preset, it is working and the value is getting mapped over to the document as expected upon submitting. I have attached some screenshots below of the errors that are getting triggered when the “CaseID” read-only field is getting preset in the first screen as well as the one at the end.    

Hi there.I have recently promoted an App from the Development Environment to Production. The intention is to replace an existing, live App already there. I do not see an option to ‘disable’ or deactivate the current live App. Any suggestions on this ?ThanksCB

Hello! The legal entity of my company asked me if we can enable the possibility for the end-user to download the Electronic and signature disclosure (what we see in the screenshot).I did not find something like this in the settings.Does someone know if it is possible?Thanks! 

Hi everyone,We’ve encountered an issue with our DocuSign integration and are hoping someone can share their experience.Here’s the situation:We send documents to a DocuSign envelope and specify the documentId for each document in our API request. The API responds with the same documentId values we set. However, when we view the envelope in the DocuSign UI, the documentId appears to have been reset or renumbered (e.g., starting at 1).Has anyone else faced this issue or something similar? If so, how did you handle it?Thanks in advance for any insights!

Hi everyone,I have a question about integration keys in the developer account.If you create an integration key in a free developer account, you need to promote it to production using your production account to move it to production.What about a paid developer account? Do integration keys created in a paid developer account still require promotion to production, or are they promoted to production by default?

Hi! I just published a new YouTube video on how to automate workflows using Docusign agreement rules.You’ll learn how to:Automatically store signed PDFs in Google Drive, OneDrive, or SharePoint. Export recipient-entered data from Docusign forms into spreadsheets. Automatically send follow-up envelopes to the same recipients when a previous envelope is signed.Master seamless integrations to save time and reduce errors in your document processes. You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hello! I have got a Go Live status: Review failed (See OAuth 2.0 migration options).After reading the doc I do not understand what we are doing wrong.Here are the 2 types of calls I do:/oauth/token/clickapi/v1/accounts/{accountId}/clickwraps/{clickWrapId}/agreementsWe have chosen JWT grant authentication.Can you help me understand what is wrong?Thanks a lot!

When using eSign API/SDK, can we somehow enable the option to attach the template PDF of the template/document to be signed via the developer console? If yes, then how?I know that after completing the signing process, the signer receives an email that contains the signed template. But in my case, I want to include the unsigned doc/template as an attachment in the sign request email sent to the signer!!

Hi, Anyone have any thoughts for ways or workarounds to only allow DocuSign to update Salesforce once an envelope is completed?We are using DocuSign Apps Launcher with Salesforce and using DocuSign envelope templates. The document first goes to recipient 1 who is required to make edits to the doc and sign it. Next it goes to an ‘Approver’ who has the option to approve or reject the document Once the Approver approves the doc, the envelope is considered completed and that is what appears in Salesforce. However, we don’t want Salesforce to be updated until the document is completed in case the first recipient had errors in the doc and now they need to be corrected? Any insights would be greatly appreciated!

Hey everyone, hoping yall doing well!I’m trying to Go-Live but have not succed in these past hours. At the moment my app passed review and its saying “Promote to production” with a green circle on the side.So these are my steps while trying to get on production:1.  Click on “Actions”2. Click on “Select Go-Live Account”3. Accept terms and click on “Accept”4. Open the pop-up5. Input email and password from my account (not the developer one) - eSignature Standard PlanAnd this is what I’m getting from it (HTTP 404 PAGE NOT FOUND): Can someone help me please​​​??!!!

Is there a Docusign endpoint that could govern me all the agreements in the user account. I am able to authenticate the user and get the info for the user

I’m using DocuSign Connect to send a webhook to Zapier when a document is completed. When I review the output of the webhook sent to Zapier, I do not see the document field values.  My custom connect is set up using REST v2.1 data format, SIM delivery mode, and data included is the following:Custom Fields Documents Attachments Document Fields Recipients Has anyone else had this issue or know a way I can adjust my configuration so that the output includes the document field values?

Our company is in the DocuSign Partner Program and we have a developer/sandbox account in DocuSign, some of our clients are looking for the feature to have the signature recipients to verify their identity with Bank ID. All signature requests are sent from client instances to DocuSign, I am looking to add the verification feature in our DocuSign integration but the “Identity Verification” is not available on our sandbox account under “Signing and Sending”. How can I get this enabled?