eSignature API

Hi, I have a weird behaviour I do not understand. I’m using the envlope-API to create an envelope based on a template (/restapi/v2.1/accounts/{{accountId}}/envelopes). My destination is the development tenant. For this API Call I use the following request body { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email": "Some.Name@test.com", "name": "Some Name", "roleName": "signer", "tabs": { "companyTabs": [ { "value": "test Company 1", "tabLabel": "atb.docusignFields.label-company <id>",

Hi, I’m implementing the SenderView in an iframe using the docusign-esign node package. I’ve set a returnUrl, however upon clicking Send in the iframe, it just redirects the user to the Sent list page instead of the returnUrl. As a result, we are unable to get any trigger or indication that the sending is complete and we don’t know when to close the iframe. Is this a known limitation? Are there any fixes or workarounds?

Hi, I am generating a document in Google Docs where I add variables like {{NAME}}, {{EMAIL}}, etc. Then I export that file (PDF) and send it using the DocuSign API.The envelope sends successfully, but the variables are not getting replaced by the values I pass in the API. The final document still shows {{NAME}} instead of the actual name.I am confused: Is Google Docs the correct place to create documents with variables for DocuSign? Does DocuSign support the {{NAME}} syntax, or does it require special tags? What is the correct way to insert fields (merge fields / tabs) so that the values I send in the API appear inside the document? Below is what I want: Create document with placeholders Send envelope through API Fill placeholders with values programmatically  

Hello, I’m using the DocuSign eSignature API to create an envelope draft from a template that uses DocGen and contains a dynamic table. After creating the draft and adding rows to the table programmatically, I attempt to add signature tabs anchored to text placeholders inside the table.The sequence of operations is:Create a draft envelope from a DocuSign template using the Envelopes API (POST /v2.1/accounts/{accountId}/envelopes). Add dynamic table rows via DocGen Form Fields API (PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId}/docGenFormFields). Wait for DocGen rendering to complete. Add signature tabs via Create Recipient Tabs (POST /v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/tabs) using SignHere tabs with AnchorString values matching the placeholders inside the table.The envelope and recipients are created correctly, and the table rows appear as expected. However, the sig

Hello, I’m currently trying to understand the eSignature API (I’m new to docusign). Our UseCase is to create a template for a document we want to send out to customers for signature This template should contain “variables” that needs to be pre-filled before sending out to the signee (e. g. a Customer ID or Name) Sending should work via API.I created a template with several variables (I just put random variables for testing inside, they do not make sense) Within my API Call I am able to send out an envelope with the help of a template by { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email":

I have a number tab called Employee Number.  How do I update this tab using esign API in C# before I send the email?This is my existing MakeEnvelope where I am attempting to do it:         public static EnvelopeDefinition MakeEnvelope(            string signerEmail,            string signerName,            string ccEmail,            string ccName,            string templateId)        {            // Data for this method            // signerEmail            // signerName            // ccEmail            // ccName            // templateId            EnvelopeDefinition env = new EnvelopeDefinition();            env.TemplateId = templateId;                        //env.AllowMarkup = "false";            //env.EnforceSignerVisibility = "true";            //env.RecipientViewRequest            Number employeeNumber = new Number            {

Hello - I have a custom integration that scans the Sent folder of a processor’s account for a completed document and moves it to another custom folder.If I click the custom folder, it shows the folder ID in the URL: https://apps.docusign.com/send/documents?folder={folderID}.  However for the Sent folder, it only shows https://apps.docusign.com/send/documents?view=sentYears ago the URL showed as it does with the custom folder with the folder ID, but now it now longer does.  How do I find the folder ID of the Sent folder?  I am switching accounts to a new processor

Hi there, I am setting up a docusign sending to some recipients through the developer API. Everything works fine but the emails recipients received show a document that can be edited by the recipients. Why is that? none of the fields I have added are editable. (the same thing happens when I test the signing in the docusign UI, meaning issue is not in my code). Thanks for your help 

Not sure if my last question was posted…As I said before, this is not much information on the JavaScript $.ajax call on the DocuSign REST API.  If there was, not much information on it (or even examples).I’m am trying to use JavaScript (JQuery) $.ajax call using a DocuSign REST API.  Even though I tested out on Postman successfully, it does not work using $.ajax (i.e. https://account-d.docusign.com/oauth/token) including the header information and the requested body (note the ${???} represent a placement of the actual values - just to be safe):                    let tkHeader = {                        'Content-Type': 'application/x-www-for-urlencoded',                        'Accep

Hii have a problem while sending a documents via binary transfer in multipart requests to the endpoint: POST /restapi/v2.1/accounts/{accountId}/envelopes Im receiving the following error:{"errorCode":"NO_DOCUMENT_RECEIVED","message":"The document element did not contain the encoded document, or there is a problem with the encoding. Bytes for document corresponding to documentId 1 not found in request. 'documentId=<x>' possibly missing from Content-Disposition header."} For some context, im sending the request from an SAP-System, and im limited to the http_interface that the system provides. I dont have full control over how the request is generated in the end and that is the problem i think:See → The content-disposition header of the added pdf-file is in lower case, while the tuturial (

After authorizing through the authorization url, how should the code passed in when docusign initiates a callback be used? I haven't found a clear definition of "code" 

We have been successfully using the API end-point since around March 2024 with a custom built plugin in WordPress Gravity Forms on our USA server. The custom plugin uses the composer package docusign/esign-client ^6.10 behind the scenes. In mid august we migrated our setup to new server in the EU. Since migrating to a fully patched ubuntu 24.04 server (no java or log4j), using a LAMP stack, all of our API calls get HTTP 444 with the vague error message “The custom error module does not recognize this error.”If we run “curl -v  https://na4.docusign.net/restapi”  on the cli from the new server we receive this response: < HTTP/1.1 444 < Content-Type: text/html< Vary: Origin< X-Content-Type-Options: nosniff< X-DocuSign-TraceToken: c247ca85-1505-4838-9d76-693daec3245d

I need to send an envelope that is made from multiple server templates (compositeTemplates). There is a fixed set of signers (4) across the business process — each signer should only sign the templates that are assigned to them (not every signer signing every template).My goals are: Avoid repeating signer details (name/email/custom emailNotification) inside every composite template so the request JSON stays small and non-redundant. Reuse “global” signer definitions (by recipientId / recipientIdGuid) and reference those signer IDs wherever a template role needs that person. Achieve faster envelope creation / better API performance by reducing payload size and duplication. When I try to use global signers and reference their recipientId (or recipientIdGuid) from inlineTemplates, DocuSign rejects

Hi.In the documentation, I was able to find a complete list of statuses with which a user’s work with the Recipient View can end (and which is subsequently passed as a query parameter to the specified RedirectUrl):https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createrecipient/At the same time, I can’t find similar information anywhere for the Sender View:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createse

Hi, I am developing an interface from SAP C4C (Sales Cloud) which brings in Sales quote data for e-signature. There is a standard connector available in Integration suite for authenticating and perform function calls to Docusign. Can someone help me with what function/API to call and if there is a sequence of APIs I need to call for this requirement

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":

Hi all,I’m trying to add a new recipient to an existing envelope after it has already been created.I’m using the following endpoint:/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}?advanced_update=true&resend_envelope=true(from the Docusign Documentation)It works fine for all recipients, except for the one I’m trying to add after the envelope was created.When I try with this new recipient, I get this error response:"UNSPECIFIED_ERROR"Object reference is not set to an instance of an object I’ve tried multiple approaches and endpoints, but none of them worked.Here’s one of the request bodies I’ve used:{ "recipients": { "signers": [], "agents": [],

 Hello,I want to configure the settings for my organisation. I am an Admin and can edit all settings except the recipient Roles. Why?I need it for a third party Application to work. Am I missing something here? Why cant I set the checkmark on “Enable allow to edit recipient”?  

I am trying to automatically send docx documents for signature to Docusign using only google apps scripts. I went through all the steps to convert the docusign RSA private key from pkcs1 to pkcs8 and then paste the pkcs8 key into the apps script project properties, but i am still running into this error on the code line const signature = Utilities.computeRsaSha256Signature(signatureInput, keyBytes); I also tried an alternative with uploading the pkcs8 .pem file to drive and using the file ID as one of the project properties, but that didn’t work either, the cleaned key in the debugger is showing up like this (screenshot). I used the texteditor on macbook (with make plain text formatting utf-8 option) to create the .pem  files, the openssl terminal command to convert from pkcs1 to pkcs8 and the cat command to get the pkcs8 key after conversion.

So I have to make an envelop using a combination of documents:First is a lets say 10 page flattened pdf from our document management system that need to be in the envelop (in this document no signature or client input is required), then,it is followed by another document that is from the same system and this I am overlaying with a server template.Issue: When the envelop is created, the server template fields are overlaying on the first document and not the second where it is supposed to.I am using the following Json: {    "allowMarkup": "false",    "brandId": "86aee07f-0f86-4c26-xxxxx",    "compositeTemplates": [        {            "compositeTemplateId": "1",            "document": {                "documentId": "1",                "fileExtension": "pdf",                "name": "forms.bound_pages",                "transformPdfFields": "false"            },

We’re building an integration where envelopes are created via the DocuSign API (through Make.com). The goal is to customise the Completed confirmation emails (subject and body).I reached out to DocuSign Support, but I’ve been bounced around and still don’t have a clear answer. So I’m putting this out here:🔹 Which plan level unlocks the Branding feature so we can create and reference brandId values?🔹 Once branding is enabled, can we use:PUT /restapi/v2.1/accounts/{accountId}/brands/{brandId}/resources/emailwith a custom XML resource file (including <completedSubject> and <completedBody>) to fully customise those confirmation emails?🔹 Can HTML and placeholders (like signer name or envelope ID) be used inside those tags?🔹 If we specify {brandId} when sending envelope

Set the ExpireEnabled, ExpireAfter and ExpireDateTime using Docusign SDK 8 for C# and its not taking the values. Key points :Using Docusing SDK 8 with C# Using developer accountI’m creating the envelope from a template.I changed the expiration days in docuSign settingsThese are the lines of code :   // Get the envelope definition after configuration var envelopeDefinition = config.GetEnvelopeDefinition(); // Set the envelope status to "sent". The signer will get an email from DocuSign envelopeDefinition.Status = "sent"; // Set expiration date envelopeDefinition.ExpireEnabled = "true"; // Enable expiration envelopeDefinition.ExpireDateTime = DateTimeOffset.UtcNow.AddDays(14).ToString(); envel

I am encountering the following error when attempting to send a document using a static variable in my integration with DocuSign:The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying documents for Envelope ID = 95d29fa2-762b-49c6-a162-44ce4d16cd23Context:I am using a static variable to pass the document to the envelope. The envelope creation process seems to fail because it does not recognize the document as attached. Recipients and subject line are already set, but the error persists.Question:How can I ensure that the document is properly included in the envelope when using a static variable? Are there any specific steps or API parameters required to validate the envelope before sending?Any guidance or best practices would be greatly appreciated.

Hello there,I got stuck when I am trying to integrate docusign-esign node module in my spfx webpart.I’ve created a new spfx webpart I’ve installed docusign-esign module in the working directory. (My webpart package.json has the following entry…   "docusign-esign": "^8.5.0Error When I gulp serve - I am getting the following , one of so many.: 'dist':./node_modules/docusign-esign/src/index.js: Module not found: Error: Can't resolve 'ApiClient' in 'C:\Phani\Custom Development\PembinaApprovalsDashboard\PembinaApprovalsDashboard\node_modules\docusign-esign\src'Did you mean './ApiClient'? On init of my webpart, I’ve the following code.try      {        let dsApiClient = new docusign.ApiClient();        dsApiClient.setOAuthBasePath(this.DOCUSIGN_OA

Hi everyone,We’re experiencing an issue with the embedded signing flow that recently started occurring (it was working fine until last week).We’re following the official guide for creating a focused signing view:👉 https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/Our backend uses docusign-esign@^8.5.0 to generate the signing URL.We include the following domains in our FRAME_ANCESTORS directive:https://our-domain.com https://demo.docusign.net https://apps-d.docusign.com The generated signing URL opens correctly in a separate browser tab.However, when embedding it inside an <iframe>, the frame fails to load and the browser