Developer

Hello,We set up a DocuSign app on our client’s dev account, passed the Go-Live check, and published to production. As the next step, a production user opened the consent link and approved it. We can see the app listed under the user’s Connected Apps.However, our OAuth token request to https://account.docusign.com/oauth/token still returns:{"error":"consent_required"}Note: We also have another production account where this flow works as expected—authentication succeeds—so the issue appears to be specific to this production account. I’m out of ideas on what else to verify and would appreciate any tips or guidance. Thank you.

Thanks to everyone who stopped by the Docusign Developer Lab at Dreamforce! It was great meeting so many of you—developers, admins, and builders—who jumped in to explore building Maestro workflows and using the Maestro API.  We heard from many of you that some of your biggest agreement challenges come from manually processing agreements, which ultimately slows down deals. Docusign Intelligent Agreeme

Hello,We setup a Docusign app on dev and followed all the steps mentioned in granting administrative consent for JWT Grant Flow. When we migrated our app to Prod, firstly, we don’t see the Organizations Tab that we see on Docusign dev and I get this error when I am trying to get an access token from Docusign.error 400 while reaching https://account.docusign.com/oauth/token: {"error":"consent_required"}I am not sure how to move forward from here because our setup works on Docusign Dev but doesn’t work after going live.

Hi Team, Today we found docusign iframe was not loaded, it even worked yesterday, no changes applied in our side.When I opened the signing URL  in the browser, which starts with “https://demo.docusign.net/signing/mtredeem/v1”.I cannot find our domain in “content-security-policy” response header, and confirm our domain has been added into the FrameAncestors whie calling CreateRecipientView API. Is their any update for demo site? Thanks,Fei

Hi DocuSign Community!I'm experiencing an issue with displaying base64-encoded images in HTML templates used for embedded signing via the eSignature API.I'm using HTML templates with <img> tags that contain base64-encoded images in the src attribute (using data: URLs). The images display perfectly when viewing the HTML in a standard web browser, but they disappear when the document is embedded using the DocuSignJS SDK for signing.Technical Details:API Used: DocuSign eSignature API with embedded signingSDK: DocuSignJS SDK (https://js.docusign.com/bundle.js)Image Format: Base64-encoded images using data:image/[format];base64,[data] syntaxImplementation: HTML templates with embedded <img> tags Are there any known limitations or specific requirements for displaying base64-encoded images in HTML templates when using embedd

I have a strange misalignment of signer records when I am setting up one signer as a host and another signer as an inPersonSigner using API.  The result of a setup is the signerName is used along side of a host email when it is showing “Hosted By” and also in one of the flow dialogs when it is saying that “Name1, pass control of the session to Name1”, where Name1 is the inPersonSigner signerName. I am submitting clientUserId for both host and inperson signer, otherwise I could not match the inPerson signer while generating a RecipientView. I see that it aligns the names correctly if I remove clientUserId from inPersonSigner record, but it breaks the mapping for RecipientView. Is there any possible work around for this?

Hello everyone,I’ve got some questions regarding the export of events, generated by employees to a company’s SIEM. As a security team’s representative, I’m interested in enhancing the monitoring and security of this system in my company, so I want to know if it’s possible to export this events to SIEM systemOur company has eSignature Business Pro Edition Plan and I have read the DocuSign has a Docusign Monitor, which can detect potential threats and it also has a pre-built alerts and SIEM integration capabilities, but unfortunately our plan doesn’t have this DocuSign Monitor. Are there any other ways to export the event logs to our SIEM system? Thanks everyone in advance.

​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 a

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?

I’ve been using Power Automate to send/track agreements sent by our legal team for about a year. Sending an envelope inserts a record into our MSSQL database, and the tracker PA updates the row when an envelope status changes.The contracts team recently reached out and wants to start recording the reasons that envelopes are being voided/declines. Previously I was just tracking if they were or not, but added a new column to the SQL table for ‘reason’. Capturing the reason for future envelopes has already been implemented, but I have ~350 voided envelopes I would like to retroactively access the ‘void reason’ for. I have all the envelope IDs that I need, but is there an API endpoint that I can call to get the void/declined reason? If I have to make two PAs (one for void, the other for decline, as the JSON packages are slightly different), that’s fine. I just haven’t found anything that works so far. Thank you!

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 b

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?