Help Forums

We used to be able to send envelope creation requests to the API with FirstName and LastName variables in the JSON payload.  And the responses included FirstName and LastName.  Now we are suddenly getting responses that only include ‘name’.  Did something change recently?

Hi All I have just been given admin rights and I note the new Bulk Send V2 is now out I already have templates set up that I use for document generation (not set up with previous Bulk Send)I have all the signatories set up below with all the spots on the document they would need to sign  It then takes me to this page where I painfully copy and paste all the relevant data into each field The document is then generated as below exampleNote the doc has lots more signature fields this is just an example My question is, I have been trying to use the Bulk Send V2  as it looks like it could save me so much time. However how do I use the template to fill in the Document Generation fields and also save the pre-existing signatories? Some are approvers, some are witnesses etc and I don’t know how to replicate this in the CSV file. It looks like if you use the Bulk Send option you HAVE to input a bulk send recipient?  

Hey everyone,I’m working on a workflow setup where I have a parent workflow that kicks off a child workflow which includes approval logic. My goal is for the parent workflow to automatically finish or abort if those approvals within child workflow are rejected.Does anyone have experience with this or any suggestion on how to achieve this? All input is greatly appreciated.

Hello,         I am developing an integration from Workday to DocuSign to pull the completed documents into Workday. I am getting following error when trying to authenticate to the endpoint - https://account-d.docusign.com/oauth/token to get the access tokenError code : badrequestResponse :{"error":"invalid_grant","error_description":"unsupported_grant_type"}I have the following Grant type which works fine in Postman. In addition to grant type, assertion key is generated which is passed along with grant type in Workdayassertion=@{props['jwt.assertion']}&grant_type=urn:ietf:params:oauth:grant-type:jwt-bearerPostman: 

I want to create an envelope with the third party notary service and template via the eSignature REST API v2.1. But the TemplateRoles doesn’t have any attributes about notary recipient to set notaryType=remote, notarySourceType=thirdparty and notaryThirdPartyPartner=onenotary. The third party notary info that only can be set in recipients.notaries, but I can not set recipients and templateRoles at the same time. Since I get the error: The request contained at least one invalid parameter. 'recipients' may not be specifed when 'templateId' is set. Use 'templateRoles'.Any ideas? Thanks!

Hello! I know this is more of a Microsoft question but we all know how effective Microsoft support is. Previously, organization users were able to sign documents without creating an account, and then access those documents again via the links in the emails they received. Now, however, clicking the links in their emails is giving them Azure AD access denied errors. Has anyone else had this issue before, and if so how did you resolve it?The only thing that’s changed in our organization is that we’re starting to rollout a new domain, but the users reporting the issue don’t yet have it. We are also unable to recreate the issue in development.  

Hello, I need to send the same document for signature to multiple different recipients. All signatures should be together on the same page at the end of the document. BUT how can I make sure that once everyone signs that they don’t receive the final document and see all the signatures? I don’t want them to see each other for privacy reasons. I hope this makes sense. My goal is to have their signatures all on the same page but they should not be able to see who signed the document. Each and everyone should receive only the version with their signature and no one else’s.  Thanks for helping.Mitar

As a REALTOR, we send many contracts to clients for signature, and I’ve been using DocuSign for about 10yrs now. I’ve personally never had an issue with it.  For some reason today when sending envelopes to yahoo accounts, recipients are not receiving them. All other email networks work well and receive envelopes except for yahoo.  Even after pressing Resend, neither does the original email nor the resend are being receives. and Yes I’ve checked make sure emails are correct.  Anyone else having this issue?

Hello,  My subscription expires on December 15. If I run out of envelopes and purchase an additional $100 envelope package today, I would like to know whether the added envelopes will be usable only until December 15.

I have begun receiving phishing message from Docusign.  There seems to be no way to notify Docusign so they can clean up these accounts and get rid of them.  My only choice is to block the Docusign address.  Anyone else running into this?

I am the system admin for our account. All of the templates in use have been created by me over the years. This morning I created a new template, first from a word document, and then from that same word document converted to a PDF file. The result was the same, when either I or our users try to access the template we get an error: “Unable to create the envelope”.  Has anyone else experienced this? How do we solve it? Any idea what causes it? I created another template this morning using a different file with no issues. Thanks!  

Hi there, We already set up the DocuSign Webhook, “Docusign Connect” which is running successfully in our PROD environment for another Signature API called from our application to connect to DocuSign. We are able to connect, so there are no issues with our DocuSign Connect configurations. However, we are using Legacy Mode and are also trying to implement new behavior with PowerForms in DocuSign where we created a PowerForm template. The user is able to click on the PowerForm URL from our application and proceed to fill out the PowerForm; however, Docusign is not publishing the signed document and sending it back to us after use signs and submits it. Does anyone have any suggestions on any approaches/solutions we can try? Screenshots have been provided as per our current DocuSign and PowerForm configurations. Any help is appreciated. Thanks,Linda 

Until recently, I had two Docusign accounts. I’ll use fake email addresses below to describe the situation and problem. The login for my long-standing Docusign account is: FirstEmailAddress@host.com At some point, I created a second Docusign account with: SecondEmailAddress@host.com - this account only ever had one envelope in it. A couple weeks ago, I tried a combination of actions to get the SecondEmailAddress@host.com released so I can use it on my main account (i.e., would like to revise FirstEmailAddress@host.com to SecondEmailAddress@host.com). First, on my secondary Docusign account, I revised my SecondEmailAddress@host.com email address to ThirdEmailAddress@host.com). That didn’t release the gmail address for re-use on Docusign. Then, I deleted my secondary Docusign account. That also didn’t release my gmail address. When I try to revise FirstEmailAddress@host.com to SecondEmailAddress@host.com, I get an error message: "This security information you are trying to add is already

In DocuSign CLM, when I add a field to the form in document generation it is not showing up in my params folder to add to the workflow.  Even updates I have made to existing params are not updating (mostly just names or merge tags).  Is there another step to update the form fields so they show up?  I don’t remember running into this in the past so it is odd.Thanks!

Hi Everyone! I am trying to create a simple workflow with maybe 1 or 2 steps to combine two documents together. One is a document an individual will upload and will be different every time. The second is a static document that is stored in clm.  I don't need anything to be sent out for signature, this is just a simple flow that I am trying to get to work.  These two documents are supposed to be combined together under the Combined Documents  So, the testing document is supposed to be under the same tab as combined documents.  Any suggestions? 

Hi,I have recently started working on Docusign Gen Templates and looking to add a watermark to the template? How can I get started on this?

When a user begins filling out a DocuSign CLM intake form that includes a field linked to a CSV file (e.g., Vendor Name), the form auto-saves its state. A change is made by the admin to the CSV file after this stage and If the user exits without submitting and later returns to the form, the linked field displays the previously saved data rather than the latest values from the updated CSV. This results in outdated information being shown unless the user discards the draft and starts a new form, which then correctly reflects the updated CSV data. How can I fix this?

I am experiencing an issue with creating a developer account (issue atttached with image). I have attempted the process multiple times using different devices and networks, but the problem persists.Could you please assist me in resolving this issue?Thank you for your support.   

On the My Tasks screen, as a CLM Admin, I can see the 1) Orphaned tasks and 2) Unassigned tasks.However, I am unable to extract the information from the 2 screens into Excel spreadsheets, OR create a Report(s) of this information.  DocuSign Support advise that there is no existing Report for this.Ideally I would like to be able to schedule a Report / Reports to be generated say weekly, and sent to the Head of Sales so they can respond to me with the names of the new CLM Users that I can assign to each task.  

Hi,  I have created an app in demo developer account in docusign. I am using docusign api https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes  to send document to my website user on their signup as well to get document status. Now My testing is done, my app is approved but i try to promote app to go-live, it gives me error “these accounts don't support API integrations. Select a different production account to continue'. Now i have two queriesIs it happening due to the fact that my live account does not any plan yet? If i take developer api plan in live account, will i  be able to promote app from developer account and Api integration will keep working with live keys?Kindly help me on this as i am not able to find any relevant information regarding and i am really confused on which plan to take in order for API integration to work. i am aware that developer API plan has a envelope limit/month.Thanks in advance 

hi docusign team i requested before 48 hours for go live after all successfully calling api for 20 times but now status show declined can i know the reason behind this?

Hi, We are unable to go live with our company account and cannot login to the support centre to open a case either, even thou we manage to login to the actual signing and developer account, and it’s not a recently made account. This is the first problem.The second, more important issue is the API go-life. I try to follow the instructions and get this error integration key.What are we supposed to do?Who can help? Where can I find an actual support email or phone number? Reaching support shouldn’t be that difficult for a paid platform!

Hello,I’m looking to set up the scheduled send attribute when creating an envelope using composite templates, but running into some issues. I understand to apply scheduled send it needs to use the following payload:            "workflow": {              "scheduledSending": {                "rules": [                  {                    "resumeDate": "2025-07-01T15:55:00.0000000Z"                  }                ]              }            }When I use this payload in a Create Envelope request that does NOT use composite templates, it is working correctly. I’m seeing it create the envelope with the defined workflow and see that it is set up to be scheduled for send out on the date specified. This is the request that works correctly:{  "emailSubject": "Please sign this document set",  "documents": [    {      "documentBase64": "<base64encodedString",      "name": "Lorem Ipsum",      "fileExtension": "pdf",      "documentId": "1"    }  ],  "workflow": {    "scheduledSending": {     

We have docusign connect setup to receive events and to monitor the recipient authentication status. The authentication method we are currently using is KBA and the RecipientAuthenticationStatus we receive is correct:<RecipientAuthenticationStatus> <IDLookupResult> <Status>Failed</Status> <EventTimestamp>2025-06-30T22:41:25.04Z</EventTimestamp> </IDLookupResult></RecipientAuthenticationStatus>However, when switching to SMS authentication and according to this doc https://www.docusign.net/api/3.0/schema/dsx.xsd, which might be outdatedthere should be PhoneAuthResult under the RecipientAuthenticationStatus. after testing this is not the case and instead i see an empty object with no info:<RecipientAuthenticationStatus />Any ideas how to get the PhoneAuthResult to show up?

Hi.How can I get support if the Support page wont let us login?We have a Business Pro subscription.  We can login to support.  Therfore we cannot raise a ticket / case to get support.Subscription was over a day ago.Error page“Unable to log in.If this is your first login attempt after purchasing a DocuSign plan, allow 15 minutes for account creation before accessing your account.For all other log in scenarios,  contact DocuSign Support  for assistance.”Directed to contact support.  But we cant contact docusign support as it wont let us.