Developer

How do I send an ICP Brazil certificate via the API?I'm using PHP with Laravel.And using your Git repo.https://github.com/docusign/docusign-esign-php-laravel/tree/main

DocuSign integration in my app allows to find the DS link in a specific field of my database. This DS link allows me to get the signed document on my server. 90% of the time it works. 10% of the time the DS link does not appear in the field where it is supposed to be.I can not establish any common properties or specificities in between all names for which the DS link does not appear.Thank you if you can help  

Hi,I’m working with a sandbox to integrate docusign in my web app. My service is able to create the envelopes and, checking on the docusign developer page all appear to work properly. The problem is that the mail never get to the recipients.

 I am  trying to access and send documents through the Dropbox integration with DocuSign, but we keep encountering the following error:https://na4.docusign.net/plugins/api/RedirectExternalDocService.aspx?status=fail&error=AuthenticateFailed  Details: Integration: DocuSign connected with Dropbox SharePoint Site URL:  App Version: 4.0.3 Server Version: 4.0.0.6 Status: Dropbox is connected successfully, but when we try to prepare an envelope with a Dropbox file, the authentication fails. Has anyone experienced this issue before? How can we fix this AuthenticateFailed error?Any guidance will be highly appreciated.

When a document gets voided due to the expiration date, I assume the webhook sends out an event to the listener telling the doc has been voided, but I am not receiving any voided event. I am receiving all the other events just not any voided or expired events. Can someone tell me how to configure the voided\canceled\expired documents?

How do I access my sandbox?

Hello everyone,I’m currently working on an integration with the DocuSign API using JWT authentication. When I try to call the API, I get the following error:❌ [send-docusign-signature] DocuSign rejects JWT signature - public/private key mismatch or missing consentHere’s what I’ve already checked: The private key in my code is the one generated when I created the app. The public key has been uploaded correctly in my DocuSign integration settings. My Integration Key (client_id) is correct. I suspect the issue might either be a key mismatch or the fact that the user consent has not yet been granted. My questions are: How can I confirm whether the issue is due to missing user consent versus a key mismatch? What is t

I'm learning how to use SOAP UI. Does Docusign provide a WSDL (Web Service Description Language) file or some documentation for REST API?

Our next Developer Async Ask Me Anything (AMA) is coming up in September—and we want you to decide what we cover. Cast your vote in the poll below to let us know which topic you’d find most valuable.If you’ve got another idea for a future AMA topic, share it in the comments. Your input helps us make these AMAs as useful and relevant as possible.If you missed the last AMA on embedded signing & sending, you can check it out here. 

💻 While vibe coding is possible with our Docusign Developer AI Assistant, it’s important to be smart about incorporating vibe coding into production projects. Over at The New Stack, I wrote about how the Developer AI Assistant for VS Code can be used to build integrations with trusted AI assistance that goes beyond just vibes.  💡 Check out the post and let me know what you think! Have you tried

Hi,I'm encountering an issue when using the compositeTemplates feature to create an envelope from a template that contains multiple documents.When retrieving this template via the EnvelopeTemplates:list endpoint, only the first document is returned in the response - the remaining documents are omitted.This behavior is different from what I observe in the DocuSign web UI. If I simulate the same process (e.g., by creating an empty envelope and applying the templates), all documents are present as expected.Is this a known limitation of the EnvelopeTemplates:list API? Or am I missing something in the way the template is structured or retrieved? Thanks in advance for any help or clarification.

I am using embedded signing with my API and every day I send documents to sign to many recipients. All the documents I send need to be signed again by our company but it is not viable to do it one by one so I would like to know if there is any way to sign several documents easily. The way it would be done it is that we put our company the last in the recipients order to sign of each document, and then, instead of signing all one by one, sign all at once (of the ones alredy signed by the previous recipients to sign). Thank you.

How to enable live video and screen sharing options for DocuSign Notary in a demo (developer) accountI want to check DocuSign Notary in my developer (demo) account, and I can see the Notary option there.However, while testing, I found that the live video recording and screen sharing features are not available. I need to test and demonstrate the full RON workflow before moving to production.How can I enable the video session and recording features in my demo account, or is there any alternative to achieve the same?

Please explain the process for setting up Remote Online Notarization (RON) with DocuSign Notary in a Developer Account, including configuration and prerequisites.

We have noticed a few errors in our system where the response for the EnvelopeLocks:get endpoint (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopelocks/get/) does not contain the lockToken field.The docs dont seem to have any point which indicates this as expected behaviour.Wanted to know if there is some nuance I am missing?btw we get all the other data about the lock in the response, its just the lockToken that is not there: { lockedByApp: "-", lockedByUser: { uri: "--------------", userId: "--------------------", userName: "----------

Hello,I’ve been working in Maestro Workflows using webforms to build them out. The goal being so that the webforms speak with the workflow so that people on my team can use a link to send out and fill out contracts versus needing to sign into DocuSign. Currently I have set up all my webforms reflected off my contract templates, and then I built out my workflows reflecting the needs of my departments and the flow of my contracts. For example Department X needs 4 types of contracts and so they branch out in different ways. Here’s an example of what a workflow would look like:LinkWebformBranching question 1: Are they A or B?A:Are they B or C? → contracts 1 & 2 B: Are they D or E? → contracts 3 & 4Right now when I test the webform it works perfectly but the branching question 1 is always leading to option B, even though I select all the options for option A. So I’m always getting the wrong contract as a result. 

I wanted to ask if there are there any APIs available for the following tasks?1. Fetching the total number of documents that have not been signed bythe recipients, or to provide the status of all the documents?2. Fetching the total number of envelopes that are in a pending or failed state?3. Fetching logs or metrics data for Docusign CLM and eSignature thatwould contain latency (duration) and reliability (http status code)information for APIs being called, CLM Workflow Execution Stages orEnvelopes Processing Stages along with their statuses?4. Fetching the start to end time of all the CLM workflows?

What I wanted:I need to use both Remote Signing & Embedded Signing in a single DocuSign template (Single Signer). My goal is to redirect the user to a custom page once they complete the signing process, whether they sign through the flow page or via the email link I send for the signature in DocuSign.What I've already tried: I have tried implementing both BrandId (for remote signing) and ClientUserId (for embedded signing) in the same template. This approach is working fine for embedded signing, but I am facing issues with remote signing: The exception is thrown when using remote signing, and the user is not redirected to the custom page after signing. What I know: Signing Completed URLs can be set in In-session Landing Pages. In-session Landing Pages are an account-level setting

Hi everyone,I’ve heard that DocuSign uses Onfido in some of its identity verification workflows.My question is:Is it possible to pass existing Onfido verification data (photo of the document & video with face) directly to DocuSign in the background, so that the user can generate a Qualified Electronic Signature (QES) without going through the identity verification process again?If yes, could someone share documentation or examples showing how to integrate this, ideally via API?Thanks in advance!

Hi,I am updating an embedded signing flow that uses a iFrame element on a page to use the Docusign JS method defined here (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/#docusign-js). I get the recipient URL and pass it to the following code:  var iframurl = "{{iframeUrl}}"; window.DocuSign.loadDocuSign('xxxx').then((docusign) => { const signing = docusign.signing({ url: iframurl, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary but

How can I implement notary using DocuSign video conferencing? Can you please provide the code implementation for Remote Online Notarization?Can you please help me

Hi everyone,We're using the DocuSign API to send legal agreements (Unilateral Undertaking and Customer Supply Agreement) via our platform. The envelope is generated using the primary user's profile — it includes their name, address, and other key details. That user is assigned as the signer and receives the envelope via email.However, in many cases the property has two owners, and we need both individuals to sign the same document — even though it’s initially triggered and sent using just one user's profile and email.Our goals: The primary user receives the envelope and signs as normal. The same envelope should allow a second person (co-owner) to sign. This may either be: Another signer using the same email address, or A second signer added by the first signer at the time of signing (if poss

We’ve just published a brand new developer use case focused on Compliance and Identity Verification, and it’s packed with ways to help you build secure, compliant verification flows right into your applications.Whether you work in financial services, insurance, or any industry that requires strong identity checks, this guide walks you through Docusign tools and APIs you can use to:Verify signer identity with multiple authentication options   Meet industry regulations while keeping the user experience smooth   Integrate verification directly into your signing workflows  Check it out here: 

With SOAP API, I can send envelope up to 35 MB most of the time. If it’s more than 35 MB, DocuSign returns error REQUEST_ENTITY_TOO_LARGE. However, I had a case where envelope contains a 17 MB PDF, with 2 supplement files (10 MB and 14 MB). The envelope was sent successfully. Why?WIth REST API, the limit is 25 MB. If envelope sent is more than 25 MB, DocuSign returns error request is too large. Sent envelope with 30 MB PDF and error returned is:REQUEST_ENTITY_TOO_LARGE - The request size of 41625837 bytes exceeded the maximum size of 35651584 bytesFile size is 30,487 KB. The maximum size limit is not 35 MB. Should the limits be different between SOAP and REST? I’m trying to figure out whether the issue is on our server.