eSignature API

We are generating contracts for our customers and sending them via DocuSign. However, for one of our customers, the contract wasn’t sent and we are receiving the following error:{'errorCode': 'ENVELOPE_IS_INCOMPLETE', 'message': 'The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying recipients for Envelope ID = 1db6cbd9-cd95-4a42-8c43-41ad321bfe77'}This is the first time we have seen this issue. It has worked fine for all our customers till date. Please let us know what’s the exact issue and how can this be fixed.

 When calling RequestJWTUserToken, an exception is returned:Exception: "We call the token API, but the token creation sometimes results in a non-successful HTTP response code," not always.What could be the issue? We are implementing it as shown below.var _apiClient = new ApiClient(_baseurl);token = _apiClient.RequestJWTUserToken(_integratorKey, _userID, _baseurl, Encoding.UTF8.GetBytes(PrivateKey), 1, Scopes);TokenGeneratedAt = DateTime.Now;

SCENARIOWhen calling: PUT {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/docGenFormFields With the following payload:  "docGenFormFields": [    {      "docGenFormFieldList": [        {          "value": "2024 Carbon",          "name": "Z1TKH6C",          "required": "true"        }      ],      "documentId": "1"    }  ]}Returns the following error response body:{    "errorCode": "INVALID_REQUEST_PARAMETER",    "message": "The request contained at least one invalid parameter. Value for 'documentId' is invalid."}The endpoint is NOT honoring the standard value of 1, which has been the normal approach for other DocuSign REST endpoints.RESEARCH 

Hi,Currently to get JWT access token we are following these two steps. Step -1: manual action:Currently to get JWT access token we need to manually prepare JWT JSON and here we need to add start time, expire time and need to generate JWT token.Step-2: Rest APIFrom the above generated JWT token we are execute DocuSign API to get the access token “https://account-d.docusign.com/oauth/token?grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<JWT token>. Is there any way so that with the user credentials/data we need to fire only one API to get the access token no need of again manual generation of JWT token. Is there any way to avoid manual action.  

The docusign folder is not stable when I marked the folder complete and moving to the complete status.   The word “COMPLETED” disapears. 

But everytime, when I type : https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id={my_real_client_id}&redirect_uri=https://localhost:8080/callbackDocusign ask the developer account to sign in, otherwise I cannot get the auth code, so I cannot get the access token by the auth code. So it is not a one time thing, everytime, If I want to call some eSign API, I need to login the developer account everytime, why? 

I am attempting to delete/close an account user using the Python SDK. The access token was obtained using the Oauth Authorization Code Grant Flow. I have the user_read and user_write scopes as well. The schemas were imported from the docusign_admin.models and used to craft the response bodyI am declaring my api client and making the request in the following manner. api_client = ApiClient(host="https://api-d.docusign.net/management")api_client.set_default_header( header_name="Authorization", header_value=f"Bearer {access_token}")users_api = UsersApi(api_client=api_client)request_body = DeleteUserIdentityRequest( identities=[ UserIdentityRequest( id=account_id ) ])response = users_api.delete_identities( organization_id, user_id, request_body)I am getting the following response. The reference id has been redactedHTTP response body: b'{"error":"internal_se

Good morning.   As Administrators of our DocuSign account we create templates for users to send for signatures.   Since yesterday we are encountering the below error on all our DEMO templateswhen clicking on USE.  Can anyone help with this? 

I am reaching out to clarify whether it is possible to download signed documents via the DocuSign API without encryption or without copy restrictions, as we need to automate the process of redacting (blacking out) confidential information** in these documents.  Our current workflow involves receiving signed documents from clients, but they appear to be encrypted or restricted, preventing us from copying or modifying the content. Great!We need to automate the redaction of specific sensitive information before distributing the documents internally.  Could you confirm:  1. Is there an option to download the document without encryption or restrictions via the API?2. If encryption is enforced, is there an official way to process and automatically redact specific content while maintaining compliance?3. Are there any recommended best practices, tools, or integrations within DocuSign that support automated redaction of signed PDFs?We are looking

Is there anyway or any call we can use to retrieve the envelope ID from signing URL.  An example of signing in urL is: 

Hi everyone,I’m reaching out for your help regarding an issue we're experiencing with our DocuSign integration with HighQ. The integration is authorized and generally works, but we encounter problems when sending certain documents for signature.Issue:Some documents trigger the error message:“The server has encountered an issue while processing this request.”This happens regardless of the method we use to send the document.Key Details:There’s no clear pattern linking the problematic documents. Interestingly, if I upload two identical copies of the same document, one may trigger the error while the other sends successfully.Has anyone encountered a similar issue? Are there any specific troubleshooting steps we can take on the DocuSign side to identify the root cause?Thanks in advance for your support! 

I'm participating in a hackathon and building a project using Docusign's ID verification functionality. However, the API only seems to offer phone authentication as an option. Does anyone know why this might be happening and how I can enable other ID verification methods? Any guidance would be greatly appreciated!

Hi DocuSign Community,I'm having trouble sending an envelope via the DocuSign API using a template. I have verified that my template is set up correctly (it works as expected when I create and send an envelope manually from the console). However, when I create an envelope using the API, the envelope is created with a status of "created" (i.e., a draft) rather than "sent".Here’s my setup: Template Details: Template ID: templateId The template contains two recipient roles: one with the role name "provider" and one with "site". The template has required fields and signature tabs already configured. Envelope Definition (API Payload): const envelopeDefinition = { templateId: 'templateId', templateRoles: [ { email: 'provider@a

I have a Zap setup to pull info/file from Monday.com and then send it via DocuSign. It was working for a while and then all of a sudden over the last 5 days, its stopped and is throwing errors. The latest one I cannot figure out because the sending account is a full admin thus security shouldn't be an issue. I cannot find anywhere in the DocuSign settings for “display” or 'signermustacknowledge'.  Error: Could not create signature request: ACCOUNT_LACKS_PERMISSIONS: This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document Offer of Employment. (Offer of Employment = the Template we use in DocuSign) The error you're encountering indicates that your DocuSign account lacks the necessary permissions to set certain properties, specifically 'display' or 'signermustac

Our elastic template has the following settings: However, when we look at the certificate of completion, we see that “Must view” and “Must read” are marked as FALSE:How can we make sure the certificate shows accurate information?

Does DocuSign API support TLS1.3?

Hi There, We are trying to implement a read-only field in a DocuSign webform that is preset when the form URL is sent from our CRM system. However, when the read-only field is preset from a CRM system, it seems that it can’t be configured as a read-only field. The system throws an error at the beginning of the webform and also after you submit it. When you configure a read-only field that is not getting preset, it is working and the value is getting mapped over to the document as expected upon submitting. I have attached some screenshots below of the errors that are getting triggered when the “CaseID” read-only field is getting preset in the first screen as well as the one at the end.  

Hello! The legal entity of my company asked me if we can enable the possibility for the end-user to download the Electronic and signature disclosure (what we see in the screenshot).I did not find something like this in the settings.Does someone know if it is possible?Thanks! 

Hi everyone,We’ve encountered an issue with our DocuSign integration and are hoping someone can share their experience.Here’s the situation:We send documents to a DocuSign envelope and specify the documentId for each document in our API request. The API responds with the same documentId values we set. However, when we view the envelope in the DocuSign UI, the documentId appears to have been reset or renumbered (e.g., starting at 1).Has anyone else faced this issue or something similar? If so, how did you handle it?Thanks in advance for any insights!

Hi everyone,I have a question about integration keys in the developer account.If you create an integration key in a free developer account, you need to promote it to production using your production account to move it to production.What about a paid developer account? Do integration keys created in a paid developer account still require promotion to production, or are they promoted to production by default?

When using eSign API/SDK, can we somehow enable the option to attach the template PDF of the template/document to be signed via the developer console? If yes, then how?I know that after completing the signing process, the signer receives an email that contains the signed template. But in my case, I want to include the unsigned doc/template as an attachment in the sign request email sent to the signer!!

Is there a Docusign endpoint that could govern me all the agreements in the user account. I am able to authenticate the user and get the info for the user

Our company is in the DocuSign Partner Program and we have a developer/sandbox account in DocuSign, some of our clients are looking for the feature to have the signature recipients to verify their identity with Bank ID. All signature requests are sent from client instances to DocuSign, I am looking to add the verification feature in our DocuSign integration but the “Identity Verification” is not available on our sandbox account under “Signing and Sending”. How can I get this enabled? 

Hi everyone,I'm working on a DocuSign integration where I want to use a template that dynamically updates as it progresses through a multi-signer workflow. Here’s the flow I’m trying to achieve:The initial template is populated with some hardcoded values for the first signer. Once the first signer completes and the envelope is redirected to the next signer, the template should dynamically update certain fields (e.g., names, amounts, or other placeholders) using data retrieved from an Azure Storage Account via API. This process should repeat for each signer, with the template being updated dynamically based on the signer’s role and data pulled from Azure.Steps I’ve Considered:Use the DocuSign API to create an envelope based on a pre-defined template. Populate initial tabs (fields)

The CXO of a company needs to sign over 20 envelopes daily, which are sent from various systems like Salesforce, SAP and with the majority coming from Docusign web app. Currently, the CXO uses a mobile app for signing documents. The company has developed a new internal portal for employees, which includes functionality for managing approval processes. Now, the CXO would like to use the new portal to sign all of their pending Docusign envelopes. Is this feasible using embedded signing?