Developer

I am using embedded signing with my API and every day I send documents to sign to many recipients. All the documents I send need to be signed again by our company but it is not viable to do it one by one so I would like to know if there is any way to sign several documents easily. The way it would be done it is that we put our company the last in the recipients order to sign of each document, and then, instead of signing all one by one, sign all at once (of the ones alredy signed by the previous recipients to sign). Thank you.

How to enable live video and screen sharing options for DocuSign Notary in a demo (developer) accountI want to check DocuSign Notary in my developer (demo) account, and I can see the Notary option there.However, while testing, I found that the live video recording and screen sharing features are not available. I need to test and demonstrate the full RON workflow before moving to production.How can I enable the video session and recording features in my demo account, or is there any alternative to achieve the same?

Please explain the process for setting up Remote Online Notarization (RON) with DocuSign Notary in a Developer Account, including configuration and prerequisites.

We have noticed a few errors in our system where the response for the EnvelopeLocks:get endpoint (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopelocks/get/) does not contain the lockToken field.The docs dont seem to have any point which indicates this as expected behaviour.Wanted to know if there is some nuance I am missing?btw we get all the other data about the lock in the response, its just the lockToken that is not there: { lockedByApp: "-", lockedByUser: { uri: "--------------", userId: "--------------------", userName: "------------------" }, lockedUntilDateTime: "--------------------", lockType: "------"} 

Hello,I’ve been working in Maestro Workflows using webforms to build them out. The goal being so that the webforms speak with the workflow so that people on my team can use a link to send out and fill out contracts versus needing to sign into DocuSign. Currently I have set up all my webforms reflected off my contract templates, and then I built out my workflows reflecting the needs of my departments and the flow of my contracts. For example Department X needs 4 types of contracts and so they branch out in different ways. Here’s an example of what a workflow would look like:LinkWebformBranching question 1: Are they A or B?A:Are they B or C? → contracts 1 & 2 B: Are they D or E? → contracts 3 & 4Right now when I test the webform it works perfectly but the branching question 1 is always leading to option B, even though I select all the options for option A. So I’m always getting the wrong contract as a result. When I check my Instances it looks like this: everything is greyed out.

I wanted to ask if there are there any APIs available for the following tasks?1. Fetching the total number of documents that have not been signed bythe recipients, or to provide the status of all the documents?2. Fetching the total number of envelopes that are in a pending or failed state?3. Fetching logs or metrics data for Docusign CLM and eSignature thatwould contain latency (duration) and reliability (http status code)information for APIs being called, CLM Workflow Execution Stages orEnvelopes Processing Stages along with their statuses?4. Fetching the start to end time of all the CLM workflows?

What I wanted:I need to use both Remote Signing & Embedded Signing in a single DocuSign template (Single Signer). My goal is to redirect the user to a custom page once they complete the signing process, whether they sign through the flow page or via the email link I send for the signature in DocuSign.What I've already tried: I have tried implementing both BrandId (for remote signing) and ClientUserId (for embedded signing) in the same template. This approach is working fine for embedded signing, but I am facing issues with remote signing: The exception is thrown when using remote signing, and the user is not redirected to the custom page after signing. What I know: Signing Completed URLs can be set in In-session Landing Pages. In-session Landing Pages are an account-level setting, and these settings apply to all templates in the account. The Problem: I want to redirect users to a custom page after signing, but In-session Landing Pages work at the account level, meaning they

Hi everyone,I’ve heard that DocuSign uses Onfido in some of its identity verification workflows.My question is:Is it possible to pass existing Onfido verification data (photo of the document & video with face) directly to DocuSign in the background, so that the user can generate a Qualified Electronic Signature (QES) without going through the identity verification process again?If yes, could someone share documentation or examples showing how to integrate this, ideally via API?Thanks in advance!

Hi,I am updating an embedded signing flow that uses a iFrame element on a page to use the Docusign JS method defined here (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/#docusign-js). I get the recipient URL and pass it to the following code:  var iframurl = "{{iframeUrl}}"; window.DocuSign.loadDocuSign('xxxx').then((docusign) => { const signing = docusign.signing({ url: iframurl, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary button */ backgroundColor: '#333', /** Text color of primary button */ color: '#fff', } }, /** High-level components we allow specific overrides for */ signingNavigationButton: { finishText: 'Custom Button Te

How can I implement notary using DocuSign video conferencing? Can you please provide the code implementation for Remote Online Notarization?Can you please help me

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!