eSignature API

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',                        'Accept': '*/*',                        'Accept - Encoding': 'gzip,deflate,br',                        'Connection': 'keep-alive',                        'Authorization': `Basic ${basicBase64IntSecKey}`                    }                    let tkRequestBody = {                        'grant_type': 'authorizatio

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 (https://developers.docusign.com/docs/esign-rest-api/how-to/send-binary/) suggets “Content-Disposition” instead.  

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

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 the envelope with an error such as:400: “The envelope is not complete and a  complete envelope requires document recipients, tab and a subject line.”I need to know: What is the correct, suppo

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/createsender/ Please advise where I can find the list or maybe provide the full list itself.Thanks in advance!

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 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": [], "editors": [], "intermediaries": [], "carbonCopies": [], "certifiedDeliveries": [], "inPersonSigners": [], "seals": [], "witnesses": [ { "witnessFor": "1", "name": "teste", "email": "nahh336@gmail.com", "recipientId": "3", "routingOrder": "3", "recipientType

 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"            },            "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 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 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

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.