eSignature API

Hi, i am currently in the developer phase, I was testing if multiple routing order can be done. Made a request with the following api{{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesand with body{  "documents": [    {      "documentBase64": {{document}},      "documentId": {{documentId}},      "fileExtension": "pdf",      "name": "document"    }  ],  "emailSubject": "Multiple Signing Example from api testing",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "1",        "routingOrder": "1"      },      {        "email": {{user2_email}},        "name": {{user2_name}},        "recipientId": "2",        "routingOrder": "2"      }    ]  },  "status": "sent"} The first order signer gets mail, after signing it shows that invitation was sent to 2nd signer but the 2nd signer did not get any mail in the inbox. After i forced “Resend” in the developer console, It sent the mail. What could be the issue?There is

We are encountering DocuSign issues while retrieving the status of packages in the development and test environments. ( Note - This issue is NOT happing in production environment ) The core issue is a `com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException` within the `cwaDocusignApi.war` application. This exception arises when the application attempts to deserialize a JSON response from the DocuSign API, as the response contains a field named "isTicketRelatedEnvelope" that is not recognized by the application's `com.docusign.esign.model.Envelope` class. The root causes appear to be:1. **Outdated DocuSign SDK:** The `cwaDocusignApi` application uses an older version of the DocuSign eSignature SDK, which does not include the `isTicketRelatedEnvelope` property in its `Envelope` model.2. **API Changes:** DocuSign has updated its API to include this new field, and our application has not been updated to accommodate it. To isolate the issue, the existing code was deployed in a loc

We’re planning the November Developer AMA and want your input. Vote for the topic you’d like us to feature. Then we’ll line up a Docusign expert to lead the discussion. This round of topic options is all about building, customizing, and automating with Docusign so you can spend less time troubleshooting and more time creating.

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’m using the Signature API example.  When the user opens the email, rather than being able to sign, the document is getting opened for editing instead of for signing. string envelopeTest = CreateEnvelopeFromTemplate.SendEnvelopeFromTemplate("scottftrick@gmail.com", "Scott Trick","strick@michels.us","Scott Trick", accessToken.access_token, acct.BaseUri + "/restapi", acct.AccountId, "9d0acb57-30c5-414f-a4fe-1d72e8bfca66");         public static string SendEnvelopeFromTemplate(string signerEmail, string signerName, string ccEmail, string ccName, string accessToken, string basePath, string accountId, string templateId)        {            //ds-snippet-start:eSign9Step3            var docuSignClient = new DocuSignClient(basePath);            docuSignClient.Configuration.DefaultHeader.Add("Authorization", "Bearer " + accessToken);                       EnvelopesApi envelopesApi = new EnvelopesApi(docuSignClient);            EnvelopeDefinition envelope = MakeEnvelope(signerEmail, signerName,

I need to implement e-signature functionality on my client’s website. We are generating a PDF, and I already have the signature image of the authorized person. I would like to apply this e-signature to the PDF document, but I do not want to perform verification every time. Could you please suggest which APIs or Steps would be suitable for this requirement?

I am following this guide:https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-template-remote/ I have a template in my dev environment that contains all the fields for the user to enter and sign.When I use the guide above and send the template to the user, rather than the signing fields they are getting the document and need to add fields to the document.  How do I change this to be the actual document where they fill in the fields and sign, that is setup with the template? Thank you!

We build signing envelope via API. We often have multiple signers in our envelope and are currently signing sequentially. We use the TextTabs to put read-only text on the document. And, we are putting those tabs on the lowest order recipient. The tabs, in this case, have a transparent background and overlay nicely on-top of the document. Lately, I was asked to parallelize the signing process (i.e. send the document to multiple recipients at the same time). We tried a few things to make this work: Copy the tabs to all recipient. This caused issues since we were exceeding the Maximum number of tabs in an envelope (we have a lot of documents in our envelope). So, this option was not acceptable.  Use the shared option on the tabs. When using shared, all recipients would see a white background on the tab. Even if required and locked were set to ‘true’.  Use the global option “When an envelope is sent, write the initial value of the field for all recipients”. This was working pretty well for

i want to use DocuSign Api Service to send document for digital Signature but the problem is that i want sign box in specified row of document so i want to change the width accordingly but their is only one option which is scaleValue so is there any option or api with any payload by which i can fix the height and width as per my require ment

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

I Can’t find any way to set prefill tabs datathru all posts it looked like I should do it this way, but it doesn't work let results = await envelopesApi.createEnvelope(accountId, {            envelopeDefinition: {                templateId: 'xxxxxxxxxxxxxxxxx',                templateRoles: [                    {                        email: 'reciepient@gmail.com',                        name: 'john doe',                        roleName: 'client'                    },                ],                tabs: {                    prefillTabs: {                        textTabs: [                            {                                tabLabel: 'name',                                value: 'Jabberwocky!',                            },                            {                                tabLabel: "text",                                value: 'lorem ipsum'                            }                        ]                    }                },                status: 'sent' 

Is the eSignature API fully functional on the Personal and Standard plans?For example, if I have a custom PDF that is generated from my own website (automatically filled with the user data), can I use that same PDF to create an envelope on the fly?I can’t find out where I can see what API features are allowed in Personal / Standard / Business / Enterprise. Or can I assume that all features are available in all of these unless specified in the docs? Thanks!

I tried to create the Prefill tab using a POST call, but it threw an error message in Postman. I’m using the Business Pro plan on my account. Below is the request body I used for the API call. Request body:{    "tabs":    {    "prefillTabs": {      "textTabs": [        {          "validationPattern": "",          "xPosition": "124",          "tabId": "4d21df0f-7324-421d-xxxx-07142a62a055",          "shared": "false",          "templateLocked": "false",          "tabLabel": "Text 50eeec15-xxx-4fe3-b950-9f9f6baf1d7d",          "pageNumber": "1",          "underline": "false",          "yPosition": "182",          "requireAll": "false",          "tooltip": "prefiltab",          "tabType": "prefilltab",          "italic": "false",          "required": "false",          "templateRequired": "false",          "locked": "false",          "value": "oooo",          "height": "41",          "disableAutoSize": "false",          "validationMessage": "",          "originalValue": "oooo",          "a

We deployed Docusign embedded signing and embedded CoC download into our own system. We have configured the Japan timezone in Settings > Regional Setting.But we are always got CoC timestamps in UTC timezone. Is it possible to change that into Tokyo Timezone? How can we do it? In addition, can we change language of "Electronic Record and Signature Disclosure" into Japanese in CoC?Looking forward to your guidance. Thank you

Hello there.I need help with implementing the eSignature API. I have a simple Word document with variables - {{contractor_name}}, {{contractor_email}}. How can I use the API to update this document and populate real data instead of {{contractor_name}} and send it to the recipient?- I tried to use textTabs and send all the necessary data in one request, including a Word document in Base64 - the fields didn't populate.- I tried to manually create a template using the web UI, upload a Word document, manually add sender fields, and then made a request to update these custom fields (docGenFormFields). Nothing. ChatGPT assumed that docGenFormFields wasn't turned on in my account. But how to turn it on, I have no idea.I'm using the developer sandbox account. Can anybody point me to how to implement field population via API?I've used:Document generation manual - https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/documents/document-generation/Prefilled tabs - https://develope

Hi — I’m not a U.S. citizen. How can I register and sign the DocuSign document from abroad?Also, our company’s authorized officer will sign the document. Do you require any corporate documents (e.g., board resolution, power of attorney) or notarization for the corporate signature

I am embedding Docusign in my application and at the same time i would like share the document links to sign from my application.I have already integrated in my application. And when I am using the embedded link in mail. The link expires in 5 mins or else the link is returning to return url once the signing is complete but once the signing is complete it should close the tab and then return to return urlThe link is open from the mail then how can i close?

After working for some time with Docusign's API I thought it would be a good idea to look into the API's 'Connect' feature (https://developers.docusign.com/docs/esign-rest-api/reference/connect/).This allows the sending of information to an application via webhooks when an event occurs for the envelope in question.Currently the only webhook listeners I have available are with Microsoft Teams and Mattermost. I have created the webhook listener in both and can send information to them using the following command: curl -H 'Content-Type:application/json' -d '{"text":"Test text 1"}' <endpoint>where `<endpoint>` is the URL of the webhook listener in either Teams or Mattermost.Next I have tried to send information from an existing Docusign envelope to Teams/Mattermost using the following perl code: use strict;use warnings;use LWP::UserAgentuse HTTP::Request::Common;use JSON;my $EnvelopeID='"92f294ba-a5a0-4a4d-ac85-f08ad5b6a09a"';my $webhookURL=q{https://site.webhook.office.com/web

I’ve placed the anchor tags for my document in a 3 column table.  The first cell has anchor tag \c1\ for recording a Text Tab value for signer’s company, the second cell has anchor tag \n1\ for recording the signer’s full name, and the last cell has anchor tag \s1\ for recording the signature.The problem is that the displayed value for the anchor tags are not wrapping within the cells of the table.  So if the company names or signer’s names are long, they run into the values of the other cells causing the text to overlap.  Is there a way to force the injected text to wrap in the cell and respect the layout where the anchor tag is defined? I’ve tried to specify the “width” property to 100 and “anchorUnits” property to “pixels” (also tried “inches”), but it doesn’t seem to affect anything:"recipients": {    …    "signers": [      {       ...        “Name”: “Sample Name”        "tabs": {          "signHereTabs": [            {              "anchorString": "\s1\",              "anchorUnits

Hello,I am attempting to implement JWT Grant authentication for my DocuSign integration in a developer account (demo.docusign.net). I consistently receive the following error when making API calls (e.g., oauth/token endpoint):"Authenticatie mislukt (400): no_valid_keys_or_signatures"This translates to no_valid_keys_or_signatures.Here's what I've done so far:I have created an RSA Keypair within my DocuSign developer account for my Integration Key. I am using the Private Key from this newly generated keypair. I have confirmed that it's copied completely, including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- headers/footers, and that there are no extra spaces or missing line breaks. I have correctly set my CLIENT_ID (Integration Key), USER_ID (API Username), ACCOUNT_ID, and DOCUSIGN_BASE_PATH (https://demo.docusign.net) in my application's environment variables. I have performed the required user consent grant by navigating to the consent URL (https://account-d.d

Hi, I am using the C# eSign SDK and am trying to allow users to open a sender view for envelopes that they are not the sender on, but have been granted shared access to. i.e. User A creates a draft envelope and User B opens the sender view for that envelope.The documentation says I need to attach a header ( X-DocuSign-Act-On-Behalf) with the principal user id (User A’s id) as the value in order to act on their behalf.Here’s what I am doing generally in my code (language is Visual Basic). I am using the agent user’s (User B) access token and base uri:DSClient = New DocuSignClient(baseUri & "/restapi")DSClient.Configuration.DefaultHeader.Add("Authorization", "Bearer " & accessToken)DSClient.Configuration.DefaultHeader.Add("X-DocuSign-Act-On-Behalf", principalUserId)...EnvelopesApi.CreateSenderView(accountId, envelopeId) The problem is when I add the header and make the API call, I get an error back:{errorCode: “ACT_ON_BEHALF_USER_NOT_ALLOWED”,errorContent: "An 'Act on Behalf Of'

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My Azure web App Service to supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

Hi DocuSign Community,We’ve developed a system that integrates with DocuSign to access templates and send offer letters directly from our portal. In our setup, users log in to our portal with their DocuSign accounts, and from there they can access their templates and send offers through DocuSign using eSignature API.So far, we’ve been testing successfully using a Sandbox account. To move into production, we understand that we need a Partner Production account. We have already filled out and submitted the required form for this, but we haven’t received any response yet.Has anyone else experienced delays with this process? Is there a recommended way to follow up or escalate the request to get our Partner Production account enabled?Any guidance would be greatly appreciated.Thanks in advance!

We host in-person meetings, and want the attendees of the meeting to sign the meeting document via a tablet that gets passed around.  We don’t know who the attendees/signers will be, or how many, but we want them to sign the document within our web application.  After a lot of experimentation with Docusign’s APIs, we’ve taken this approach:We create an envelope (POST to /restapi/v2/accounts/{accountId}/envelopes) with 100 allocated signers (the maximum allowed and hopefully more than will ever attend our meetings).  These are placeholder signers.  Our document also has 100 lines allocated for recording attendee information which feature anchor tags for recording the signature (\s1\, \s2\, etc.), anchor tags for the attendee’s name (\n1\, \n2\, etc.), and anchor tags for recording the attendee’s company (\c1\, \c2\, etc.)   As each attendee enters their information on the tablet, we call Docusign’s recipient-update API endpoint (PUT to /restapi/v2/accounts/{accountId}/envelopes/{envelop

 Hi DocuSign Community!I'm implementing embedded signing with Focused View/Click to Agree using the eSignature JavaScript SDK. I need to display the embedded document in a dialog/modal within my page.Question: Does Focused View provide any built-in dialog/modal component for displaying the embedded document (similar to Click API), or do I need to implement my own custom UI container where the document will be embedded?I've checked the documentation which covers styling the container div, but I want to confirm if there are any built-in presentation options before building a custom solution.Thanks!