Developer

We’ve recently decided to change how we distribute the Docusign Developer Newsletter. While we’re still producing the Newsletter monthly, we’re transitioning to a quarterly email distribution model. Our March issue, coming out next week, is the first issue affected by this change: if you’re a Newsletter subscriber, you’ll receive this issue in your email inbox. The April and May issues, however, will be posted to the Docusign Developer Center and announced here in Docusign Community. We’ll also be posting announcements of each issue to our social media feeds, so feel free to stay up-to-date with us on

A former employee created a custom field integration to add the start date to a docusign agreement. I updated the Hubspot property to ACC Cohort Start date. It was previously just ACC Start date, and now nothing works. This is the connection on the Hubspot end:  This is the connection on the Docusign end:This is what the agreement form looks like in docusign:

The Docusign Intelligent Agreement Management (IAM) platform gives developers more flexibility in how they integrate Docusign and Salesforce.  Download the Salesforce Extension App on Docusign App CenterEasily build and deploy custom agreement workflows without writing any code, securely pulling in and writing back data from Salesforce with the new extension app. 

I calling signature API with JAva SDK.I generate my PDF with itext library and I’m able to extract the correct position and dimension of some table cells in my PDF. I pass these coordinates to SignHereTabs because signers should sign on their own table row in a specific cell.Because PDF coordinates have a bottom-left origin but Docusign’s fixed-positioning coordinates have top-left origin, I reverse my “y” coordinate by subtracting it from page size to get the correct y-from-top value. Itext and Docusign coordinates values are compatible because they both use dots as unit ( = 1/72th of inch)But I have 2 issues :1) position : signHere effective position (as given to signer by Docusign signing view on their website) is about 68 or 72 pixel too low. I don’t know what is shifting signHere tabs 1 row toward the bottom…2) dimension : though I set explicitly signHere width and height, signature are not respecting it and are too big. I could reduce

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of February 2025. To make sure we see your questions on Stack Overflow, use the tag docusignapi.Thread: Webhook payload in XML Formathttps://community.docusign.com/docusign-connect-69/webhook-payload-in-xml-format-22548Summary: The developer is using webhooks with Docusign Connect. They want to change the payload format of their webhook object from XML to JSON.Answer: Once a custom Connect configuration has been created, it’s no

My SetupI have a user access request form built in Webflow that requires users to agree to terms and conditions. Currently, the form has a checkbox that users must check to indicate agreement.What I'm Trying to AccomplishI want to implement a legally binding electronic signature process where:The user simply checks a box to sign the terms and conditions This checkbox action is recorded as a valid electronic signature in DocuSign The signature is legally binding and creates proper audit records The entire process happens within my Webflow form without redirecting to DocuSignTechnical RequirementsThe form needs to maintain its current UX with checkbox-based acceptance Each signature needs to be properly recorded and verifiable Solution should work with Webflow's capabilities Must capture relevant metadata (timestamp, IP address, etc.) for legal validity (op

Hi Community,I have followed all the exact steps and configured docusign.I have provided all the table permissions, and all looks good except one error when I click on View and Sign button which is as attached. Error: “There was a problem opening the document. Please contact your administrator.” Please let me know what exactly is causing this issue and how can I resolve the issue.   

I have been successfully using a composite template to add recipients to a server template.(see attached code) However, one of the recipients - Approver at routing order 3 is now a part of a conditional recipient group. (See attached image) When I now try to overwrite the recipient at routing order 3, i end up with two recipients at routing order 3 instead of one. (See attached image) I tried a workaround where I would simply update the recipient at routing order 3 using PUT method of the recipients endpoint in the REST api, however that did not work either.  How can I overwrite the recipient in the conditional routing group at routing order 3 using a composite template?  { "emailSubject": "@{variables('SubjectLine')"}, "status": "sent", "compositeTemplates": [ { "serverTemplates": [ { "sequence": "1", "templ

Hi there!We currently are working toward adding a DocuSign integration into our App. Our workflow is quite simple and was implemented without issue into our Continuous environment using the eSignature API to create envelopes and Connect to listen to events happening to those envelopes. We use an OAuth2.0 Client to be able to authorize DocuSign to call our backend using a route listening to Connect calls and act on those events. Now that the implementation on Continuous has been successful we would like to implement it on other environments including our Test environment. Every environment use a different base url and a different OAuth client. In order to setup that we looked into the EventNotificaiton property of the envelope to be able to configure a custom url to send our events for that specific envelope. I’m still stuck on one last point, I need to be able to specify the OAuth2.0 configuration to use for that EventNotification. Is there a way to specify it? 

Hello, I am creating a form that requires to activate some fields, I know it is possible to achieve it with the rules. Is it possible to create a rule through the API?. Thanks.

Can anybody guide me to access legacy jar file - net.docusign.api._3.docusignconnect ?

Hi! I just published a new YouTube video on how to configure Docusign to collect payments and save customer payment methods during the signing process.You’ll learn how to:Integrate Stripe, PayPal, and other payment gateways into Docusign. Use formulas to calculate dynamic payment amounts. Set up conditional logic for payment methods like credit card vs. wire transfer.Streamline your payment collection process with Docusign! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with

 Hi EveryoneI am new to DocuSign and currently integrating it with MuleSoft using the "Envelopes Post Envelopes" API. I am sending the following payload, but the envelope is not being populated with the data I am passing. However, when I include xPosition and yPosition, the data appears in the envelope. My goal is to populate the fields using tabLabel instead, but it is not working. How can I resolve this issue?Template with Standard Text field Payload:{ "brandId": "d380fe66-xxxxxxxxxxxxx", "templateId": "63ebae68-xxxxxxxxxxxxxxxxxxxx", // Need full template ID "status": "sent", "compositeTemplates": [ { "templateId": "63ebae68-xxxxxxxxxxxxxxxxx", // Should match above

 PhoneAuthentication is received as null.Code used to add Authentication is below: orignalSigners.IdCheckConfigurationName = "Phone Auth $";                                    RecipientPhoneAuthentication recipientPhoneAuthentication = new RecipientPhoneAuthentication();                                    List<string> senderProvidedNumbers = new List<string>();                                    recipientPhoneAuthentication.SenderProvidedNumbers = senderProvidedNumbers;                                    recipientPhoneAuthentication.SenderProvidedNumbers.Add(t.PhoneNumber);                                    orignalSigners.PhoneAuthentication = recipientPhoneAuthentication; Trying to get Signer with Authentication using following code but the signer.PhoneAuthentication is received as null: System.Net.ServicePointManager.SecurityProtocol = (System.Net.SecurityP

Hi Team,Actually we are using “#Automatically send to eSign”  flow in DocuSign. Previously it used to work but recently flow got broken and we are getting response as Draft from Docusign and not sending for Signature automatically even though we are providing anchor signature details in request body.Can you please let us know what might be the issue ?Thanks in anticipation!Regards,Bhaskari.

Hello,  I’m trying to display the embedded signing view using DocuSign's focus view, but I’m encountering an issue. Here’s the screenshot and the error message from the console log. This is occurring in my local environment.  Could someone please help me understand why this is happening? Below is an example of the code I’m using. I’d really appreciate it if you could point out anything I might be doing wrong. Thank you! 

I am working on a PoC for Integration with Docusign and using Embedded Signing with Focussed View because we have our website and don’t want Admins to go out of application context.I have 2 options to display the document to end user Load the document in the same application window by loading DocusignJS and passing it RecipientViewURL and ClientId. Cross Launch the RecipientViewUrl obtained by making CreateEnvelope and CreateRecipientView API calls.For my integration, I am making Docusign eSignature API calls from a backend service and passing on the URL to the frontend portal.I am also working on using Connect APIs to receive a callback when Envelope event is raised (completed, voided and declined). I want to understandWhat event is raised when the enduser views the Document but Does not perform any action and the URL expires. Close the browser without taking any action

COMO ACHAR A API DO DOCUSIGN HOW TO FIND THE DOCUSIGN API  

Is there a way to translate the message in the AutoRespondedReason field when receiving a Connect callback or when calling the List Recipients API?I see no pattern in the text I receive from this field, sometimes it comes with the STMP error code, and sometimes it doesn’t, and I can’t show this message to the user of my system, because it is not easy to understand the real error that occurs.My APIs are in C#, it would be great if DocuSign could translate the error or give us a way to decode it.

I’m working on updating our Java SDK usage from 2.17 to 6.0.0 and API from v2.0 to v2.1. Given some signature changes I’m comparing with the API references to make sure I’m making the correct changes. We have a process to create templates, and we set a password to prevent accidental editing - in v2.0 it’s part of the envelope template definition (https://developers.docusign.com/docs/esign-rest-api/v2/reference/templates/templates/create/#schema__envelopetemplate_envelopetemplatedefinition). In v2.1 at some point I believe the fields in the template definition object were flattened to the envelopeTemplate object, including the `password` field (

deleted

Im integrating eSignature API using ASP .NET web api core and getting the below error after deploying it on our test site.  My test server supports TLS12 and I explicitly set it for http client handler in my api for DocusignClient.   Monitored the traffic using Wireshark and I could see my test server sends hello handshake, but I do not see the hello handshake from Docusign server, Any leads to resolve this issue greatly appreciated. Thank you Error Content: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.   --- End of inner exception stack trace ---

I have a flow to create envelope, add doc, add recipient, tag (as needed) and send. When I log into DocuSign, I have 2 accounts, a default and a group account for all the appropriate users. Since I need all users to trigger the flow, I changed the connections to all steps to reference the group account number. All step look good EXCEPT Create Envelope. This one gives me the following error: Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'docusign' operation 'GetCustomFields' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: {"errorCode":"USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT","message":"The specified User is not a member of the specified Account."}' I’ve tried creating a new connection and it is still upset. Any help is appreciated. Thanks :)

Hi community,I need some help with the Go-Live process. I’m trying to get my Integration-Key into production since round about a month. There is no problem with the automatich review (20 successful API calls, no polling). But there seems to be some sort of manual review when I try to promote the Integration-Key to a production account. The first two times I tried it took 10-14 days and in the end the review was declined. Today I created a new Integration-Key and tried again and it got declined within a few hours.I actually have no idea why the promotion is declined. I didn’t get a mail or any sort of information about the decline.While waiting for the promotion the first time I created a support ticket with our production account and I was told that there is no support on basic API plan.So what are my options? Currently we’re paying for an API plan that we cannot use.Best regards,Dominik

Hello, I’m trying to use the docusign rest api to create a signing url from a pdf. The problem i’m encountering is no matter whether i sent up a placeholder recipient or use a template to have a user create their own envelope they can sign i get auth blocked. the reason why i’m doing it this way is that A. users in my app may not have a pre-existing docusign account and i don’t want to add a cascade update for all event documents when they make one B. i don’t want our app to keep having to use the hosts docusign account to add people as recipients. all i need is a solution that opens a signing event in a url and the host can get those signed documents