eSignature API

The Go Live Status for my App is "Pending approval" along with an alert at the top that says "After submitting for review and signing the envelope, please allow for 48 hours and DO NOT submit for review again", but it also shows a link that says "Click here to proceed". Should I click on this link or should I wait for 48 hours as the alert says? 

Hello,I was trying to connect to DS using a PowerShell script and received the following error message: 'Error: Consent required.' Does anyone know the reason for this error and how I can fix it?  

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?

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!

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 

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?

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

I have a text tab assigned to a recipient and I’m prefilling its content when creating the envelope via Docusign API. I need to break the line using \n,  but when I add this character in my text, the text tab shows it instead of breaking the line. I also tried \\n, but had no success.How can I accomplish this?

I'm working on a DocuSign integration using the eSignature API (sandbox environment) and I need to configure BCC email settings on envelopes using the email_settings.bccEmailAddresses field.The request works perfectly in the API Explorer:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeemailsettings/create/?explorer=true However, when I try the same request from my Ruby application (using the official SDK), I get this error only when bccEmailAddresses is included: {  "errorCode": "API_REQUEST_IS_FORBIDDEN",  "message": "The API request is forbidden. Request blocked due to excess usage"}HTTP status: 444 Without the email_settings, the envelope is created successfully.I also tried to set email_settings during the create_envelope call, but it did not work — the field is either ignored or causes the same error depending on how it's passed. Even when correctly structured (and working in the API Explorer), it fails in the application context.Details: SDK: docus

Bonjour,Je vous contacte concernant un dysfonctionnement observé lors de l'envoi de documents XML via l'API DocuSign.Jusqu’à récemment, nous pouvions transmettre des fichiers au format .xml dans une enveloppe, et ceux-ci étaient correctement interprétés et affichés de manière lisible dans l'interface DocuSign.Cependant, depuis peu, bien que l’appel à l’API (POST /envelopes) retourne un code 201 (Created), le document XML n’est plus converti ni affiché correctement. Il apparaît désormais sous forme brute (texte XML non rendu) pour les signataires, ce qui nuit à la lisibilité et à l’expérience utilisateur.Je souhaiterais savoir : Si ce changement est volontaire (ex. : mise à jour du moteur de rendu DocuSign) Ou s’il est possible de restaurer le comportement antérieur via une configuration spécifique Dans l’attente de votre retour, 

I am having issues related to RECIPIENT_LIMIT_EXCEEDED on what I believe is a free account.  Most of the responses to this have said the limit is 5 recipients.  I am trying to send 2 signers and 2 CC’d users and getting this error.  I have tried with different emails and everything and am still getting the same error.  Everything works fine if I take my CC’d users off the email.Any help would be appreciated.

Hello Everyone, I am creating a webform for a loan application, and I see that there is an option for currency in the webform, but I cant figure out how to link it to an API in the template I have. I’ve tried to use a text box that has a number validation, but that isnt working. I’ve tried just a text box, and manually changed the API reference in the webform, but that didnt work either. Am I missing something?  

I am trying to void an envelope using the DocuSign REST API. I used the API Explorer provided in the DocuSign Developer Portal.Here is what I did:✅ API endpoint:PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId}✅ Request body I used (in API Explorer):{ "status": "voided", "voidedReason": "No longer needed" } ✅ The response I get back:{ "envelopeId": "e811fcff-e313-4234-a755-09d394729536" } Notice — there is no "status": "voided" returned in the response.✅ When I run GET /envelopes/{envelopeId} afterwards, the envelope still shows status "sent" (not "voided").✅ I can still access the signing link and sign the envelope.What I have tried: Confirmed that I used the correct accountId and envelopeId Using API Explorer, so OAuth and headers are handled Provided valid voidedReason and "status": "voided" in body Tried multiple times — same result Question: Why is my envelope not being voided even though I am calling the correct endpoint? Is this an issue with API Explorer or somethin

Hello CommunityI appreciate all the kind people that are willing to help me. But I have a problem thats a bit tricky, that you may already know about. Any cards, banks, money assuming it wasnt fraud, is still controlled by them. They have the ability to freeze my assetts and funds. And now that the day is getting started I no longer know who is who anymore. I dont know which ones are the good guys and the bad guys, and my life is still at stake. I will do all I can to fix these couple of small issues and get settled in, but I dont know what that means outside of me, getting a new phone, computer etc. Anyways just wanted to let yall know im trying and this is where things get difficult for me. So until I can get things sorted if you could have some patience I would appreciate it.John

Hi Team,I've been testing a web app that generates prescriptions. The process involves the nurse entering the client’s information and selecting the required medications. There are two recipients in the workflow: the first is myself (to review that the document is populated correctly), and the second is the doctor, who needs to sign it.Up until yesterday afternoon, I was receiving the DocuSign email almost instantly. However, since then, the emails have been significantly delayed—sometimes taking several hours to arrive.Could this be due to a usage limit on my account? Have I possibly triggered a throttle by running too many tests?Appreciate any insights—thanks!Bradt to how many i can do? 

In an embedded template editor, saving template with a prefill tab results in an error.The error message is “The access token provided is expired, revoked or malformed.” Please see the attached screenshot. A red border line appears around the prefill tab. The access token is valid, when I remove the prefill tab and save my template it is successful without any error. I can also create prefill tabs using API request.What is the issue? Anyone has some ideas?   

This is already the 4th time that this has happened to me:- I'm unable to log in. I use a password manager, so I'm not writing it wrong.- I request the code to reset my password, and I don't receive any message.- I'm not able to create a new account because my phone numbers has been blocked (and my friends too, because I need a new phone number to create a new accountThis is frustrating; every time this happens, I lose my Templates, configurations, apps, and so on. Also, my phone number is not available to create a new account. So, I get blocked.It is not possible to work under these circumstances, which happen every other week.How to get unblocked and avoid getting blocked again? 

Hello,I made a few API calls through Postman and noticed some failed requests. Could you help me understand the reasons for these failures?  

I am trying to use the Folder Archive Task API. But I am getting an error that “Documents and folders lists cannot be null.”Following is the Error Response:{ "Error": { "HttpStatusCode": 422, "UserMessage": "Validation Error", "DeveloperMessage": "See the list of validation errors", "ErrorCode": 101, "ReferenceId": "60bb783e-c6ec-49f2-b991-22303cb7ff84" }, "ValidationErrors": [ { "PropertyName": "folderArchiveTaskFilesToZip", "UserMessage": "Documents and folders lists cannot be null.", "DeveloperMessage": "Documents and folders lists cannot be null.", "ErrorCode": 1003 } ]}And Here is my request body: { "DocumentsToZip": [ { "Href": "https://apiuatna11.springcm.com/v2/c517b2a4-c268-4e62-abd2-c11efbd14e55/documents/1f8941b5-13d1-4d2e-ad55-7d53047d1021" } ], "DestinationFolder": { "Href": "https://apiuatna11.springcm.com/v2/c517b2a4-c268-4e62-

Hi.  We recently integrated DocuSign with our Treasury Management System, Reval.  The bank account management software is called IBAM.  When sending documents via IBAM for internal signature [ie signer update], DocuSign doesn’t allow the signer to open their DocuSign account to sign the document with their personal, uploaded signature image.  It only allows them to sign with a generic signature which we all know will not be accepted by the bank.Any advice?  I created a case with DocuSign in April, and they told me when a document is sent via IBAM to DocuSign, the signer should be able to use their personal account.  That is now how it is happening.  Before I open another case, I wondered if anyone else has experience this issue, and if so, how was it corrected?Thanks,Tammy

Hello,I apologize if this question has already been raised, but after searching extensively for similar issues, I couldn’t find a definitive answer.We would like to use a dedicated account specifically created for API access. This account would be shared by all our users to send envelopes to recipients, both inside and outside our organization.We want the user interaction with the API account to be entirely transparent, they should not need to log in to the API account, even once. I have read online that this setup is possible, but we are struggling to get it working as intended.I was able to obtain consent to use the API account on my PC, but when I attempt to send an envelope from another PC, it prompts me to sign in to the account to grant consent again.Shouldn’t the consent only be requested once?Perhaps we’re missing a critical configuration step?Here’s the URL we use to obtain consent:https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation

Hello,We have recently completed the integration between SAP SuccessFactors and DocuSign for onboarding purposes. The process is working correctly, and documents are being sent to new hires automatically after their data is processed.However, for compliance and identity verification reasons, we would like to enable multi-factor authentication (MFA) — such as SMS verification, phone authentication, or access code — at the moment the new hire receives the DocuSign envelope.Our goal is to ensure that the recipient is the correct person before any document is opened or signed.Could you please confirm: Is MFA (e.g. SMS, phone call, access code, or ID verification) supported for signers via the SuccessFactors–DocuSign integration? If yes, is this available in all SuccessFactors versions, or only from a certain release onwards? Are there any SAP KBA articles or DocuSign guides available to configure this correctly? Any help or guidance would be greatly appreciated!Thank you in advance.

Hi everyone,Until a few days ago, I had never used DocuSign, so I’m sure my problem is something simple—but I just can’t figure it out.I’ve built a web app where our nurses and doctors can create prescriptions for medications. The workflow is: the nurse selects the patient from the database, chooses the medications, and this information populates into a DocuSign template.Once all the details have been entered, the user clicks “Send to DocuSign.” At this point, a new browser window opens with the DocuSign document, which is great—it allows the nurse to review everything before proceeding.Here’s the issue: after that review step, I want the document to be sent to the doctor, who only needs to sign it and add the date, but also needs to edit the medications if required.Right now, it’s making me sign the document, which then completes it. That’s not what I want—I just want to preview it, then pass it to the doctor for their signature and potential edits.I’m guessing the issue is with how I

I’m writing an integration that will need to email the same document to hundreds of different people to sign.  The application should run with no user intervention, so I’m using a JWT Grant and have setup a template for my document to be signed.  My code can successfully use the JWT grant to get a Bearer token.  But, when I use the Bearer token to call the eSignature API for sending an envelope, I get an HTML page back.  I do not get a document set to the signer.  I’m getting some type of error, but the returned HTML is no help on what the error is. URL I’m calling: https://account-d.docusign.com/v2.1/accounts/<my account id>/envelopesPOST body:{  "templateId": "dd5bb40b-2801-4434-babe-1e01eccc8ded",  "templateRoles": [    {      "name": "Eric Calvert",      "email": "xxxxxxxxxx@xxxxx.com",      "roleName": "signer"    }  ],  "status": "sent"}Code snippet (golang):     req.Header.Set("Content-Type", "application/json")    req.Header.Set("Authorization", fmt.Sprintf("Bearer %s", t

I have a signature date text using the DateSigned tab from DocuSign java client. I noticed it uses time zone from the sender's account setting. Is there a way to set a time zone specifically for one of the date signed tab? Don't want to update the account setting. I am using the envelope API to set the data in document  Thanks