Developer

I am trying to develop a Docusign integration with a dev account. After 20-30 envelopes the API just gives up with a permanent ENVELOPE_LIMIT_EXCEEDED error. Not very helpful for a developer.The support live chat I can’t seem to get to do anything - click the button and nothing happens. Trying to login to support gives me an auth error. How can I contact support to get them to lift this limit. I’m on my second developer account already and I don’t want to keep creating them.Anyone know the email address for support or some way of sorting this?

Calling Login with https://www.docusign.net/api/3.0/credential.asmx fails with "One or both of Username and Password are invalid."  The Login call is made by using “[IntegratorKey]Username” as the username.This just started recently.  I was only made aware of it today, so it could have started today.  All my customers are down. Is it possible that the API has changed and I never received any emails? We got our Integrators Key in 2013 and have not made any changes to this code in quite a while.

Hi all, we had DocuSign Apps Launcher working on our test Salesforce sandbox. I’ve migrated to the User Acceptance Testing sandbox and am getting a ‘Page doesn’t exist - Enter a valid URL and try again’ when we click the ‘Send with DocuSign’.I’ve set up a new template on the UAT sandbox and that’s working, there’s a corresponding IK on my Apps & keys dashboard, so it’s connected to my dev account.The button is calling:{!URLFOR($Site.BaseUrl + '/apex/dfsle__sending', null, [sId = Farm_Visit__c.Id])}I’ve tried swapping out the /apex/… with endpoints for REST & SOAP to no effect. I wasn’t really expecting that to work but /apex/ isn’t listed on the endpoint page listing so figured it was worth 30 seconds to cut’n’paste.I'm assuming that $Site.BaseUrl is correct (https://demo.docusign.net but I don’t know how to check that from Salesforce. That is wha

Hello everyone,I’m encountering a problem when accessing the DocuSign Developer Portal:- URL: https://developers.docusign.com/platform/account/  - After logging in, the page stays completely blank (only the header appears).- In DevTools Network tab, the request to `/api/user/settings` returns HTTP 500.- On the console, I see the error:    TypeError: Cannot read properties of undefined (reading 'account_name')Steps already tried:- Tested in Chrome and Edge (both latest versions).- Cleared cache and cookies, used incognito mode.- Tried on different networks and devices.- Extensions like AdBlock are not the root cause.It seems the frontend cannot proceed without user settings.  Has anyone experienced something similar? Any workaround, or is there a direct way to reset or repair account settings?Thank you for your help!

Dear DocuSign Team,I am writing to express my extreme frustration regarding the Go-Live process for my Integration Key (Podio-API). I have been stuck in a loop between your technical and sales teams for several days now.Here are the facts of my case: Technical Compliance: I have successfully completed 26+ API calls in the developer environment, and my status is currently "Ready to Submit". Account Status: I have already upgraded my account to the Business Pro plan (Account ID: *******), which should support custom integrations. And my Developer Account ID is ******* The Issue: Despite the upgrade, the "Select" button remains disabled, and the system shows my account as "ineligible" to promote an integrator key. I have been told by your technical team that I am on the right track, yet

Hi, I have a template docx where I want to put payment details with QR code image (different for each user).I’ve already tried all of the following (`payment_qr_code` = Base64 encoded image).And none of it displayed anything, it just prints the string/html tag. I use the https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/documentgeneration/updateenvelopedocgenformfields/ API.

Hello everyone!I’m currently working in a company that use Docusign mainly through API to send and manage legal document signature.My company has different brands so we subscribe to the option of branding. Each of our brands needs to have specific e-mails body for the signing invitation, when we resend the invitation and when all signers have signed. From what I understood the main option to customize those templates is to upload custom email resource files.But the disclamer on top of the feature: Important: Customizing resource files is an advanced branding configuration option which can significantly impact your account, and should be done only by someone with expertise in XML and HTML. The master resource files are subject to change without notice. If you customize your resource files, after each release, Docusign recommends you review any changes and update your custom files as needed.I wanted

i am trying to send the  impersonation consent url in my production environment and am getting a 404 error and not sure why. below is the setup of the url:https://PROD_DOCUSIGN/oauth/auth? response_type=code &scope=signature%20impersonation &client_id=YOUR_INTEGRATION_KEY &redirect_uri=YOUR_REDIRECT_URI Thank you

 We are using Salesforce Sandbox with a DocuSign Demo account that includes DocuSign Gen licensing.DocuSign Gen Preview fails with error [100] even for a minimal “Hello World” template and System Administrator user.Please verify and re-provision DocuSign Gen for our Salesforce org and confirm the correct Demo Account ID is bound.ERRORFailed to initiate document generation. Please try again later or contact your administrator for assistance. [100] Error occurred Reference ID: 0a3f3e69-9559-44a1-83f5-05cc70697d12 With Regards,Gana.

After experiencing a significant outage for my largest user group for DocuSign at my organization, I have been asked by management to confirm DocuSign’s role in third party integrations like SAP Ariba falling out of compliance resulting in a complete rejection of signature tasks.Are these third parties reviewed or tested on a regular schedule? DocuSign was very quick to respond and helpful working with the integration team at SAP and it is working.But the question I was asked by our management team is why this wasn’t identified sooner? If anyone has information or experience in overseeing integrations with DocuSign and some best practices you have adopted in your team, I would be grateful to know it.Thanks!

Here are some of the latest popular questions that developers asked in the Docusign Community for the month of January 2026.CORS error on redirection errorSummary: The developer has built an application using

Greetings DocuSigners! My name is Kristen and I own a property management company. I had previous DocuSign experience as a manager in the aviation industry for several years, so when I started my current company over 10 years ago, I knew I wanted to use the product for all lease applications, management agreements, leases, vendor items, communications, checklists and much more. However, after building all of these forms for sometime, they are now becoming time-consuming and cumbersome, and not mobile-friendly, even though DS offers the options, the failure rate for the end-user is discouraging. Here is my current need, and wonder if this could actually be done. I want my website to be able to offer:Easy to use, rental application, with ability to upload applicant drivers license, proof of income, pet info, etc.  A syndication of all of my available rentals. Most current apps are not compatible A way for contractors to apply or mak

I’m currently integrating with the DocuSign eSignature REST API (v2.1) and facing an issue when creating envelopes using composite templates.What I’m Trying to Do Create an envelope using a server template The server template already contains one or more documents At runtime, upload multiple additional attachment documents (PDFs) Use compositeTemplates (serverTemplates + inlineTemplates) for this purpose IssueWhen the server template contains documents, I’m unable to upload multiple additional attachment files via composite templates. Additional documents are ignored / not added to the envelope If the server template has no documents, multiple attachments work as expected

Description:I'm unable to authenticate using JWT Grant with my promoted integration key in production. I receive an issuer_not_found error despite having the integration key properly configured.Configuration:Integration key was created in developer account and promoted to production using DocuSign's go-live process Generated new RSA key pair in production User Application setting: Yes Authentication Method: Authorization Code Grant Redirect URI: http://localhost:8080/callbackError:When attempting JWT authentication, I receive:{"error":"invalid_grant","error_description":"issuer_not_found"}Steps Attempted:Tried granting individual consent via multiple authorization URLs (both account.docusign.com and account-d.docusign.com) A

Following this instruction : https://support.docusign.com/s/document-item?language=en_US&bundleId=als1679428547895&topicId=kyy1679958874136.html&_LANG=enusI was able to create a word document using DocuSign Add-on , and then uploaded to Docusign as template.In MS Word it looks like this :I created an app in C# that uses DocuSign.eSign.dll 8.0.2 version and cannot set values to those "sender field data".Any idea how to do it ?These is what I tried so far : Tried upgrading the library to 8.6.0 to use : envelopeDefinition.PrefillTabs (failed)

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My Azure web App Service to supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

👋 For teams implementing account maintenance workflows in fintech:Do “simple” account updates still turn into custom logic, edge cases, and manual exception handling?If those requests mean repetitive data entry across fragmented systems, slow compliance checks, or frustrated customers, you’re definitely not alone. Our newest Developer Center use case breaks down how developers can modernize account maintenance with secure, scalable self-service workflows—without sacrificing compliance.Key takeaways: Orchestrate self-service and assisted flows in a single process using Maestro workflows Capture structured, validated data with Web Forms to reduce rework and errors Apply policy-driven IDV, KYC, and AML checks only when needed Integrate cleanly with CRMs, core banking systems, and internal ser

Hello,I first created a developer account with my work’s email, then i realized that i do not have access to the advanced signing methods that i have to test.I have a user in my company’s production environment, but it shares the same logs with my developer account, that is not linked to the company, so when i log in the developer realm using my work email, i do not have access to the advanced features. Is there a way i could associate my developer account with my company ?Thank youMathieu

Hi, I am sending a DocuSign email from Apex and using the Salesforce Email Template to generate the Email Body. I am using Messaging.renderStoredEmailTemplate to get the HTML body, and when I check the result using System.debug the HTML content is correctly generated and present. However, after the email is sent, the email body is completely blank. Relevant Code:Messaging.SingleEmailMessage renderResult = Messaging.renderStoredEmailTemplate( opportunityEmailTemplateId, opportunityId_i, myContact.Id);String opportunityOfferEmailContent = renderResult.getHtmlBody();myEnvelope = myEnvelope.withEmail( opportunityOfferEmailSubject, //Subject opportunityOfferEmailContent //Email Body);myEnvelope = dfsle.EnvelopeService.sendEnvelope( myEnvelope, true);How do I resolve this?

Hi, I work as an Integration Engineer for Unit4 and we’ve developed an integration between our ERPx platform and Docusign for document e-signing. We are now introducing some changes in the integration and we noticed an apparent difference on the signer consent process. We used to have a ‘consent_required’ error (HTTP response status 400) when requesting an OAuth token for the signer and we used it to identify that a given signer hadn’t yet given their consent. Currently it seems that all the signer consent process is dealt exclusively on Docusign UI. Can you please confirm if Docusign introduced any changes at the signer consent processing level? Thanks in advance

I have submitted and signed the Docusign API Go Live Form that is linked to the ‘Submit verification form’ button. I would like to know if I need to do anything else aside from wait until the manual Go Live review finishes. My dashboard status did not change status which is making me unsure. And how long might the Go Live process take on average? Thanks 

Hello, I have an issue concerning the simplified view, it would seem that it doesn’t support HTML, or just partly ?When sending an envelope via docusign API, i am sending HTML through the “emailBlurb”, that html is well rendered on the email side. But it is not on the docusign simplified preview pageOn the email side: On the simplified welcome view, many spaces generated, images doesnt work. 

  Hello DocuSign Community,  We are hitting the ENVELOPE_ALLOWANCE_EXCEEDED error on our Developer Demo account, and the error occurs both via the REST API AND the web interface. This rules out the "API has separate limits from web" explanation mentioned in previous threads.  Environment:  - Account type: Developer Demo (sandbox)  - Authorization server: account-d.docusign.com  - API base path: demo.docusign.net/restapi  - Integration method: REST API via official PHP SDK (docusign/esign-client v8.6)  - Error code: ENVELOPE_ALLOWANCE_EXCEEDED  - Error message: "The envelope allowance for the account has been exceeded"  Critical detail:  The same error appears when trying to send envelopes through:  - ✗ REST API calls  - ✗ Web interface (appdemo.docusign.com)  This suggests either a system-wide bug or an account-level issue, not an API-specific quota.  Su

Core ProblemMy organization has implemented Docusign-Connect to send completed envelope to our Laserfiche storage system. This Works as intended for envelopes with a single template however multi-template envelopes additional templates do not express retrain their Envelope Custom fields metadata correctly when transferred to Laserfiche, and instead assume the Envelope Custom Field data of the initial template.  Current DesignEach Template has 4 key pieces of metadataTemplate Category: This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field.  Template Sub-Category:  This could be either Custom Envelope or Document Field and is a static value for the template. Currently set to an Envelope Custom Field. Recipient Account Number: This is currently a Custom Document Field on