Developer

For years, developers building integrations with Docusign APIs have voiced a common frustration: “Why do I need to make 20 eSignature API calls to take my integration live?”We heard you. And we’ve fixed it.Today, we’re excited to announce the launch of a streamlined Go-Live experience in Apps & Keys that eliminates the 20 API calls requirement, making it easier for developers to take their integrations live. 🌟 What’s NewNo more 20 eSignature API calls for Go-Live: Going live is now seamless. Simply select your integration type, enter your production account details, and the built-in validation will check if your integration is eligible to go-live in that production account. If eligible, your integration can, in most cases, go live instantly. 🎯 Why This MattersPreviously, developers were required to make 20 eSignature API calls to start the Go-Live process. In many cases, this effort added no value and slowed down launches. This requirement was especially painful for those working

How can developers take workflows to the next level? 🚀 In this blog, we highlight how This Dot Labs partnered with Monday.com to integrate with Docusign, helping teams streamline processes, cut down on manual tasks, and keep everything moving in one place. It’s a clear example of how the right tools can simplify complex processes. 🎤 Want to hear more? Tracy Lee and Rob Ocel from This Dot Labs will be at Docusign Discover to share insights and stories from this project. 👉 Don’t miss it—register now for Docusign Discover!

Is the eSignature API fully functional on the Personal and Standard plans?For example, if I have a custom PDF that is generated from my own website (automatically filled with the user data), can I use that same PDF to create an envelope on the fly?I can’t find out where I can see what API features are allowed in Personal / Standard / Business / Enterprise. Or can I assume that all features are available in all of these unless specified in the docs? Thanks!

I tried to create the Prefill tab using a POST call, but it threw an error message in Postman. I’m using the Business Pro plan on my account. Below is the request body I used for the API call. Request body:{    "tabs":    {    "prefillTabs": {      "textTabs": [        {          "validationPattern": "",          "xPosition": "124",          "tabId": "4d21df0f-7324-421d-xxxx-07142a62a055",          "shared": "false",          "templateLocked": "false",          "tabLabel": "Text 50eeec15-xxx-4fe3-b950-9f9f6baf1d7d",          "pageNumber": "1",          "underline": "false",          "yPosition": "182",          "requireAll": "false",          "tooltip": "prefiltab",          "tabType": "prefilltab",          "italic": "false",          "required": "false",          "templateRequired": "false",          "locked": "false",          "value": "oooo",          "height": "41",          "disableAutoSize": "false",          "validationMessage": "",          "originalValue": "oooo",          "a

We deployed Docusign embedded signing and embedded CoC download into our own system. We have configured the Japan timezone in Settings > Regional Setting.But we are always got CoC timestamps in UTC timezone. Is it possible to change that into Tokyo Timezone? How can we do it? In addition, can we change language of "Electronic Record and Signature Disclosure" into Japanese in CoC?Looking forward to your guidance. Thank you

This is a follow-up question from my previous post Salesforce Apex Toolkit cannot override Email subject from Docusign Envelope templateBasically I needed to disable option “Custom email and language for each recipient” so that I can dynamically set the email subject and text using Salesforce Apex Toolkit.Now the issue is, the email is always sent in English. How do I set the default email language, with / without Salesforce Apex Toolkit? 

Hello there.I need help with implementing the eSignature API. I have a simple Word document with variables - {{contractor_name}}, {{contractor_email}}. How can I use the API to update this document and populate real data instead of {{contractor_name}} and send it to the recipient?- I tried to use textTabs and send all the necessary data in one request, including a Word document in Base64 - the fields didn't populate.- I tried to manually create a template using the web UI, upload a Word document, manually add sender fields, and then made a request to update these custom fields (docGenFormFields). Nothing. ChatGPT assumed that docGenFormFields wasn't turned on in my account. But how to turn it on, I have no idea.I'm using the developer sandbox account. Can anybody point me to how to implement field population via API?I've used:Document generation manual - https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/documents/document-generation/Prefilled tabs - https://develope

I am embedding Docusign in my application and at the same time i would like share the document links to sign from my application.I have already integrated in my application. And when I am using the embedded link in mail. The link expires in 5 mins or else the link is returning to return url once the signing is complete but once the signing is complete it should close the tab and then return to return urlThe link is open from the mail then how can i close?

 👋 Hey developers! Each edition of the Developer Newsletter is packed with the latest product updates, tutorials, events, and real-world stories to help you get the most out of Docusign APIs and tools. Here’s what we have for you in October.This is your space to explore what’s new, ask questions, share feedback, or chat with our team and other developers in the comments.Docusign Discover ‘25 - Agreements just got smarter 🚀Ready to turn manual, disconnected agreement workflows into fully automated, AI-powered solutions, all in a single day? Docusign Discover is our in-person, builder-focused event where you’ll move beyond the “what” and dive into the “how” with the Docusign Intelligent Agreement Management (IAM) platform.Seats are limited—sign up today!Are you attending Discover? Let us know what you’re looking forward to most, or ask any questions in the comments.News and community highlightsThis Dot Labs connects Docusign to Monday.com with their new extension appThis new extension

Hi, I have created a Docusign Envelope Template (dfsle__EnvelopeConfiguration__c) with name “Opportunity Document”. I also used Docusign Salesforce Apex Toolkit to send the Email and adjust the email subject and email message dynamically. However, the email subject is not being overwritten by the code.Relevant Apex Code:Id mySourceId = opportunityId_i; // Opportunity ID// Create an empty envelope.dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity(mySourceId)); // Use a Salesforce Contact ID as a RecipientContact myContact = opportunityIdToContactIdMap.get(opportunityId_i);// Use the Recipient.fromSource method to create the Recipientdfsle.Recipient myRecipient = dfsle.Recipient.fromSource( myContact.Name, // Recipient name myContact.Email, // Recipient email null, //Optional phone number 'Signer', //Role Name. Specify the exact role name from template new dfsle.Entity(myContact.Id)); // Add Recipient to the EnvelopemyEnvelope = myEnvelope.withRecipients

After working for some time with Docusign's API I thought it would be a good idea to look into the API's 'Connect' feature (https://developers.docusign.com/docs/esign-rest-api/reference/connect/).This allows the sending of information to an application via webhooks when an event occurs for the envelope in question.Currently the only webhook listeners I have available are with Microsoft Teams and Mattermost. I have created the webhook listener in both and can send information to them using the following command: curl -H 'Content-Type:application/json' -d '{"text":"Test text 1"}' <endpoint>where `<endpoint>` is the URL of the webhook listener in either Teams or Mattermost.Next I have tried to send information from an existing Docusign envelope to Teams/Mattermost using the following perl code: use strict;use warnings;use LWP::UserAgentuse HTTP::Request::Common;use JSON;my $EnvelopeID='"92f294ba-a5a0-4a4d-ac85-f08ad5b6a09a"';my $webhookURL=q{https://site.webhook.office.com/web

I want to create a PKS/P12 certificate file from the RSA key pair for JWT.  Have tried open SSL command openssl.exe pkcs12 -export -out docusign.pfx -inkey docusign.key -in docusign.crtWith the inputs as the Private and Public key contents, but getting ‘unable to load certificates’  

It’s that time of year again! We’re so excited to see you all at Dreamforce, October 14-16 in San Francisco! At this year’s event, we’re all about helping you unlock your agreements’ potential.You’ll be able to connect with us to learn more about automating agreement workflows, leveraging AI-powered search to get additional value out of agreements, and integrating Docusign with systems like Salesforce and Slack. Join us at the Docusign Outpost where developers and admins alike can get hands-on experience building with Docusign in our Docusign Developer Lab. You’ll learn how to:Build no-code agreement workflows Automate those workflows by triggering them through the Workflow Builder (formerly Maestro) API Embed workflow steps into your applications for a seamless user experienceIn the lab, you’ll be tasked with building a Workflow Builder (formerly Maestro) workflow through the UI designer, including agreement steps that fit a use case of your choice. These could include anything from c

Hello, community!I’m having trouble publishing my app to production. I had already started the process, but it was rejected due to not meeting the requirement of 20 test requests. After completing this step, I resubmitted the request, but now the go live status only shows “error”, without specifying what went wrong. In addition, I no longer have the option to resubmit. I reached out to support, and they advised me to look for a solution here in the community.

We have recently got DocuSign for our company and integrated it with our OneDrive app. The sync between the two keeps slipping. We need signed documents to be saved to the original forlder. Can anyone advise on where this could be going wrong? It just saves to the primary folder in OneDrive. We had it setup initially but it keeps changing. 

Here are some of the latest popular questions that developers asked in the Docusign Community for the month of September 2025. Thread: Is it possible to wrap the value of an anchor tag?https://community.docusign.com/esignature-api-63/is-it-possible-to-wrap-the-value-of-an-anchor-tag-25514Summary: The developer is adding tabs to a document using anchor strings, and they want to place those tabs within a table. When a recipient fills out the tab, the text within the tab should wrap to the next line so that it stays contained within the table’s borders. Answer: One solution is to set the value of disableAutoSize on the tab to true. This disables the auto-sizing of single line text boxes in the signing screen and only allows users to enter as much data as the text box can hold. It’s also possible to control the size of the text tab with the height and width properties. Thread: Need to add CEO signature in signed documenthttps://community.docusign.com/esignature-api-63/need-to-add-ceo-signa

Hi! I just published a new YouTube video on how to automate contracts faster using Docusign CLM for Salesforce. You’ll see how to generate contracts in one click with Salesforce data, send them for signature, and track status directly in Salesforce. I also show how signed contracts and key terms flow back into Salesforce automatically, saving hours of manual work and reducing errors across your process. Watch the full video 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

I’ve placed the anchor tags for my document in a 3 column table.  The first cell has anchor tag \c1\ for recording a Text Tab value for signer’s company, the second cell has anchor tag \n1\ for recording the signer’s full name, and the last cell has anchor tag \s1\ for recording the signature.The problem is that the displayed value for the anchor tags are not wrapping within the cells of the table.  So if the company names or signer’s names are long, they run into the values of the other cells causing the text to overlap.  Is there a way to force the injected text to wrap in the cell and respect the layout where the anchor tag is defined? I’ve tried to specify the “width” property to 100 and “anchorUnits” property to “pixels” (also tried “inches”), but it doesn’t seem to affect anything:"recipients": {    …    "signers": [      {       ...        “Name”: “Sample Name”        "tabs": {          "signHereTabs": [            {              "anchorString": "\s1\",              "anchorUnits

Hello,I am attempting to implement JWT Grant authentication for my DocuSign integration in a developer account (demo.docusign.net). I consistently receive the following error when making API calls (e.g., oauth/token endpoint):"Authenticatie mislukt (400): no_valid_keys_or_signatures"This translates to no_valid_keys_or_signatures.Here's what I've done so far:I have created an RSA Keypair within my DocuSign developer account for my Integration Key. I am using the Private Key from this newly generated keypair. I have confirmed that it's copied completely, including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- headers/footers, and that there are no extra spaces or missing line breaks. I have correctly set my CLIENT_ID (Integration Key), USER_ID (API Username), ACCOUNT_ID, and DOCUSIGN_BASE_PATH (https://demo.docusign.net) in my application's environment variables. I have performed the required user consent grant by navigating to the consent URL (https://account-d.d

Hi, I am using the C# eSign SDK and am trying to allow users to open a sender view for envelopes that they are not the sender on, but have been granted shared access to. i.e. User A creates a draft envelope and User B opens the sender view for that envelope.The documentation says I need to attach a header ( X-DocuSign-Act-On-Behalf) with the principal user id (User A’s id) as the value in order to act on their behalf.Here’s what I am doing generally in my code (language is Visual Basic). I am using the agent user’s (User B) access token and base uri:DSClient = New DocuSignClient(baseUri & "/restapi")DSClient.Configuration.DefaultHeader.Add("Authorization", "Bearer " & accessToken)DSClient.Configuration.DefaultHeader.Add("X-DocuSign-Act-On-Behalf", principalUserId)...EnvelopesApi.CreateSenderView(accountId, envelopeId) The problem is when I add the header and make the API call, I get an error back:{errorCode: “ACT_ON_BEHALF_USER_NOT_ALLOWED”,errorContent: "An 'Act on Behalf Of'

Hi DocuSign Community,We’ve developed a system that integrates with DocuSign to access templates and send offer letters directly from our portal. In our setup, users log in to our portal with their DocuSign accounts, and from there they can access their templates and send offers through DocuSign using eSignature API.So far, we’ve been testing successfully using a Sandbox account. To move into production, we understand that we need a Partner Production account. We have already filled out and submitted the required form for this, but we haven’t received any response yet.Has anyone else experienced delays with this process? Is there a recommended way to follow up or escalate the request to get our Partner Production account enabled?Any guidance would be greatly appreciated.Thanks in advance!

We host in-person meetings, and want the attendees of the meeting to sign the meeting document via a tablet that gets passed around.  We don’t know who the attendees/signers will be, or how many, but we want them to sign the document within our web application.  After a lot of experimentation with Docusign’s APIs, we’ve taken this approach:We create an envelope (POST to /restapi/v2/accounts/{accountId}/envelopes) with 100 allocated signers (the maximum allowed and hopefully more than will ever attend our meetings).  These are placeholder signers.  Our document also has 100 lines allocated for recording attendee information which feature anchor tags for recording the signature (\s1\, \s2\, etc.), anchor tags for the attendee’s name (\n1\, \n2\, etc.), and anchor tags for recording the attendee’s company (\c1\, \c2\, etc.)   As each attendee enters their information on the tablet, we call Docusign’s recipient-update API endpoint (PUT to /restapi/v2/accounts/{accountId}/envelopes/{envelop

 Hi DocuSign Community!I'm implementing embedded signing with Focused View/Click to Agree using the eSignature JavaScript SDK. I need to display the embedded document in a dialog/modal within my page.Question: Does Focused View provide any built-in dialog/modal component for displaying the embedded document (similar to Click API), or do I need to implement my own custom UI container where the document will be embedded?I've checked the documentation which covers styling the container div, but I want to confirm if there are any built-in presentation options before building a custom solution.Thanks! 

curl --location 'https://demo.docusign.net/restapi/v2.1/accounts/44a2f9ab-3470-4650-b2e6-ac8a4dfea066/envelopes/cf7b3774-9987-4833-a90f-2a66e0a1afbd/views/sender' \--header 'Authorization: Bearer eyJ0eXAiOiJNVCIsImFsZyI6IlJTMjU2Iiwia2lkIjoiNjgxODVmZjEtNGU1MS00Y2U5LWFmMWMtNjg5ODEyMjAzMzE3In0.AQoAAAABAAUABwAAOgdG_s_dSAgAAKLLpwbQ3UgCAEz2CsEDomdHhcUDVEctjgkVAAEAAAAYAAIAAAAFAAAAHQAAAA0AJAAAADZhZTY0YTNkLTRiMjEtNGM1OC04MzU1LTA1ZGU0NTU4NzgzYiIAJAAAADZhZTY0YTNkLTRiMjEtNGM1OC04MzU1LTA1ZGU0NTU4NzgzYhIAAQAAAAYAAABqd3RfYnIjACQAAAA2YWU2NGEzZC00YjIxLTRjNTgtODM1NS0wNWRlNDU1ODc4M2I.DLenJSax1U2_6ASAm9tYR1GCqQTVj37eDJHhSURCMfNKZ2CYLWn-X-NKTVIaYF-xTA51tZtHiSXqiQI-t171Aqk6GnqEEW4oLChLFotkEBoJUvPj3UvUu_87-PDp1meJJmqzYUiOVeF2iHZijdFEWU0apBRbAujitSNyU4R7SEWAZO8i9xUq70lf0heo9qnGs1qWdlRqn5R-rady1ufdrJxlH2vKAoTsPSYCXnvImYWRZyKx5c_kndFUdBMF_JpMZsObhgDXbRH5pBT0hGgxhN1rsaJBY-RdTT_vrYCs4DVux8rduk5cnoZbGBzqK04b_IMncNXKpqqG5GFZFYoXKA' \--header 'Content-Type: application/json' \--data '{  "returnUrl": "https://pms.imi