Developer

I have a Docusign template that:-Updates to “Pending Signature” status when sent (this works fine)-Updates to “Signed” status when completed.The problem is that if the language of the user sending it is in Spanish, it does not update to “Signed.” If I change it to English, it works correctly.I have the values of the picklists translated.I don't know what the problem could be.

Can anyone share Rest API reference to fetch IDV Evidence PDF. As per the information in https://developers.docusign.com/docs/idevidence-api/how-to/retrieve-idevidence-media/ we are able to capture the photo id only. How can we fetch the PDF with IDV data and captured front and back id images?

The Salesforce org I’m working in currently has DocuSign implemented via a URL Button that initiates DocuSign from the Quick Actions menu. I’m working to update that functionality to occur in a Salesforce Flow instead. I’d like the same functionality to fire automatically when the flow completes and populate the DocuSign envelope with variables from the flow.My thought is this would need to be done in Lightning or Apex and called in the flow. I initially tried automatically firing the button on init, but Lightning doesn’t support URL buttons so it won’t fire as expected. Has anyone initialized DocuSign from a Flow before?

Can I access admin dashbaord where we setup webhooks and integration keys from a business plan or do I have to buy a developer plan

I’m happy to announce 🔦 that Docusign has just released a new Postman collection for the Workspace API.🎀You can find this new collection here - https://www.postman.com/docusign/docusign-s-public-workspace/collection/e7gl0uc/workspaces-api-betaHere is some basic information about the Workspaces 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",

Hi everyone, My name is Valeriya, and I’m a product manager at fintech startup that helps people refinance their high-interest credit card debt into one lower-interest loan, with a single monthly payment and a clear debt-free date. We’ve successfully tested the DocuSign API and SDK in the sandbox environment to enable digital loan agreement signing between our company and our clients. Here’s how it works in our app:1. The loan agreement is generated on our side and sent to DocuSign via API.2. The client receives a link to the signing ceremony directly in the app.3. DocuSign opens in the in-app browser, allowing the client to sign the loan agreement easily on their mobile device. We’ve now purchased a commercial plan under and want to move to the production environment.I’ve already completed the ISV Embed Developer Account form for our app. How can we get someone to: 1. Review our ISV Embed for

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 i

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.

Hi everyone, My name is Valeriya, and I’m a product manager at fintech startup that helps people refinance their high-interest credit card debt into one lower-interest loan, with a single monthly payment and a clear debt-free date. We’ve successfully tested the DocuSign API and SDK in the sandbox environment to enable digital loan agreement signing between our company and our clients. Here’s how it works in our app:1. The loan agreement is generated on our side and sent to DocuSign via API.2. The client receives a link to the signing ceremony directly in the app.3. DocuSign opens in the in-app browser, allowing the client to sign the loan agreement easily on their mobile device. We’ve now purchased a commercial plan under and want to move to the production environment.I’ve already completed the ISV Embed Developer Account form for our app. How can we get someone to: 1. Review our ISV Embed for

Join us in San Francisco on October 30 at Docusign Discover25 for a hands-on developer experience built for builders who want to shape the next generation of agreement management.Spend the day coding alongside Docusign engineers, partners, and fellow developers—testing new APIs, exploring AI tools, and influencing the roadmap for Intelligent Agreement Management.Why you should comeShip faster. Get early access to new SDKs, APIs, and automation frameworks. Build with AI. Learn h

Built something cool in the Docusign Developer Lab during Dreamforce? Show off what you made. Whether it’s a workflow that collects customer data, verifies identity, or connects with Salesforce or Slack, every build tells a story of what’s possible with Docusign.How to participatePost in the Developer Forum with a short summary or screenshot of your workflow, or a code snippet highlighting how you triggered it by Monday, October 20  Add the tag “DevLab25” to the post so we can find it

Hi, I would like to set Email Default language to all recipient. I am aware of the option “Custom email and language for each recipient” on the settings, but that is not what I am looking for.I do not want to enable it because I need to dynamically set the Email subject and text with the Salesforce Apex Toolkit. If I enable this option, I cannot set the subject and text programmtically. I want to set the default language to German (Currently in English).  How do I achieve this? 

Hello — I’m working with a DocuSign Maestro template where I’d like a signer to enter a “whole dollar” value (e.g., 100) and have it automatically display or format as currency (e.g., $100.00).In the template designer, using a Currency / Number field works perfectly when setup so the signer enters the value manually on the contract. However, when that same field is prefilled via a Web Form and Maestro Workflow, the formatting (dollar sign, decimal places) doesn’t carry through — it just outputs the raw number.I’m trying to determine if there’s a way to apply or trigger that formatting on prefilled values.The only workaround I’ve found so far is hard-coding the “$” before the field and “.00” after it, leaving space for the user to type the number — but that feels like a fragile solution.Has anyone found a cleaner approach? Can a Web Form / Maestro prefill override or trigger the formatting rules of a currency field?

Hey everyone! 👋 Niani here—I’m a programmer writer at Docusign and former full-stack engineer.In September, I hosted an async AMA focused on automating agreement workflows with Docusign APIs.You all asked some great questions, ranging from authentication and webhook tracking to workflow versioning and resiliency patterns. I’ve pulled together a recap of the top questions here so you can reference them anytime as you build with Maestro. How does authentication work with Maestro? Can it be linked with S

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

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 recip

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

👋 Hi Community, Sagnik here—Docusign’s CTO.Developers are redefining how agreements move through business—faster, smarter, and more connected. That’s why I’m excited to invite you to Docusign Discover on October 30 in San Francisco.This is our flagship builder event, designed for developers, architects, and IT leaders. Together, we’ll:Harness AI to unlock agreement data Automate workflows to eliminate bottlenecks Build integrations that scaleMost importantly, we’ll connect as a community—sharing ideas, experimenting hands-on, and learning from one another.Seats are limited—

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!',                            },

For years, developers building integrations with Docusign APIs have voiced a common frustration: “Why do I need to make 20 eSignature API calls to take my integration live?”We heard you. And we’ve fixed it.Today, we’re excited to announce the launch of a streamlined Go-Live experience in Apps & Keys that eliminates the 20 API calls requirement, making it easier for developers to take their integrations live. 🌟 What’s NewNo more 20 eSignature API calls for Go-Live: Going live is now seamless. Simply select your integration type, enter your production account details, and the built-in validation will check if your integration is eligible to go-live in that production account. If eligible, your integration can, in most cases, go live instantly. 🎯 Why This MattersPreviously, developers were required to make 20 eSignature API calls to start the Go-Live process. I

How can developers take workflows to the next level? 🚀 In this blog, we highlight how This Dot Labs partnered with Monday.com to integrate with Docusign, helping teams streamline processes, cut down on manual tasks, and keep everything moving in one place. It’s a clear example of how the right tools can simplify complex processes. 🎤 Want to hear more? Tracy Lee and 

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!