eSignature API

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"            },            "inlineTemplates": [                {                    "recipients": {                        "signers": [           

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 envelopes via the API, will the customised branding email templates apply automatically?🔹 And finally, if branding isn’t applied, is there any other way to override the Completed email subject/body via API?If anyone h

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(); envelopeDefinition.ExpireAfter = "14"; // Set expiration days // Initialize the EnvelopesApi client (reuse existing ApiClient) EnvelopesApi envelopesApi = new(this.ApiClient); // Create the envelope on DocuSign (it will not be sent due to the "created" status) EnvelopeSummary envelopeSummary = envelopesA

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, 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 signature tabs are never added, List Tabs (GET /tabs) shows SignHereTabs = 0, a

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_OAUTH_BASE_PATH);        // Use Buffer.from for DocuSign API compatibility        const privateKeyBuffer = Buffer.from(DOCUSIGN_RSA_PRIVATE_KEY, 'utf8');        const results = await dsApiClient.requestJWTUserToken(          this.DOCUSIGN_INTEGRATION_

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

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 shows a CSP violation error:Content Security Policy of your site blocks some resources Some resources are blocked because their origin is not listed in your site's CSP. ... Resource Status Directive Source location https://apps.dev.docusign.net/.../1ds-bundle.js.map blocked connect-src (unknown) https://apps-d.docusign.com

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< X-DocuSign-Node: SE101FE106< Date: Wed, 08 Oct 2025 17:14:15 GMT< Content-Length: 54< Strict-Transport-Security: max-age=31536000; includeSubDomains< * Connection #0 to host na4.docusign.net left

Is it possible to have the API call limit raised from the default of 3000 per hour ?   Is this based on the plan you have wit Docusign ? Can it be raised for a certain number of hours per day  ? Ex: 5pm to 8pm an then it goes back to defaultWhat is the maximum if it is possible for it to be raised ? Are there other stipulations for raising it ?Do the API limits only impact Docusign Retrieve or all aspects of sending envelopes  etc. ?What is the procedure to have it increased ?   support ticket ?  Thank YouNorman

Hi DocuSign Community,I need some guidance on the correct architectural pattern for checking envelope status without violating API rules. Context: I’m a developer using the docusign eSignature product. I have an envelope that requires signatures from two separate recipients. I need to trigger a specific operation in my application, but after both recipients have successfully signed and the envelope is complete, and when only either one of the recipient has signed the contract.  Problem: My initial thought was to call the GET /envelopes/{envelopeId} endpoint to check the recipients' status every time one of them signs. However, these two signatures could easily happen within minutes of each other. This would mean I'd be making multiple GET calls to the same envelope ID in less than the 15-minute window, which I believe violates the API polling rules. My application is already live, and I want to ensure I remain compliant. I have also read this, where there isn’t a specific guideline or

Request Failed: 400 {"error":{"message":"Model is not supported for this request.","code":"model_not_supported","param":"model","type":"invalid_request_error"}}

Hi All,I know you can embed in-person signing on a document,But is it possible to embed in-person signing on a website (specifically a sharepoint site).We have site created where users have to provide in person consent, they will be in an office, office users will add the signers name and email address(and a second signer if required) and we expect the signers to sign in person.Is this possible?Thanks in advance.

Hi everyone,I’m trying to send an envelope using the DocuSign eSignature REST API from an n8n automation workflow, but I’m getting a 400 - UNPROCESSABLE_ENTITY error when using a template.Here’s the full request body I’m sending:{  "emailSubject": "Please sign this document",  "templateId": "b19401de-25af-426b-addc-c290c0ef0753",  "templateRoles": [    {      "email": "abc@gmail.com",      "name": “Group",      "roleName": "BCBA"    }  ],  "status": "sent",  "eventNotification": {    "url": "",    "loggingEnabled": true,    "requireAcknowledgment": true,    "envelopeEvents": [      {        "envelopeEventStatusCode": "Completed",        "includeDocuments": true      }    ]  }} And here’s the error response:400 - {"errorCode":"UNPROCESSABLE_ENTITY","message":"The entity could not be processed."}Request details: Endpoint: https://demo.docusign.net/restapi/v2.1/accounts/a66ffa71-c12f-4cab-b5ae-854d3c378e3f/envelopes Auth type: OAuth2 (Authorization Code grant) Integration tool: n8n

We are creating 100 pages of forms and calling Docusign API to create an envelope for user to e-sign from our application. User have already reviewed the document in preview state before proceeding with E-sign. Is there option to E-sign all 100 pages in one click rather than user clicking each signature element in each form?  We want to improve the user experience for the client. Thanks.

I am have a usecase where my template is going to be signed by multiple clients. in those templates, I am prefilling different kinds of information (texts, checkboxes, radio buttons and so on). I have a usecase where I need to upload/prefill a logo. this logo will be different in many cases. and I am trying to figure out a way to generate a document with the corresponding logo. is there a way to do this ?

Hello, We’ve noticed that when multiple emails are sent from DocuSign with the same subject line, Gmail automatically groups them into a single conversation thread. This makes it difficult for our recipients to easily identify or track individual signing requests.Could you please let me know if there’s a way to prevent this behavior by adding unique identifiers so that each message is treated as a separate email in Gmail? The envelopes are created via the API from a PHP application, and I’m using the Email Signing Resource file to define the email subject template.  

I need to build one envelope with three composites: a plain PDF with no signers, a server template with roles mapped to recipients, a flat PDF that overrides a server template’s original doc and maps template roles RoleA → Employee (routing 1) and RoleB → Owner (routing 2). ProblemIn composite #3, the tabs/fields from the server template appear on the wrong document (seem to land on the first doc), and the template for the flat PDF looks “ignored.What am I missing or doing wrong that it showing 3 documents as required but adding only last assigned template’s tab and text to complete envelope [i.e. overlaying on first document only ] and ignoring 2nd server template tabs and fields and not adding 3rd template it’s respective 3rd document ???{ "emailSubject": "Combined Envelope Example", "status": "sent", "compositeTemplates": [ { "compositeTemplateId": "1", "document": { "documentId": "1", "name": "Notice.pdf", "fileExtension": "pdf", "doc

Hello,Could you please explain why email subject > 100 caracters are allowed trhougt Docusin_EmailResource customization but not with method RecipientEmailNotification ? 

Hello,I'm developing an application using the eSignature REST API (via the Node.js SDK) and facing an issue with embedded signing. The `signing_complete` event is not being sent from the DocuSign iFrame to my parent application via `postMessage`.Here is my current setup and what I've tried so far:**Workflow:**1.  **Server-Side (Node.js/SvelteKit):**    *   I create an envelope successfully.    *   I call `envelopesApi.createRecipientView()` to generate a `recipientViewUrl` for an embedded signer.    *   Crucially, I am including `frameAncestors` and `messageOrigins` in the `recipientViewRequest` pointing to my local development origin (`http://localhost:5173`).    ```javascript    // Simplified server-side code    const viewRequest = {        returnUrl: `https://example.com/docusign/return`, // A simple fallback page        authenticationMethod: 'none',        email: user.email,        userName: user.name,        clientUserId: user.id,        // @ts-ignore - Types are missing, but API

Hello,We set up a DocuSign app on our client’s dev account, passed the Go-Live check, and published to production. As the next step, a production user opened the consent link and approved it. We can see the app listed under the user’s Connected Apps.However, our OAuth token request to https://account.docusign.com/oauth/token still returns:{"error":"consent_required"}Note: We also have another production account where this flow works as expected—authentication succeeds—so the issue appears to be specific to this production account. I’m out of ideas on what else to verify and would appreciate any tips or guidance. Thank you.

Hello,We setup a Docusign app on dev and followed all the steps mentioned in granting administrative consent for JWT Grant Flow. When we migrated our app to Prod, firstly, we don’t see the Organizations Tab that we see on Docusign dev and I get this error when I am trying to get an access token from Docusign.error 400 while reaching https://account.docusign.com/oauth/token: {"error":"consent_required"}I am not sure how to move forward from here because our setup works on Docusign Dev but doesn’t work after going live.

Hi Team, Today we found docusign iframe was not loaded, it even worked yesterday, no changes applied in our side.When I opened the signing URL  in the browser, which starts with “https://demo.docusign.net/signing/mtredeem/v1”.I cannot find our domain in “content-security-policy” response header, and confirm our domain has been added into the FrameAncestors whie calling CreateRecipientView API. Is their any update for demo site? Thanks,Fei

Hi DocuSign Community!I'm experiencing an issue with displaying base64-encoded images in HTML templates used for embedded signing via the eSignature API.I'm using HTML templates with <img> tags that contain base64-encoded images in the src attribute (using data: URLs). The images display perfectly when viewing the HTML in a standard web browser, but they disappear when the document is embedded using the DocuSignJS SDK for signing.Technical Details:API Used: DocuSign eSignature API with embedded signingSDK: DocuSignJS SDK (https://js.docusign.com/bundle.js)Image Format: Base64-encoded images using data:image/[format];base64,[data] syntaxImplementation: HTML templates with embedded <img> tags Are there any known limitations or specific requirements for displaying base64-encoded images in HTML templates when using embedded signing? Is there an alternative approach I should consider for including images in signable HTML documents?Documentations references:Envelope creationEmbed

I have a strange misalignment of signer records when I am setting up one signer as a host and another signer as an inPersonSigner using API.  The result of a setup is the signerName is used along side of a host email when it is showing “Hosted By” and also in one of the flow dialogs when it is saying that “Name1, pass control of the session to Name1”, where Name1 is the inPersonSigner signerName. I am submitting clientUserId for both host and inperson signer, otherwise I could not match the inPerson signer while generating a RecipientView. I see that it aligns the names correctly if I remove clientUserId from inPersonSigner record, but it breaks the mapping for RecipientView. Is there any possible work around for this?