eSignature API

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 poss

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.

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?

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!

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?

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.

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.

We built an integration with DocuSign SOAP APIs in 2012 and a few of our clients are still using them. We are hitting the end points https://demo.docusign.net/api/3.0/dsapi.asmxhttps://na2.docusign.net/api/3.0/dsapi.asmxhttps://www.docusign.net/api/3.0/dsapi.asmxto create envelopes for our clients. Recently, we noticed that whenever we add the custom tags for the recipients, they are automatically are required, even if when have not specified the customtabrequired property to true. Whenever we require the custom tag, we specify the two properties to true.CustomTabRequired = trueCustomTabRequireSpecified = tr

The template below is currently configured to display a voided envelope when the email address is updated. At present, the content is static. Have a requirement to display different text based on either a flag / custom field when making a call to v2.1/accounts/xxxxx/envelopes/xxxxx/recipients?resend_envelope=true How can I pass a custom field and make this template conditionally display text based on that custom field? Appreciate your support!

Hello,I’d like to integrate JWT authentication to access the DocuSign API from my server.I understand that, on first use, I need to accept a consent request by visiting a URL like:https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature impersonation&client_id=CLIENT_ID&redirect_uri=https://www.docusign.comMy question is:Once I’ve granted this consent, is it valid indefinitely as long as I don’t change the client_id? Or do I need to repeat this consent step periodically (e.g., when the token expires or per session)?Thanks for your help!

Hello,I am trying to create a developer account. But it didn't let me create in a first step. it just does nothing when clicking on button can you please look into it . the details i am trying to signup is as followsit gives me error in the console Failed to load resource: net::ERR_NETWORK_CHANGEDIs someone facing the same issue?

I'm building a DocuSign integration using the v2.1 REST API. I create an envelope with multiple recipients and documents, and then open the embedded sender view using: POST https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/views/sender{ "returnUrl": "https://myapp/return", "viewAccess": "envelope", "status": "sent" }My goal: let the sender adjust Document Visibility settings before sending the envelope in the preview screen—uncheck/check visibility for a recipient.Go to: Prepare → Advanced Options → enable "Recipients must be signers to view signed documents" → click Next.Under Documents → Document Visibility, uncheck a recipient for a document and hit Done.Error appears: "Document visibility changes could not be saved. Please try again"Then, if I try Send, I get: "The access token provided is expired, revoked or malformed"

I am using a free DocuSign developer account and encountering the following error when trying to send an envelope:“The recipient limit on the envelope has been exceeded. The cumulative recipient limit has been exceeded.”I am unsure about the exact recipient limits for free developer accounts. In my case, the number of recipients per envelope is relatively small (2-3), yet this error still occurs. Could you please clarify what the exact recipient limits are for free developer accounts? Also, are there any ways to resolve or work around this issue?

Hi all,I’m integrating DocuSign with my application using the Node.js SDK and template roles. When I first set up my integration, the template autofilled a few fields as expected. However, now when envelopes are sent, the recipients still receive the emails, but none of the fields in the template are being filled out—even though the data I’m passing looks correct.Here’s a summary of my setup and what I’ve tried:I’m using the createEnvelope API with a templateId and templateRoles.The envelope is sent successfully, and recipients get the email, but all fields are blank.The data I’m passing to the tabs property in templateRoles matches the field names in my template.When I first set this up, a few fields were autofilled, but now none are, even though the code and data structure haven’t changed.I’ve double-checked that the role names and field na

Hey Docusign community,I have a Docusign account with a few users. I am trying to perform common CRUD operations with users using the Users api through the Python SDK. I was able to remove (or close, as you call it) a user from the account using this: from docusign_esign import UsersApi, UserInformationdef remove_user(users_api: UsersApi, account_id: str, user_ids: list[str]): users_info = [ UserInformation(user_id=user_id) for user_id in user_ids ] user_info_list = UserInfoList(users=users_info) return users_api.delete(account_id=account_id, user_info_list=user_info_list) Now, I want to reactivate this same user using the Python SDK. How can I do that? I have tried these two enable functions below, but with no success: def get_user(users_api: UsersApi, account_id: str, user_id: str): return users_api.get_information(account_id=account_id, user_id=user_id)def enable_user(users_api

I include our CFO as a signer/guarantor on all the agreement envelopes I send to new clients. All of a sudden, he no longer receives the envelopes to sign.  Nothing's changed.  I need support 

Hello @Everyone,I'm encountering an issue with DocuSign Java SDK integration in my Spring Boot application, specifically concerning email notifications for signers and carbon copy (CC) recipients.Here's a breakdown of my setup and the problem:Setup: We have multiple signers, and their routing order is set sequentially. We have two carbon copy (CC) recipients, both assigned a routing order of "1". Observed Issues: Initial Email (Signing Request): When the document is sent for signing, signers receive the email according to their sequential routing order. However, both carbon copy users also receive an email at this initial stage, seemingly along with the signer who has routing order 1. Declined Email: If any signer declines the signing process: Signers with a routing order less than

When I have more than one copy recipient, an error will be reported. it will tips “The specified envelope has duplicate recipients”

My docusign webhook api calls work in developer account but they fail in prod account giving me KeyErrors in prod. Why is it different and when was this change made?Here’s how the dev response looks like: ``` {"status": "completed","documentsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/documents","recipientsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/recipients","attachmentsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/attachments","envelopeUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd","emailSubject": "Please review your solar contract","envelopeId": "8554a84b-c12e-4d66-a3ae-asdasasd","signingLocation": "online","customFieldsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/custom_fields","notificationUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/notification","enableWetSign": "true","allowMarkup": "false","allowReassign": "true",

Hi everyone,I'm using the eSignature REST API v2.1 and enabling "transformPdfFields": true to automatically convert PDF AcroForm fields into DocuSign tabs.What I’ve noticed is:In the original PDF, some text fields are center-aligned.After transformation, those fields become left-aligned, and there seems to be no way to restore the original alignment.My questions:Is there a current way (via tab properties or metadata) to re-align or preserve the original alignment of transformed fields?Is there a plan to allow alignment options (left, center, right) on transformed tabs in the future?Thanks!  

Hi DocuSign Community,I'm working on an integration where I need to detect when the first recipient (vendor) signs a document so I can trigger a specific workflow (update status, send notifications, etc.).However, despite configuring my DocuSign Connect webhook to include recipient-signed and recipient-completed, I only receive the envelope-completed event, and never any recipient-level ones.🔧 My Setup: I’ve registered a webhook using the POST /accounts/{accountId}/connect API. events configured:  jsonCopyEditevents: [ "recipient-signed", "recipient-completed", "envelope-completed", "envelope-declined", "envelope-voided" ] The webhook URL is a secure public HTTPS endpoint (not localhost/tunnel). Routing order is sequential: