Developer

Both the prod and developer docusign account have exact identical structure. Can anyone please help? This is blocking a lot of our customers and this is very high priority.this is my prod account envelope request structure → { "emailSubject": "Please review your solar contract", "documents": [ { "documentBase64": "", "name": "Solar Contract", "documentId": "1", "file_extension": "pdf", } ], "recipients": { "signers": [ { "email": "neel@xyz.com", "name": "neel patel", "phone": "(44)", "recipientId": "1", "routingOrder": "1", "clientUserId": "1000", "tabs": {"signHereTabs": [{"xPosition": 199, "yPosition": 176, "pageNumber": 1, "documentId": "1"}]}, } ], "carbonCopies": [{"email": "neel@xyz.com", "name": "neel", "recipientId": "10"}], }, "status": "sent", "eventNot

🎉 Big news from the Docusign developer team—we’re honored to be named a 2025 Postman Champion Award winner! This recognition means a lot to us. Over the past year, we’ve focused on making our APIs easier to work with, more reliable at scale, and better supported with tooling and documentation. Whether you're embedding Docusign into your workflows or building complex integrations, we aim to make that experience as smooth and developer-friendly as possible. I had a fantastic time participating in this year’s POST/CON. The event was filled with in-depth technical sessions, and two topics particularly stood out: scaling APIs for performance and reliability, and fostering strong, authentic developer relations by providing developers with interactive content and tools built from developer feedback. These are areas the Developer Advocacy team deeply cares about, and observing how other teams tackle them has sparked many ideas that we're eager to explore further. A huge thank you to the Postm

  Ever wondered whether vibe coding has a place in building Docusign integrations? I experimented with the Docusign Developer AI Assistant for VS Code to find out whether I could vibe code my way to an embedded signing session and I was pretty surprised with the results.Want to try it out yourself? Learn more about the Docusign Developer AI Assistant and let us know your thoughts! https://developers.docusign.com/tools/visual-studio-code-extension/

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?

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