Developer

Hi everyone,We're using the DocuSign API to send legal agreements (Unilateral Undertaking and Customer Supply Agreement) via our platform. The envelope is generated using the primary user's profile — it includes their name, address, and other key details. That user is assigned as the signer and receives the envelope via email.However, in many cases the property has two owners, and we need both individuals to sign the same document — even though it’s initially triggered and sent using just one user's profile and email.Our goals: The primary user receives the envelope and signs as normal. The same envelope should allow a second person (co-owner) to sign. This may either be: Another signer using the same email address, or A second signer added by the first signer at the time of signing (if possible). Our questions: What’s the best way to set up the envelope via the API to allow two signers, if we only have the primary signer’s email at the time of sending? Can both recipien

We’ve just published a brand new developer use case focused on Compliance and Identity Verification, and it’s packed with ways to help you build secure, compliant verification flows right into your applications.Whether you work in financial services, insurance, or any industry that requires strong identity checks, this guide walks you through Docusign tools and APIs you can use to:Verify signer identity with multiple authentication options   Meet industry regulations while keeping the user experience smooth   Integrate verification directly into your signing workflows  Check it out here: Compliance & Identity Verification Use Case What kinds of solutions are you building for this use case? We would love to hear your thoughts. Share your feedback in the comments so we can continue making these resources even better for you! 

With SOAP API, I can send envelope up to 35 MB most of the time. If it’s more than 35 MB, DocuSign returns error REQUEST_ENTITY_TOO_LARGE. However, I had a case where envelope contains a 17 MB PDF, with 2 supplement files (10 MB and 14 MB). The envelope was sent successfully. Why?WIth REST API, the limit is 25 MB. If envelope sent is more than 25 MB, DocuSign returns error request is too large. Sent envelope with 30 MB PDF and error returned is:REQUEST_ENTITY_TOO_LARGE - The request size of 41625837 bytes exceeded the maximum size of 35651584 bytesFile size is 30,487 KB. The maximum size limit is not 35 MB. Should the limits be different between SOAP and REST? I’m trying to figure out whether the issue is on our server.

I am creating an integration with my App using the .NET SDK. My App is written in VB.NET, and I have installed the package “DocuSign.eSign.dll” V 8.3.0 (latest). I have downloaded the C# JWTConsole example and tried that - everything works great! - I get the emails, I can sign, I see the envelope in the dashboard, status is “sent” etc… all good. This example is also using the DocuSign.eSign.dll package.My main project is in VB.NET, so I convert (using the Telerik C# to VB converter) the C# code, and paste that in to my project… with a little bit of tweaking here and there I can get it all “working” - insomuch as I can run it, I get no errors, I can log in to the Docusign dashboard where I can see the envelope with a status of “sent”, I even get webhooks from DocuSign with status of “envelope_sent” and “client_sent” - but I get no Signer email - I have checked that the email address is correct. I can click RESEND on the dashboard, but I still get no email.What could I be doing wrong? -

I need to go live my app , my develope Integration Key is “8c174c81-7390-446b-a128-814fef95c028”，And it was declined wihout any reason.How can I get the reason?

So I have seen a few people that have the same issue. I have tried the best answer to open support. Now I get this reply But I still can’t access developer account. Clicking on the button just redirect me to maestro page. i have tried to login with my email, but I can’t. I tried to change my password but it said that I don’t have any account.What should I do from this? 

I'm trying to set up JWT Grant authentication in the DocuSign sandbox, but I'm constantly running into an invalid_grant / issuer_not_found error, even though I have successfully completed the consent process.My Configuration Environment: Development (account-d.docusign.com) Integration Key: 1b490ae4-97d1-4b5b-a4d4-cee9998fdf03 API Account ID: 73228f49-0509-4526-ac11-20a1025960e3 User ID (the user who granted consent): 80a3a400-b695-4fbf-9809-7cf4538d9419 Problem DescriptionMy server-side application (a Firebase Cloud Function on Node.js) is using the official docusign-esign library to call requestJWTUserToken. In response, I receive a 400 Bad Request error with the following body:{ "error": "invalid_grant", "error_description": "issuer_not_found"}What I've Already Tried Verified all IDs: I have repeatedly checked the Integration Key, API Account ID, and User ID against the details on the "Apps and Keys" page. They are correct. Verified the endpoint: My code is using account-d

Curious about creating a smooth, in-app signing experience with Docusign? We recently hosted an async Ask Me Anything (AMA) with ​@paige.rossi, Lead Developer Advocate at Docusign, where developers submitted their questions on embedding eSignature using the Docusign API.Below is a recap of the top questions and their answers.What’s the difference between embedded signing and embedded sending?Answer: These two terms sound similar but serve different purposes in your Docusign integration. Embedded signing lets signers complete documents within your app or website, instead of navigating away to check their email. It’s all about making the signing experience faster and smoother for your users. Embedded sending, on the other hand, is for the senders. It allows you to embed the Docusign sending experience into your own app or portal, so users can create and send envelopes without going to Docusign.com. Why does this matter?By embedding either (or both), you streamline the agreement workflo

Hi all,I’m using a JWT Grant flow in PHP (RS256).The token works perfectly against the sandbox endpoint:https://demo.docusign.net/restapi/v2.1/accounts But when I send the exact same JWT to the Maestro (developer) endpoint:https://api-d.docusign.com/v1/accounts DocuSign returns:“Jwt payload is an invalid JSON”Does anyone know why the payload is accepted in demo but rejected in Maestro/API-D?What’s different ?Thanks in advance for any help 🙏

I am using the C# SDK and the ListStatusChanges method to get multiple envelopes that we have open. The returned object Envelope class doesn’t appear to have a Comments property. It does have HasComments property but even this seems to be null on the returned object. I don’t see any options to include comments on the ListStatusChangesOptions class. The only Comments related API calls I see is to get the comment transcript as a PDF, however I really just want the comments themselves, not a PDF. It's worth noting, the API reference does show a Comments property on the Envelope object, but this does not exist in the C# SDK. Is there any way to get the comments using the C# SDK as objects, or is this just not possible at the moment?Envelope Class - Docusign CSharp Docs: DocuSign.eSign.Model.Envelope Class Reference

Hi,I've been trying to create a DocuSign developer account, but no matter which email I use, the registration process doesn't complete. I even tested the process with an existing email, expecting an error message indicating that the account already exists, but instead, the "Get Started" button stays in a submit state and nothing happens—no error message or confirmation.At this point, I'm unsure if the registration form is working correctly. I have attempted the process with five different emails and have also tried the following troubleshooting steps:Clearing cookies and cache Using a private/incognito window Trying a VPN Using a mobile device on a different networkDespite these efforts, the issue persists. Could someone please assist me in resolving this?Thank you.

Well, when I create the envelope with status “sent”, usually I got the “create” envelope email, from DocuSign, but never the one to sign it. So I signed the document from the DocuSign page and then I got the “complete” email, but no the email that request the signature.Even from the DocuSign dashboard I select the envelope and hit the “resend” button and still not getting the email. I checked the the email address is correct. Is there a setting that I need to change?

Hi all,I'm currently working on integrating DocuSign into my C# application. One of the features I’d like to implement is Signing Groups. While I can see that the DocuSign REST API does support Signing Groups (as referenced in the official documentation), it appears that the DocuSign.eSign.dll NuGet package does not expose equivalent functionality.Could someone confirm if this functionality is currently missing from the NuGet library, or if there’s an alternative way to access Signing Group features through the SDK that I might have overlooked?Thank you!

I have Docusign integrated with Salesforce. Currently, I have a DocuGen Template created and I can click a Salesforce button to generate a document from an Opportunity, complete with various merge fields. I have a use case where I’d like to help automate workflows by having a Salesforce Flow (with Invocable Apex assistance, if necessary) take a given Opportunity, generate the ContentDocument, and then attach the ContentVersion as an email along with a Salesforce Email template and send it to a Contact. I can see how to generate a Docusign Envelope through Apex (really great documentation btw), but I don’t want an entire envelope. I just want to generate the doc itself, and send that raw doc attached to a templated email to the designated Contact for review. I cannot find any documentation about how to use the DocuGen features to use the Template and merge fields to generate the doc so that I can use it as an attachment. Any help is appreciated. Thanks!

In my Salesforce org, I’ve installed the eSignature app. I’ve successfully configured and activated the app user, and I’ve also created an envelope. Now, I want to send a PDF file as an attachment to the client using that envelope. This should be done automatically through Apex, triggered after a specific action. The email should include the DocuSign envelope and attach related documents from the record. What I need to know is: how can I use Apex to send an email to the customer, using the existing envelope and attaching the related existing documents?Note:Is this possible to implement? Can it be done using only Apex, or with Flow, or both?

Hi, if anyone could help with this, that would be awesome. I’m facing the following issue: I create an instance of the webform in the backend, then send the form URL and instance token to the frontend. If I clear the browser data and try to render the form using the form URL and instance token, it works. If I refresh the page without creating a new webform instance and try to re-render using the same URL and token, it also works. The problem starts when I create a new webform instance — for example, when the user changes some data — and then try to re-render it. In this case, the form tries to load, but it shows a “Something went wrong” message. When checking the network tab, the returned error is: “Session invalid.”it is only going to render again if i clear browser data. Has anyone faced this before?Do you have any idea what might be causing this or how I could fix it?  

What’s the difference between embedded signing and embedded sending?

Hi DocuSign Team,I'm trying to create a developer account, but the sign-up process doesn’t complete and no error message is shown.Steps I’ve already tried: Used different devices and browsers Switched to different networks Cleared browser cache and cookies Despite these attempts, I’m still unable to proceed. Could you please assist me with this issue? Thank you, 

HiI'm using the PHP SDK for esigning, working all great, we have all kinda of different dynamic fields, checkboxes, radio fields, text fields, etc. working great, but now the client has asked us for the following:Whenever the client has signed the PDF and the signed the PDF is returned either by mail or the webhook, the PDF only contains the filled in values, so the checked checkboxes, selected radio boxes for example, leaving a white gap where the user made no choice. Is it possible to make DocuSign render all elements?How the signed pdf is now (user selected no):How we would like to have it:  

I’m programmatically adding CheckboxGroup and RadioGroup fields to a 2-page PDF using the DocuSign REST API (SDK version 5.5.0). During signing, the signer can interact with the checkboxes and radio buttons without any issues.✅ During signing: Checkboxes can be selected Radio buttons can be chosen ❌ Issue after signing: In the final completed PDF, the selected fields show an "X" mark instead of the expected checkmark (✔) for checkboxes or filled circles for radio buttons. 🔧 Details: Using DocuSign eSignature API SDK Version: 5.5.0 Fields are added via CheckboxGroup and RadioGroup Environment: Developer Sandbox (demo.docusign.net)   ❓My question:How can I ensure that the final, signed PDF displays: ✔ checkmarks for selected checkboxes, and ● filled circles for selected radio buttons?

Hello,I’m trying to create a DocuSign developer sandbox account, but I'm unable to complete the process. The browser seems to hang during the registration, and nothing progresses beyond a certain point.When I inspect the browser console, I see the following errors:_app-573f798ac9f1a077.js:1 Logger failed attempting to post telemetry data to server Error: Error sending data to Kazmon. Status = 0 at W.n.onerror (_app-573f798ac9f1a077.js:1:221602)   telemetry-s.docusign.net/api/v1/TelemetryWrapper:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT Could you please assist me in resolving this issue? 

Using the Docusign eSignature API, I’m able to send envelopes w/o any issues. I am not setting the expiration date when sending the envelope, but do have a setting on my account with a value of 3 days. My question is, is there a way to get the value of the expiration date (or days that the expiration date is configured for) when the envelope is created, without an additional request being sent via the API to retrieve the envelope details or to get the value from my account?I’m trying to avoid bumping up against any rate limits.

Hi, Please help us with the below error in the screenshot. This happens when selecting the client account for promoting the app to production.