Developer

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, 

The template already exists, and it contains text tabs created using the Pre-fill Tools.What I'm trying to do is dynamically prefill those text tabs before the envelope is sent, by using the API.Specifically, I am:Using PHP SDK (DocuSign\eSign\Model\Text, Tabs, TemplateRole, and PrefillTabs)Ensuring the tab_label matches exactly with the Data Label from the template.Passing the values into PrefillTabs and attaching it to the EnvelopeDefinition.Despite these steps, the fields are not being prefilled as expected. I've tried three different approaches (listed below), but none worked.Could you please confirm:Whether PrefillTabs should be used in this scenario.If so, whether the use of tab_label and value is correct.Any working example or official guidance for using Prefill Tabs with a template-based envelope, where the tab was added via the Pre-fill Tools UI.We tried several methods, but none of them worked.

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?  

Hi All,I am implementing Maestro Workflow and it throws errors for various reasons, but error descriptions are not developer friendly to fix those errors easily. For e,g mentioned below error { "name": "Execute_eSign_Scope_47ac200c-b553-4ad9-a1bc-d55afa5d28b4", "startTime": "2025-06-06T19:30:13.7287018Z", "endTime": "2025-06-06T19:30:15.4834359Z", "code": "BadRequest", "status": "Failed", "apiError": { "message": "Error creating envelope for the Esign scope", "internalErrorCode": "ERR_10999", "internalTraceId": "047e235f919f7c23850e780df4eb6b0b", "apiError": "{\"errorCode\":\"UNSPECIFIED_ERROR\",\"message\":\"Object reference not set to an instance of an object.\"}" -- This error does not tell me what is missing to pass into workflow for e.g. whether I am missing to pass any recipient details, or mandatory fields info, then what mandatory field is throwing this error. Without knowing exact er

Here are some of the latest popular questions that developers asked on Docusign Community in the month of June 2025.Thread: Hide finish later option popup when it appears on clicking of "Finish Later"https://community.docusign.com/esignature-api-63/hide-finish-later-option-popup-when-it-appear-on-clicking-of-finish-la

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

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? 

Hello DocuSign Community,We're currently facing a challenge while trying to integrate the DocuSign eSignature SDK (docusign-esign-java) into our Java application. We are using the RESTEasy client version 3.13.2.FINAL, and we've encountered the following error:RESTEASY003215: could not find writer for content-type application/x-www-form-urlencoded type: javax.ws.rs.core.Form In an attempt to resolve this issue, we updated the versions of resteasy-jaxb-provider and resteasy-multipart-provider, hoping that it would fix the compatibility issue or the error above. Unfortunately, this approach did not yield the desired outcome.We also considered updating the version of resteasy-client to a more recent one. However, we found that the newer versions of resteasy-client are not compatible with our current version of keycloak-admin-client (19.0.3), which is a crit

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?   

I’m trying to request a phone call and it’s not working. I need to talk to support! I will not be renewing if it’s this hard to get support.

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? 

For the past few days me and my team have been trying to create a free Docusign developer account but every time we click the “Get Started” button, nothing happens. We have tried on multiple devices (laptop, desktop, phone) and in different browsers but we are all getting the same result. There are no errors displayed, the “Get Started” button just greys out for a second then nothing happens. Can someone please help in resolving this?

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 } ]}

I have successfully integrated docusign connect in my development environment, and it is working well.Then I moved to production environment, and it is not working. There is not any option in the docusign production account to configure the webhook.Thanks

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:

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

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

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

Does anyone know of an open source (and up to date) Django integration or guide of the eSignature flow? 

not sure what to do, please help as I am new to the api and am trying to test it out

I have requirement for DocuSign “Finish Later” option using API. Is it possible to hide the popup that appear once user click on Finish Later button. Refer below screenshotIs it possible to make Email Field editable that shows in above screenshot.