Developer

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?

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.

Imagine a scenario where I send an envelope to several recipients containing some documents (let's call this the "first batch"). Later, I send a new document inside this same envelope. If any recipient hasn't completed signing the documents in the first batch, the new document is sent to them as usual. They receive an email notification, and upon opening it, they can view both the documents from the first batch and the new one. However, another recipient who had already completed all the pending signatures for the documents in the first batch isn't sent this second notification with the new file. I'm developing this functionality in PHP with the eSignatureAPI + e-sign client sdk.I'd like to know if it's possible to create this functionality. And if so, how can I do it?

Hello to everyone, We have developed and integration between DocuSign and our custom application which allows to set up integration with Salesforce. On our side everything works fine. However, when we log into DocuSign from our iPad using the developed signature button and get redirected to the DocuSign, we have some troubles here.First of all, it may take some time to load the page with the request of the SMS confirmation but it’s not the main issue. The main issue is that when we enter the code from SMS and get redirected to the page with template, it often happens that the screen just becomes white and that’s it. We can’t do anything after this, only to cancel the signature.I was talking with the developer team on our side and they told me that it seems like an issue is on DocuSign side. So that’s why I am posting this here to understand whether there were any other cases like that. And if yes, then what can be a reason of that? So that we can fix it before Go-Live of integration.

​Hello,​I am trying to achieve a specific email notification workflow with the eSignature REST API, but I'm running into an issue.​My Goal:​I have an envelope with one embedded signer (clientUserId) and several CC recipients (carbonCopies). My desiredworkflow is:​The CC recipients should receive NO email when the envelope is sent.​After the embedded signer completes the signing, both the embedded signer and all CC recipients should receive the final "Completed" notification email.​What I've Tried:​I have tried two approaches, but both have failed:​Attempt 1: Using routingOrderI set routingOrder: 1 for the signer and routingOrder: 2 for the carbonCopies.​Result: The CC recipients still receive an email immediately when the envelope is sent. This email contains a "live view" link to the in-process document.​Attempt 2: Using suppressEmailsI kept routingOrder: 2 for the CCs and added "suppressEmails": "true".​Result: This successfully stops the initial email to the CCs. However, it also st

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

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 form submission  2. Help us move forward with the Go-Live / production setup? We’re currently una

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.

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 form submission  2. Help us move forward with the Go-Live / production setup? We’re currently una

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 how to extract structured data from contracts, automate agreement workflows, and embed intelligence directly into your app. Shape the future. Connect directly with Docusign leaders and give feedback that impacts what we build next.What’s happening🚀 Keynotes & PanelsHear from Docusign CEO Allan Thygesen, CTO Sagnik Nandy, and leaders across fintech and dev communities on how AI, extensibility, and automation are changing how businesses agree. Here’s a preview of who you’ll hear from:Allan Thygesen, President &

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 Tell us what you learned or what you’d build nextWhat you’ll getUp to 10 submissions will be selected based on creativity, technical execution, and potential impact on Tuesday, October 21 . Selected builders will each receive a $150 Loop & Tie gift of their choice. Your post might also be featured in an upcoming Community newsletter or social post.Let’s see what you built! 💥Terms & ConditionsParticipation in this challenge is subject to these terms and conditions: Contest open to Docusign Communi

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? Could a formula or script on the prefill side enforce proper formatti

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 SSO, and can data be passed from an identity system?Answer: Maestro uses OAuth 2.0 for authentication. At the account level, Docusign supports SSO for user login, but Maestro doesn’t automatically pass identity data from your IDM or authentication provider into workflows.If you need to use attributes from your IDM (like email, employee ID, or group), you can capture those after login and pass them into Maestro as workflow input variables. Maestro can also accept data from systems such as C

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,