Developer

Im using envelope level connect keys and setting the includeHMAC to true in the eventNotification object of the envelope.This works and the x-docusign-signature headers are being sent as part of the call. We are using this with a client and initially the x-docusign-signature headers were coming through. But the x-docusign-signature headers are no longer present. Ive checked with our client and the connect key still exists for that account.Is there any reason or a configuration setting that would stop the headers coming through?

Hi everyone,I’m trying to create an integration between RD Station CRM and DocuSign to automate the process of sending contracts to my clients. The idea is that when a deal reaches a specific stage in the CRM (e.g., “Proposal”), the system should automatically send the contract for signature via DocuSign and then update the deal in RD with the contract status and signing link.So far, I’ve found that: RD Station CRM provides a REST API to manage deals and contacts. DocuSign also provides an API to create and send envelopes for signature. I haven’t found any native integration between the two. My questions are: Has anyone implemented something similar using direct API integration or via tools like n8n / Zapier / Make? What’s the best approach to automatically update the contract status back in RD Station CRM? Are there any common pitfalls or limitations I should be aware of when building this integration? Thanks in advance for any help!

Hello,       I have written an application that makes RestAPI calls to a base URI (https://na1.docusign.net/restapi)     I do have clients that need to whitelist all URLs from their servers.     For the example above (na1.docusign.net/restapi), I will now need to have the client whitelist na1-b.docusign.net     My question is:               Does the base URI for the RestAPI calls remain na1.docusign.net.      I assume that the base URI remains the same (na1.docusign.net/restapi).      Thanks.

Hello everyone,We’re currently working on passing values from our website into a DocuSign Maestro webform via API trigger_inputs, and while we’ve had success with text fields and date fields, we’re running into challenges with other field types.Specifically, we want to pre-select a radio button option so that when the webform loads, the correct option is already chosen. For example: Gender field (radio buttons): Options are Male, Female, Others. We’d like to pre-select Male. We suspect this challenge may apply similarly to dropdowns, checkboxes, and phone number fields as well.Has anyone implemented this successfully? Could you please share examples of the correct variable types or payload structure required to map these field types (radio buttons, checkboxes, dropdowns, phone)?I’ve attached screenshots for reference. Any guidance or working examples would be greatly appreciated!Thanks in advance.

Hi,I have implemented the following using the REST API: Created a templated envelope with two recipients. The first recipient is required to sign, so I used the embedded signing focus view on the frontend and completed the process. Updated some additional tab details for the second recipient in the same envelope using the REST API. The second recipient does not need to sign. Now, how can I update the envelope status to ‘Completed’ using the REST API and send it to both recipients?

I have crated a Sandbox Docusign account for our Client using a Gmail test account. I have successfully connected the Sandbox Docusign account with Coupa test instance. Although, when I try to send the document for e-signing I am always getting the error “Unable to send selected attachment for signing. Please retry by clicking on Send button”. Could you please suggest if this error is due to any incomplete configuration? As I can see the Connect webhook is already active.  

I am implementing a integration with my browser application and Docusign. For this I have to call the endpoint from the browser and for this I am using the default fetch command from node. This command results in a unstoppable options command which includes a unstoppable Request-Id header. I have tried using a client instead of the browser which results in everything working perfectly. I have implemented the authentication but this is the final hurdle.Officially Request-Id is not specified in the HTTP schema but a lot of browsers do send this when cross origin querying endpoints. What do you suggest I change or is there a chance the Docusign api will support this?For completeness the error in the console: Access to fetch at 'https://demo.docusign.net/restapi/v2.1/accounts/${accountId}/envelopes/' from origin 'http://localhost:8080' has been blocked by CORS policy: Request header field request-id is not allowed by Access-Control-Allow-Headers in preflight response.

hello :) I’m using power automate to create envelopes.The API doc states the email body has a 10,000 character limit. When i send an email body over 1,500 characters I get a generic 404 response. The only difference in the call seems to be the email body. Over 1,500 chars, bad, under 1,500 chars, good. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/><title>404 - File or directory not found.</title><style type="text/css"><!--body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;}h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"treb

How do I send an ICP Brazil certificate via the API?I'm using PHP with Laravel.And using your Git repo.https://github.com/docusign/docusign-esign-php-laravel/tree/main

DocuSign integration in my app allows to find the DS link in a specific field of my database. This DS link allows me to get the signed document on my server. 90% of the time it works. 10% of the time the DS link does not appear in the field where it is supposed to be.I can not establish any common properties or specificities in between all names for which the DS link does not appear.Thank you if you can help  

Hi,I’m working with a sandbox to integrate docusign in my web app. My service is able to create the envelopes and, checking on the docusign developer page all appear to work properly. The problem is that the mail never get to the recipients.

 I am  trying to access and send documents through the Dropbox integration with DocuSign, but we keep encountering the following error:https://na4.docusign.net/plugins/api/RedirectExternalDocService.aspx?status=fail&error=AuthenticateFailed  Details: Integration: DocuSign connected with Dropbox SharePoint Site URL:  App Version: 4.0.3 Server Version: 4.0.0.6 Status: Dropbox is connected successfully, but when we try to prepare an envelope with a Dropbox file, the authentication fails. Has anyone experienced this issue before? How can we fix this AuthenticateFailed error?Any guidance will be highly appreciated.

When a document gets voided due to the expiration date, I assume the webhook sends out an event to the listener telling the doc has been voided, but I am not receiving any voided event. I am receiving all the other events just not any voided or expired events. Can someone tell me how to configure the voided\canceled\expired documents?

How do I access my sandbox?

Hello everyone,I’m currently working on an integration with the DocuSign API using JWT authentication. When I try to call the API, I get the following error:❌ [send-docusign-signature] DocuSign rejects JWT signature - public/private key mismatch or missing consentHere’s what I’ve already checked: The private key in my code is the one generated when I created the app. The public key has been uploaded correctly in my DocuSign integration settings. My Integration Key (client_id) is correct. I suspect the issue might either be a key mismatch or the fact that the user consent has not yet been granted. My questions are: How can I confirm whether the issue is due to missing user consent versus a key mismatch? What is the exact procedure to generate the consent URL and have the user approve it in the demo/sandbox environment? Are there best practices for managing the lifecycle of keys (rotation, updates) to avoid this type of error? Thanks a lot for your help 🙏 

I'm learning how to use SOAP UI. Does Docusign provide a WSDL (Web Service Description Language) file or some documentation for REST API?

Our next Developer Async Ask Me Anything (AMA) is coming up in September—and we want you to decide what we cover. Cast your vote in the poll below to let us know which topic you’d find most valuable.If you’ve got another idea for a future AMA topic, share it in the comments. Your input helps us make these AMAs as useful and relevant as possible.If you missed the last AMA on embedded signing & sending, you can check it out here. 

💻 While vibe coding is possible with our Docusign Developer AI Assistant, it’s important to be smart about incorporating vibe coding into production projects. Over at The New Stack, I wrote about how the Developer AI Assistant for VS Code can be used to build integrations with trusted AI assistance that goes beyond just vibes.  💡 Check out the post and let me know what you think! Have you tried vibe coding with Docusign yet? Any tips and tricks for others who want to give vibe coding a try responsibly?

Hi,I'm encountering an issue when using the compositeTemplates feature to create an envelope from a template that contains multiple documents.When retrieving this template via the EnvelopeTemplates:list endpoint, only the first document is returned in the response - the remaining documents are omitted.This behavior is different from what I observe in the DocuSign web UI. If I simulate the same process (e.g., by creating an empty envelope and applying the templates), all documents are present as expected.Is this a known limitation of the EnvelopeTemplates:list API? Or am I missing something in the way the template is structured or retrieved? Thanks in advance for any help or clarification.

I am using embedded signing with my API and every day I send documents to sign to many recipients. All the documents I send need to be signed again by our company but it is not viable to do it one by one so I would like to know if there is any way to sign several documents easily. The way it would be done it is that we put our company the last in the recipients order to sign of each document, and then, instead of signing all one by one, sign all at once (of the ones alredy signed by the previous recipients to sign). Thank you.

How to enable live video and screen sharing options for DocuSign Notary in a demo (developer) accountI want to check DocuSign Notary in my developer (demo) account, and I can see the Notary option there.However, while testing, I found that the live video recording and screen sharing features are not available. I need to test and demonstrate the full RON workflow before moving to production.How can I enable the video session and recording features in my demo account, or is there any alternative to achieve the same?

Please explain the process for setting up Remote Online Notarization (RON) with DocuSign Notary in a Developer Account, including configuration and prerequisites.

We have noticed a few errors in our system where the response for the EnvelopeLocks:get endpoint (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopelocks/get/) does not contain the lockToken field.The docs dont seem to have any point which indicates this as expected behaviour.Wanted to know if there is some nuance I am missing?btw we get all the other data about the lock in the response, its just the lockToken that is not there: { lockedByApp: "-", lockedByUser: { uri: "--------------", userId: "--------------------", userName: "------------------" }, lockedUntilDateTime: "--------------------", lockType: "------"} 

Hello,I’ve been working in Maestro Workflows using webforms to build them out. The goal being so that the webforms speak with the workflow so that people on my team can use a link to send out and fill out contracts versus needing to sign into DocuSign. Currently I have set up all my webforms reflected off my contract templates, and then I built out my workflows reflecting the needs of my departments and the flow of my contracts. For example Department X needs 4 types of contracts and so they branch out in different ways. Here’s an example of what a workflow would look like:LinkWebformBranching question 1: Are they A or B?A:Are they B or C? → contracts 1 & 2 B: Are they D or E? → contracts 3 & 4Right now when I test the webform it works perfectly but the branching question 1 is always leading to option B, even though I select all the options for option A. So I’m always getting the wrong contract as a result. When I check my Instances it looks like this: everything is greyed out.