Developer

 👋 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 “

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 Na

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

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

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:

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?

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": {

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 Use

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

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 /restap

 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 '{  "r

Send to p**************

We've met the following criteria and we're thinking that this is a platform bug because what we're seeing in the go-live dashboard isn't reflecting the "declined" state that's indicated in Go-Live process documentation. We have a status of “Ready to submit” but received decline email. We have the IAM Standard subscription. Here are the criteria we're meeting:- We have, and are submitting this request from, a dev sandbox account and integration key- 20 or more successful API calls in a 24 hour period- Integration exclusively using OAuth 2.0 for authentication- Active production account with a plan activated (this account)- Admin privileges on both the dev and prod accounts- Review submitted via the actions -> go live process- Logs are clean- We’re thousands of calls below the rate limits- The go-live request attached to this message is the one that's been declined twiceWe’re not getting anything in the

We are trying to reach the docusign admin Apis, using authorization code grant for authentication. We are getting the below responses for both Get and post user .Please help me understand where is this going wrong.Below are the steps I am following Get Authorization Code using https://account-d.docusign.com/oauth/token https://account-d.docusign.com/v2/organizations/OrganizationID/users?Authorization=Bearertoken Response code 200,<!DOCTYPE html> <html lang="en" cla

Has anyone integrated DS with infoEd?

Hi,I’m attempting to leverage the embedded URL function in the apex toolkit where a user can initiate a contract and have a user sign on their device in person using embedded URL to docusign.I’m requesting an envelope using this code:         // 2. Create empty envelope tied to CPA        dfsle.Envelope env = dfsle.EnvelopeService.getEmptyEnvelope(            new dfsle.Entity(cpa.Id)        );        // 3. Attach DocuSign template        dfsle.Document doc = dfsle.Document.fromTemplate(            dfsle.UUID.parse(templateUuid),            'Customer Product Agreement'        );        env = env.withDocuments(new List<dfsle.Document>{ doc });        // 4. Create embedded recipient (⚠️ role name must match template role exactly)        dfsle.Recipient signer = dfsle.Recipient.newEmbeddedSigner(            cpa.Primary_Contact__r.Name,            cpa.Primary_Contact__r.

I hope this message finds you well.I am currently working with the API developer account and would like to submit our API for production-level access. However, I am facing some issues in the submission process and would appreciate your guidance on how to proceed.Could you please provide the necessary steps or documentation required to successfully submit the API for production? If there are any prerequisites or approvals needed, kindly let me know.Thank you for your support. Looking forward to your response.Best regards,Nisar 

Hi Team,I am using REST API to create envelope and get it signed by supplier. Once its signed, on top of that signed document we need to add CEO signature automatically. Is it possible in DocuSign. I see its not possible to add directly on my analysis. Can we use composite templates to get this done. Any thoughts would be appreciated.Thanks in advance.

For three days, I have clicked the button for Promote to Production. I click through to my paid account, select the user there, and the system then says there will be a go live decision in 48 hours.24 hours later, I go back, and the Promote to Production.Looking to contact someone in Support fails, as the question mark only has the Support Center, and no option to contact support.How, exactly, do I go live if the automated system doesn’t work and there isn’t support to contact? Or do I need to rewrite my integration to use a service that actually works? 

Has anyone had any success adding an Intelagree integration at the org level? We have multiple accounts under our DocuSign org but having a hard time getting the integration to work.