Developer

Hi everyone, Via our DocuSign integration/ API, using recipients[].signers[].emailNotification.emailBody, we would like to customize the email message sent to each signer on a per-envelope basis as follows: - Embed protected images in that email message using CID (Content-ID). Is this approach supported by the DocuSign API? If not, we would greatly appreciate any suggestions or recommended approaches to achieve this functionality.Thanks!

Hi Team,We have a requirement where, based on a field update in Salesforce, we need to automatically void a DocuSign contract that has already been sent to the customer.I am new to DocuSign development and need guidance on the following:How to create a DocuSign Developer Account How to use DocuSign APIs to void an envelope that is already sent Best approach to integrate Salesforce with DocuSign so that, when a Salesforce field value changes, the related DocuSign envelope is automatically voided Any recommended best practices or sample implementations for this use caseIf anyone has experience with DocuSign + Salesforce integration or has implemented a similar scenario, your help or pointers would be greatly appreciated.Thanks in advance!

Hi,I have a working DocuSign integration in the demo environment using JWT authentication and templates.When trying to move to production, I get the error:"These accounts don't support API integrations".I have already contacted sales multiple times but received no response.We are ready to go live and need API access enabled for our production account.What is the fastest way to enable this?Thanks in advance.

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

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

Hello everyone,I am currently integrating the DocuSign API for a client project and would like some guidance on the correct process to move from the developer demo environment to production.Here is what I have done so far.Step 1 – Create developer accountI created a developer account using my email: abc@gmail.com.Inside the developer dashboard I created an application and generated the required credentials:• Integration Key (Client ID)• Account ID• API base URL• RSA private key for JWT authenticationI have already tested the integration in the demo environment and API calls are working correctly.Step 2 – Purchase Developer Starter planNext I plan to purchase the Developer Starter plan from the DocuSign plans page:https://ecom.docusign.com/plans-and-pricing/developerThe p

Hi,I need help to figure out how to automate the process of uploading all completed envelopes (pdfs) into Google drive as soon as they are completed? So as I understand first step(start) of the workflow will be Event -  Completed envelope. Btw, I don’t need all the envelopes, just from certain templates. Would appreciate any tips on thatThank you

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?

Every time I try to log in at: https://support.docusign.com/s/contactSupport?language=en_US, I end up encountering the same error. How can I fix this?  

It looks like the new SP cert has a different key from the 2026’s. - The pub keys(modulus) are different.2028 Docusign SSO Self-Signed CertificateOur IDP (Oracle IDCS) doesn’t allow to import multiple signing certs for an SP. It would have been transparent if the cert was renewed with the same key but it doesn’t seem the case. I’m thinking that I might as well tell the business team that we need to react after DocuSign has started using the 2028 cert,  but it’d be great if I’ve missed something and anyone can suggest a way to make the transition without an interruption.

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.

Hi there,We have an application configured with Public Authorization Code Grant using PKCE and so far the development integration is working fine. However, once the integration key was promoted to production and the configuration options for the key were set up (redirect uris and cors origin urls), we see the following error on the browser console when doing the “/oauth/token” call:Access to XMLHttpRequest at 'https://account.docusign.com/oauth/token' from origin 'https://<my_app_origin> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.The call itself returns a 400 error with an empty response.The setup of our production Integration key is exactly the same as the key in the development environment, with one exception: in the Docusign production account we don’t see the option “Allow CORS for OAuth calls”.We have tested that when using the Do

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?

Hi everyone,I would like to report the following issue encountered in developers.docusign.com. Issue Description: Log in to DocuSign Demo Navigate to My Apps & Keys web page That page loads but remains completely blank (no content displayed).  After this occurs: Log out Click on login again. The login form does not appear, and the system automatically logs the user in without re-entering email address and password. Could you please investigate this issue and advise on how it can be resolved?Thanks! 

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,I'm using the C# Quickstart project for embedded signing with the focused view, and I'm running into an issue when using agent recipients.Goal:The sessionEnd event should trigger when the agent completes their part of the signing session.What's Working: Embedded signing is working for both agent and signer. The ready event is triggered properly. The sessionEnd event does trigger correctly for signer recipients. Issue:The issue occurs only for agent recipients. After clicking the Done button on the completion popup, the iframe shows an error message. At this point, the sessionEnd event is not fired.This behavior happens consistently when the embedded recipient is an agent. Signer re

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?