eSignature API

Hello,>Working with the C# SDK<Using composite templates, i successfully created an envelope with 4 documents and 4 recipients (yay !)Document #2 is defined as display=”inline” and i added some tabs (SignHere, Text, DateSigned...) for recipient #1 and recipient #4 : works like a charm. Now my problem is with document #1, which is a supplemental document (display=”modal”). The goal is to set this document as “View and accept” only for recipient #4. Following the documentation I created a View tab and an Approve tab like this :Approve approveTab = new Approve() { DocumentId = "1", RecipientId = "4" };View viewTab = new View() { DocumentId = "1", RecipientId = "4", RequiredRead = "false", Required = "true", PageNumber = "1" };

I want to send multiple PDFs in a single envelope with defined signature positions. I need the signer to be able to sign at least one document and complete the signing process, while keeping the envelope active so they can return later to sign the remaining documents. Additionally, I want to receive a callback (webhook) each time the user signs a document. Is this possible using DocuSign, or should I send each PDF in separate envelopes?

Is it possible to send an envelope using the eSignature API and set up an automatic signature for a recipient, so that no human action is required from that recipient?

Hi everyone,I’m currently using the DocuSign eSignature API to create an envelope via Composite Templates. My setup involves two recipients with no signing order (parallel routing).To ensure tabs are visible to both parties, I have set the shared property to true for each tab within the inlineTemplates for the signers.The Problem: When the signing URL is opened, the shared tabs are appearing with a solid white background. I was expecting them to be transparent so they blend seamlessly with the document's underlying layout.My Questions: Is there a specific property I need to adjust / include to force transparency for shared tabs? Has anyone found a workaround to fix this? Any insights from the community would be helpful!Thank you,Quoc

I am using Java for my development. Is there a way to allow the signer to choose where to place their signature? I tried leaving out the tabs field within the signer, but in that case it considers the signature as not required, or it even allows the user to "bypass" it by filling in other fields (company, date, etc.).In my case, I would like to keep only the signature option active (the person's name), and also ensure that the process is only actually completed once the signature has been provided.

We have users who have collected large numbers of envelopes and they are interested in that legacy form data. Can an admin account be set up via API to pull that existing form data and write data labels and collected data content into a file?  Or would the sending account have to be set up as the API user who pulls this data? It seems like the admin account should be able to, since it can be set to see into any account and manually pull form data from each envelope. Going forward, I see Agreement Actions could be useful for *future* data. https://support.docusign.com/s/document-item?language=en_US&bundleId=pik1583277475390&topicId=tkx1648575795345.html&_LANG=enusThis question pertains to *existing* da

I got this issue when trying to get access token. So I don’t know how to get code challenge and its method. I tried to search around them but nothing is suitable for my issue. It also tell me bout CODE_VERIFIER, and I’m stucking with how to get these values and solve my problem. Can anyone help me to resolve this issue?https://{{hostenv}}/oauth/token{ "error": "invalid_request", "error_description": "code challenge and code challenge method required"} 

We have built a Salesforce automation. When the initial contract is sent to the client and later some changes are made, we generate a second contract.At the time of generating the second contract, we update the initial contract envelope status to Void. However, we are not receiving any void notification emails. Also, we are still receiving reminder emails for the initial contract.I think the API call is not being triggered in DocuSign.Can someone advise me on how to resolve this issue?

I recently added version 6.0.0, and when trying to implement the envelope creation, the class EnvelopeHelpers cannot be found. <dependency> <groupId>com.docusign</groupId> <artifactId>docusign-esign-java</artifactId> <version>6.0.0</version></dependency>

We have org admin permissions but we are unable to create user with status as ‘Active’ using this POST request https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/users

Hi all,I’m stuck with a DocuSign JWT Grant issue and would appreciate help from anyone who has seen this before.ProblemCalling the token endpoint consistently returns:{ "error": "invalid_grant", "error_description": "user_not_found"}Token RequestPOST https://account-d.docusign.com/oauth/tokenContent-Type: application/x-www-form-urlencodedgrant_type=urn:ietf:params:oauth:grant-type:jwt-bearerassertion=<signed_jwt>JWT Details alg: RS256 iss (Integration Key):0a09f94b-xxxx-xxxx-xxxx-722da7e2846a sub (User ID):3af994a5-xxxx-xxxx-xxxx-adf23dce0cd3 aud: account-d.docusign.com scope

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

Hello, Does DocuSign have any API connections built that could work with ADP?

Is it possible in Docusign to create a way where, when creating an envelope, a link is also generated for it so that I can send this link to someone to sign? In this case, the envelope itself would not have a predefined recipient; instead, the recipient would be whoever has access to the link. If so, how can I implement this? Is there any documentation I can follow?

Hi,I'm creating envelopes from a template using the REST API. The envelope is created successfully but all text field values remain empty.Setup:- Production account- POST /v2.1/accounts/{accountId}/envelopes- Text fields placed under Company Rep recipient- Tab labels are auto-generated UUIDsThings I already tried:- Sending tab values in templateRoles in the POST request- PUT request to update tabs after creation using tabLabel and tabId- Enabled "write initial value of fields for all recipients" settingAll attempts result in a correct draft but with empty fields.What is the correct way to pre-fill text tab values from a template via API?Thank you.

Hi Everyone,I have a question regarding “the Azure migration of demo accounts.”How can I check whether our demo account has already been migrated to the Azure environment?Also, do DocuSign send us any notfification once the migration is completed (for example via email or developer portal)?Thanks in advance for any insights.

Everything was working yesterday, but today when I go into my Docusign Developer account and attempt to access My Apps & Keys I see a message in the console of my browser saying ‘Uncaught ReferenceError: process is not defined’ and nothing loads in the page.  Using Dev tools in Edge this is the line that is causing the issue:t.dsUiPlatformProps = "1DS" === process.env.MODE ? System.import("@1ds/platform-for-libs", n.p) : new r.default( () => {}My best guess is that some code meant for the server using Node has leaked into the code getting run client side in a release made today or last night.  Does that sound right?  Could this be caused by anything else?  Could I (company policy) be blocking a related script?

Hi, I’m still in sandbox.My use case is we send the envelope to a signer. After they complete signing, we need to fill other fields for the second signer before they view the document. I’ve implemented sending the the envelope to the first signer with pre-populated fields. But after the first signer completes and I update the fields for the second signer, the second signer still sees those fields as empty.I’ve tried both envelopesApi.updateRecipients()andenvelopesApi.updateTabs()Neither of those made the fields pre-populate when the second signer loaded up the doc.Is this possible to implement? How should I go about it?

I am in the admin - > integration section.  I was expecting to see something liek API and keys in the title  . I did try the app and keys, but the only option is Authorization Code Grant. I don;’ see an way to change it,   Figure 2.   What am I missing?Figure 1Figure 2  

Hi, We have developed an integration with the DocuSign REST APIs.Over the past few weeks, we’ve observed that a few POST /envelopes requests have taken longer than usual to respond, resulting in timeouts in our system. However, these requests eventually complete successfully on the DocuSign side.To better calibrate our timeout configuration and avoid failures, we would like to better understand the expected performance characteristics of the POST /envelopes API.We would appreciate it if you could share the p99 response time metrics for the POST /envelopes API, as this will help us appropriately tune our timeout settings.TIA

Hi everyone,I’m building a Make.com scenario to create a DocuSign envelope from a template and automatically prefill fields in the document.What works: The envelope gets created successfully (status: created) The recipient (“Kunde”) is set correctly (name + email are correct) What doesn’t work: None of the DocuSign fields get prefilled (even a static test value like "Test123" doesn’t show up) This is the JSON body I send in Make (DocuSign “Make an API Call”):{ "status": "created", "templateId": "XXX", "templateRoles": [ { "roleName": "Kunde", "name": "{{4.Accountname[1]}}", "email": "{{7.ContactEmail}}" } ], "recipients": { "prefillTabs": { "textTabs": [ { "tabLabel": "vorname_nachname", "value": "T

Hello,I am developing an integration on my Demo Account (Sandbox) and I am receiving the error "ACCOUNT_LACKS_PERMISSIONS" when testing the WhatsApp/SMS delivery feature.Could you please enable "Phone Authentication" and "WhatsApp Delivery" for my account?API Account ID: ( redacted )Thank you.

Created App and Key with Redirect URI and RSA Key Pair. Sent request in format https://account-d.docusign.com/oauth/auth?    response_type=code    &scope=YOUR_REQUESTED_SCOPES    &client_id=YOUR_INTEGRATION_KEY    &redirect_uri=YOUR_REDIRECT_URI. Replacing with my value. Code returned is of typ:MT and Payload is not JSON format. Instead it is in binary format

Hello,I’m experiencing an issue with the option “Use the sender’s company name.”When I enable this checkbox, I expect the sender name shown to recipients to switch to the brand/company name. However, even after checking the option, the sender name does not change and still appears as the individual sender rather than the brand.Am I misunderstanding the purpose of this setting? Could you clarify what this option is supposed to do, and under which conditions it affects the sender name?Thank you in advance for your help.

  Hello DocuSign Community,  We are hitting the ENVELOPE_ALLOWANCE_EXCEEDED error on our Developer Demo account, and the error occurs both via the REST API AND the web interface. This rules out the "API has separate limits from web" explanation mentioned in previous threads.  Environment:  - Account type: Developer Demo (sandbox)  - Authorization server: account-d.docusign.com  - API base path: demo.docusign.net/restapi  - Integration method: REST API via official PHP SDK (docusign/esign-client v8.6)  - Error code: ENVELOPE_ALLOWANCE_EXCEEDED  - Error message: "The envelope allowance for the account has been exceeded"  Critical detail:  The same error appears when trying to send envelopes through:  - ✗ REST API calls  - ✗ Web interface (appdemo.docusign.com)  This suggests either a system-wide bug or an account-level issue, not an API-specific quota.  Su