eSignature API

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?

Hi there,We’ve been using the DocGen API (https://developers.docusign.com/docs/docgensend-api/) to create pre-populated documents using a word template. In our word-template we’ve been using a custom font family Ciutadella.We’ve been having mixed success with some generated documents (pdf output) looking accurate, and some seemingly using a different font or have issues with spacing or alignment.Are custom fonts support by this API / Docusign, and if so what steps do we need to take to ensure it can be successfully used?Thanks!

Hello,How can I increase the size of the signature window via the REST API ? I would like something like that :   Moreover, is it possible to only enable focused window to avoid closing the modal when touching the screen outside it Regards,Arthur

I am following this code sample and kept running into many errors.One of the error was that it could not find body so realized to use const result = await accountApi.createClickwrap(accountId, clickwrapRequest); instead of the following as given in code baseconst result = await accountApi.createClickwrap(accountId, { clickwrapRequest });But now I am stuck at 401 error, unable to understand the error at all. {  statusCode: 401,  header: Object [AxiosHeaders] {    'cache-control': 'no-cache',    'x-docusign-tracetoken': '86….,    'x-docusign-node': 'DA...',    'strict-transport-security': 'max-age=31536000; includeSubDomains; preload',    date: 'Thu, 23 Jan 2025 19:04:23 GMT',    'content-length': '0',

Hey, I try to localize email and sing compent by signing user and I send by API envelop body: {  "documents": [    {      "documentBase64": "{{document}}",      "documentId": "123",      "fileExtension": "doc",      "name": "document"    }  ],  "emailSubject": "Custom subject",  "BrandId": "brand id from portal",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "{{recipientId}}",        "routingOrder": "1",        "localePolicy": {         "cultureName": "es-ES",          "languageCode": "es"        },         "tabs": {                    "signHereTabs": [                        {                            "anchorString": "/sn1/",                            "anchorUnits": "pixels",

When defining an embedded signer, we need to provide a clientUserId along with the recipient's name and email. The clientUserId is a sender-defined identifier for the embedded recipient, enabling the generation of a signing URL for them. How can this be accomplished when envelope is initiated using the DocuSign web app and recipient should sign using embedded signing in a custom built mobile app

Hello,Using REST API , zoom buttons arent visible until a signature has been drawn on the document , how can i fix it please ?regards,Arthur

I am using the DocuSign API to create an envelope with a document that requires signatures from three different signers. My implementation involves the following: Embedded Signing: I need to generate recipient views for all three signers. However, I am currently only able to generate the view for the first signer. When I attempt to generate views for the other two signers, it doesn't work. How can I resolve this issue to allow recipient views for all three signers? Webhook Triggers: I have set up a webhook with specific events configured. I need to be notified when the first signer completes their signing so I can generate the recipient view for the next signer. However, I am not receiving the event that indicates the first signer has completed signing. Which specific event(s) should I configure in the webhook to ensure I get notified when a signer completes their signing? Are there additional s

I have this error when i’m trying to send an envelope:"errorCode":"ACCOUNT_LACKS_PERMISSIONS","message":"This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document ..."this is the production account. Testing in the developer account i never get that error. What is the soultion for this issue ?