Developer

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of January 2025. To make sure we see your questions on Stack Overflow, use the tag docusignapi.Thread: Send one carbon copy (CC) in bulk requesthttps://community.docusign.com/esignature-api-63/send-one-carbon-copy-cc-in-bulk-request-22345Summary:  The developer is bulk sending envelopes through the eSignature REST API. Each of the envelopes has a different signer recipient, but they want to add a carbon copy (CC) recipient that will receive a single notification for all of the bulk envelopes. If 20 envelopes are sent, they want the CC recipient to be copied once instead of having the CC recipient receive 20 email notifications.Answer: Unfortunately, what the developer is looking to do is not possible. With bulk sending, each envelope is treated as an independent object, so the CC recipient will be notified for each one independently.Thread: SenderView - Do I create

Does DocuSign API support TLS1.3?

Hi There, We are trying to implement a read-only field in a DocuSign webform that is preset when the form URL is sent from our CRM system. However, when the read-only field is preset from a CRM system, it seems that it can’t be configured as a read-only field. The system throws an error at the beginning of the webform and also after you submit it. When you configure a read-only field that is not getting preset, it is working and the value is getting mapped over to the document as expected upon submitting. I have attached some screenshots below of the errors that are getting triggered when the “CaseID” read-only field is getting preset in the first screen as well as the one at the end.    

Hi there.I have recently promoted an App from the Development Environment to Production. The intention is to replace an existing, live App already there. I do not see an option to ‘disable’ or deactivate the current live App. Any suggestions on this ?ThanksCB

Hello! The legal entity of my company asked me if we can enable the possibility for the end-user to download the Electronic and signature disclosure (what we see in the screenshot).I did not find something like this in the settings.Does someone know if it is possible?Thanks! 

Hi everyone,We’ve encountered an issue with our DocuSign integration and are hoping someone can share their experience.Here’s the situation:We send documents to a DocuSign envelope and specify the documentId for each document in our API request. The API responds with the same documentId values we set. However, when we view the envelope in the DocuSign UI, the documentId appears to have been reset or renumbered (e.g., starting at 1).Has anyone else faced this issue or something similar? If so, how did you handle it?Thanks in advance for any insights!

Hi everyone,I have a question about integration keys in the developer account.If you create an integration key in a free developer account, you need to promote it to production using your production account to move it to production.What about a paid developer account? Do integration keys created in a paid developer account still require promotion to production, or are they promoted to production by default?

Hi! I just published a new YouTube video on how to automate workflows using Docusign agreement rules.You’ll learn how to:Automatically store signed PDFs in Google Drive, OneDrive, or SharePoint. Export recipient-entered data from Docusign forms into spreadsheets. Automatically send follow-up envelopes to the same recipients when a previous envelope is signed.Master seamless integrations to save time and reduce errors in your document processes. You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hello! I have got a Go Live status: Review failed (See OAuth 2.0 migration options).After reading the doc I do not understand what we are doing wrong.Here are the 2 types of calls I do:/oauth/token/clickapi/v1/accounts/{accountId}/clickwraps/{clickWrapId}/agreementsWe have chosen JWT grant authentication.Can you help me understand what is wrong?Thanks a lot!

When using eSign API/SDK, can we somehow enable the option to attach the template PDF of the template/document to be signed via the developer console? If yes, then how?I know that after completing the signing process, the signer receives an email that contains the signed template. But in my case, I want to include the unsigned doc/template as an attachment in the sign request email sent to the signer!!

Hi, Anyone have any thoughts for ways or workarounds to only allow DocuSign to update Salesforce once an envelope is completed?We are using DocuSign Apps Launcher with Salesforce and using DocuSign envelope templates. The document first goes to recipient 1 who is required to make edits to the doc and sign it. Next it goes to an ‘Approver’ who has the option to approve or reject the document Once the Approver approves the doc, the envelope is considered completed and that is what appears in Salesforce. However, we don’t want Salesforce to be updated until the document is completed in case the first recipient had errors in the doc and now they need to be corrected? Any insights would be greatly appreciated!

Hey everyone, hoping yall doing well!I’m trying to Go-Live but have not succed in these past hours. At the moment my app passed review and its saying “Promote to production” with a green circle on the side.So these are my steps while trying to get on production:1.  Click on “Actions”2. Click on “Select Go-Live Account”3. Accept terms and click on “Accept”4. Open the pop-up5. Input email and password from my account (not the developer one) - eSignature Standard PlanAnd this is what I’m getting from it (HTTP 404 PAGE NOT FOUND): Can someone help me please​​​??!!!

Is there a Docusign endpoint that could govern me all the agreements in the user account. I am able to authenticate the user and get the info for the user

I’m using DocuSign Connect to send a webhook to Zapier when a document is completed. When I review the output of the webhook sent to Zapier, I do not see the document field values.  My custom connect is set up using REST v2.1 data format, SIM delivery mode, and data included is the following:Custom Fields Documents Attachments Document Fields Recipients Has anyone else had this issue or know a way I can adjust my configuration so that the output includes the document field values?

Our company is in the DocuSign Partner Program and we have a developer/sandbox account in DocuSign, some of our clients are looking for the feature to have the signature recipients to verify their identity with Bank ID. All signature requests are sent from client instances to DocuSign, I am looking to add the verification feature in our DocuSign integration but the “Identity Verification” is not available on our sandbox account under “Signing and Sending”. How can I get this enabled? 

I am using the navigator api for the docusign hackathon and i added the required scope but i keep getting Caused by: com.docusign.esign.client.ApiException: Error while requesting server, received a non successful HTTP code 400 with response Body: '{"error":"consent_required"}'and i just filled the request form for access to the navigator api beta but i don’t know how long it will take to getting approved considering timeframe, please i would appreciate your assistance

Hi,We have been working on getting an application up and running for our client, enabling them to send contracts for signing through DocuSign based on templates.Here is a summary of our progress:A developer account was created, and the application was written successfully. API test calls were successful, and initial testing went smoothly. We proceeded with the "Go Live" process, which initially seemed successful.However, during the second step of the process, we encountered an issue where our review was unsuccessful, but no specific feedback was provided.After reaching out to DocuSign support and going through several back-and-forth communications, we finally discovered the cause: we had missed filling out the power form. (If I recall correctly, this form used to appear when selecting the "Go Live" option, but with recent changes, it no longer seems to be offered during this process.)Once the form was completed together with the client, the production environment was properly bound to

Hi everyone,I'm working on a DocuSign integration where I want to use a template that dynamically updates as it progresses through a multi-signer workflow. Here’s the flow I’m trying to achieve:The initial template is populated with some hardcoded values for the first signer. Once the first signer completes and the envelope is redirected to the next signer, the template should dynamically update certain fields (e.g., names, amounts, or other placeholders) using data retrieved from an Azure Storage Account via API. This process should repeat for each signer, with the template being updated dynamically based on the signer’s role and data pulled from Azure.Steps I’ve Considered:Use the DocuSign API to create an envelope based on a pre-defined template. Populate initial tabs (fields) using the API (e.g., using templateRoles). Trigger a webhook or callback (via Connect) after each signer to: Retrieve data from an Azure Blob or Table. Update the envelope fields dynamically for the next sign

Hello guys, I need help ASAP!!I’ve been testing on test environment, made my 20 successful api calls and now i’m trying to Go-Live by clicking on Actions > Select Go-Live Account. Then I proceed to log in and i get a HTTP 404 NOT FOUND error.

The CXO of a company needs to sign over 20 envelopes daily, which are sent from various systems like Salesforce, SAP and with the majority coming from Docusign web app. Currently, the CXO uses a mobile app for signing documents. The company has developed a new internal portal for employees, which includes functionality for managing approval processes. Now, the CXO would like to use the new portal to sign all of their pending Docusign envelopes. Is this feasible using embedded signing?

DocuSign support states that they do not support .p7m protocol, it is CAdES. DocuSign only supports PaDES. The envelopes are from Italy. They must use the following link to unencrypted https://vol.postecert.poste.it/verificatore/itWhen the docs are unencrypted, the original does not have signatures. The signatures are on a page that is blank except for signatures.

Looking to hire a certified docusign consultant that can help implement specific features on a set of templates that I can re-use for all my clients

We’re thrilled to announce the closed beta launch of the Docusign Visual Studio Code Extension, a new tool designed to empower developers with AI-driven assistance for building seamless integrations with Docusign’s platform.With this extension, developers can:✅ Ask Docusign-specific questions: Simply type @docusign followed by your question in the GitHub Copilot chat window to get instant answers on topics like authentication, SDK usage, or integration best practices.✅  Streamline authentication setup: Use the @docusign /getAccessToken command to generate access tokens directly within your IDE, complete with guided steps for creating and managing integration keys.✅ Explore and implement solutions faster: Leverage AI-powered guidance to build workflows, automate tasks, and integrate Docusign’s capabilities effortlessly. How to join the Closed Beta ProgramThis closed beta program is your chance to test and shape this new tool while gaining early access to its features. Interested?The ext

As part of the development process, I am sending an envelope to the recipient through the DocuSign developer account (r**************@********) The email is successfully sent from DocuSign, as I can see the email content in the Developer Account Console page. However, the recipient does not receive the email in their mailbox, even after checking the Spam folder.Initially, we suspected it might be a firewall issue. I also tried sending the envelope to my personal email ID, but it didn’t work either. Although the email is sent from DocuSign, it is not received in the mailbox.Could this be because we are using the developer account?

Hi there,We’ve been using the DocGen API (https://developers.docusign.com/docs/docgensend-api/) to create pre-populated documents using a word template. In our word-template we’ve been using a custom font family Ciutadella.We’ve been having mixed success with some generated documents (pdf output) looking accurate, and some seemingly using a different font or have issues with spacing or alignment.Are custom fonts support by this API / Docusign, and if so what steps do we need to take to ensure it can be successfully used?Thanks!