Developer

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?

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!

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,  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?

The July 2025 Developer Newsletter is out! In this month’s issue, we highlight the Connected Fields API. This API lets your Docusign integration poll your Docusign account for installed extensions that can verify data so you can connect those extensions to fields in your Docusign envelopes, thereby enabling on-the-fly data verification for those fields. The Connected Fields API works with prebuilt Docusign data verification types as well as custom types defined using Connected Fields extension apps, so you can build an extension to verify any data you like against any system of record you choose, then use that data verification directly in your integration!More July Newsletter highlights:Paige Rossi shows you how to integrate Stripe payments processing into your Maestro workflows with the Stripe extension app. See how to auto-read data into your workflows with data IO extension apps. Hold the date for Docusign Discover! Our premier developer conference is coming to San Francisco this O

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?

Hi allI am developing/investigating a Docusign integration for an internal app. I have it sending eSignatures so I am confident that it is authorising correctly and can also call the API. I wanted to test out some Web Forms but every call to even list the Web Forms is failing with a 404 error.When sending an envelope, the URL called is “'https://demo.docusign.net/restapi/v2.1/accounts/<account_id>/envelopes'” and the Web Form URL is “'https://demo.docusign.net/restapi/v1.1/accounts/<account_id>/forms'”. Both those values were gotten by stepping through the Python SDK.I must be missing something obvious I assume, but does any one have any ideas where to start investigating?

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

Hi, we are working on a DocuSign integration allowing users to sign documents in-app. We do have requirements to allow users to forward the signature to external users. We initially create the Signer record with a clientUserId (so the user can sign in-app using the embedded signature), and to forward the signature, we are trying to update the signer record with the external user info and remove the clientUserId value so Docusign would send out an email inviting them to sign the envelope. However, when updating the Signer, and not specifying the clientUserId (as the documentation mentions), the clientUserId persists. Updating the clientUserId to another value does work, but deleting it doesn’t. Any recommendations here?

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.1)use DocuSign\eSign\Model\Tabs;use DocuSign\eSign\Model\Text;$textTabs = [];if ($r

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 errors, it is very difficult to fix quickly, it becomes almost impossible and t

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-later-24382Summary: This developer wants to hide the popup that appears (as seen in the screenshot below) when a user clicks Finish Later while signing a document with Docusign.Answer: This confirmation popup is a standard part of the Docusign signing process and can’t be disabled. However, it is possible to disable the Finish Later button entirely if you don’t want to give users that option. To do that, follow the steps below:Access Branding Settings: Navigate to the Brands section within Docusign eSignature Admin. Edit the Resource File: For the specific brand being used in the signing session, download the "Signing Resource File." This is an XML file that controls various

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? 

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 critical part of our application's authentication system.Given these constraints, we are seeking advice or suggestions from the community o

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?