Developer

I have a requirement to trigger sending of a document via DocuSign for remote signing. The signing link for the documents needs to be sent as a text message (SMS) using a custom solution (Twilio). Using Apex Toolkit dfsle.EnvelopeService.sendEnvelope(myEnvelope, false), I’m able to generate an envelope with a Template. Now the challenge is to get the signing URL. I have been able to get the recipient preview URL using dfsle.SigningService.getRecipientPreviewUrl(docuSignUUID,1) but it can’t be used to complete the document. I have tried using dfsle.SigningService.getSigningUrl(envelope, returnURL ,true) but it alwasy returns a NULL value.Is it possible to achieve what my requirement says? If yes, can someone throw light on what I’m missing or have been doing incorrectly?

We have Success Factors Recruiting and have used the standard API to connect to Docusign for e-signing the offer letters, work contracts etcThe SF editor is quite poor and despite my efforts to date I cannot get the ‘ok in SF preview’ to be the same in Docusign. I have tried explicit inline CSS, using tables and using CoPilot to help me with variations of simple HTML that is then rendered correctly in Docusign. The Text is too large on the whole when it gets to Docusign.The issue I think is that the SF end is HTML that Docusign tries to convert to a PDF - we use ‘tokens’ or preset field variables in the SF side to populate fields like name date etc.Would be very appreciative of anyone who has navigated this issue or can help with guidance on further steps to trythanksDarren

Hi, We have a problem with the option to decline to sign, using the python sdk with sms authentication, we still have the decline button even when adding the property in to the DocuSign_SignResource file and add the file in the brand admin.In addition, as soon as we click on the decline button, the signature is rejected without any reason being given.Do you have a solution? 

Hi, I am new to Docusign and I am working on a POC for integrating DocuSign Embedded Signing using Docusign JS  within a Vue.js application. I am using the DocuSign Python Quick Start project to generate the signing URL with a slight modification:Instead of redirecting after generating the signing URL, I print it to the console. I manually copy this URL into a static variable in my Vue.js app and load it Docusign JS ProblemWith a fresh signing URL:✅ I receive the ready DOM event callback.✅ The signing session renders successfully inside the <iframe>.✅ After completing the signing, I receive the sessionEnd DOM event callback.However, when I reuse the same signing URL:❌ No DOM events (ready, sessionEnd, or any error) are triggered by DocuSign JS. Expected BehaviorIf the signing link is expired or reused, I would expect:An error from DocuSign JS instead of silent failure. A sessionEnd event with a reason like `ttl_expired`.The Vue.js script<template> <div class="signing-co

Hi,I'm developing a service that returns a sign-embedded URL for the front end using the .NET (C#) SDK var docuSignClient = await CreateClientAsync();var envelopesApi = new EnvelopesApi(docuSignClient);var recipientViewRequest = new RecipientViewRequest{ AuthenticationMethod = "none", ClientUserId = recipientId.ToString(), ReturnUrl = returnUrl, UserName = recipientName, Email = recipientEmail, FrameAncestors = new List<string> { "http://localhost:7777", "https://apps-d.docusign.com" }, MessageOrigins = new List<string> { "https://apps-d.docusign.com" }};var viewUrl = await envelopesApi.CreateRecipientViewAsync(_docuSignConfiguration.APIAccountId, envelopeId.ToString(), recipientViewRequest);return viewUrl.Url;However, when I use the returned URL with DocuSignJS Focus View, I get the following error:Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'none'". I've

The April 2025 Docusign Developer Newsletter is out! In this issue, our top story is all about connected fields, a new Docusign extension that enables you to define any data type you like and verify its input against any external data source. You can build connected fields extensions, publish them on the App Center, install your own and others from the App Center, and then use them in eSignature envelopes. You can also use the Connected Fields API to poll your account for a full list of all the data types you can flag for data verification in envelopes you send through the eSignature REST API. Additional highlights:Maestro workflows are now embeddable in an iframe. You can use this technique to present Maestro workflows within your API integrations. Our newest Visual Studio Code extension is now in closed beta: find out how you can join.  We went to Salesforce TDX in San Francisco last month and ran a mini hack. Events and more events! We’re running online webinars and attending in-per

Hi , I am using DocuSign Connect to connect to an API . API uses OAuth and an additional security using an header . How do I pass an additional header to the api ? Thanks for the help .

Hello everyone, I hope you are all well. I am integrating with Docusign using the PHP SDK in Laravel. Everything was working perfectly until a request came up that I should have 2-factor authentication. I did it via SMS. I was able to send 1 envelope successfully. After that, I am only receiving this error:"error_code" => "RECIPIENT_LIMIT_EXCEEDED""message" => "The recipient limit on the envelope has been exceeded. The cumulative recipient limit has been exceeded."I am only sending 1 recipient.A part of my code:Note: I changed the phone number to an example one but I am passing on the real one. $signers = [new Signer([ 'email' => $client->email, 'name' => $client->full_name, 'recipient_id' => '1', 'client_user_id' => $client->user_id, 'tabs' => new Tabs(['sign_here_tabs' => $signHereTabs]), 'email_notification' => new SignerEmailNotifications([ 'send_email' =>

I need to add another record type to dropdown box of NetSuite Docusign Setting (Custom Record). Just appears 6 records type (Customer, Estimate, Invoice, Opportunity, Purchase Order and Sales Order)I want to add Expense Report to send via Docusign for approval 

I am getting blank document in email when sending through API

Hi! I just published a new YouTube video on how to use Docusign Conditional Routing to automatically send envelopes to the right approvers based on business rules.You’ll learn how to:Route envelopes dynamically to different recipients based on field inputs. Configure conditions to route the envelope to the right recipient. Combine routing with PowerForms or Web Forms for self-serve workflows. Integrate your CRM and other apps to reduce manual workSimplify your approval workflows with automation! Watch the full video here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.Solusigncom | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hi everyone,Just want to ask this question that’s been bugging me.We currently have an existing package for Salesforce DocuSign Apps Launcher - DocuSign Negotiate and a DocuSign Plan (which I’m not sure of) cause it was purchased 4 years ago. When I tested the Docu Gen Api , it was working on our demo sandbox. But am not sure if that’s going to work in our current live production. So, my idea is -- can we use the existing apps and integration key that’s in our production right now for our custom api integration build or do we still have to go through the api go-live process where we have to push the integration keys from Developer to Production account? Appreciate all your inputs!

Hi,Recently I’ve been trying to set up an integration between DocuSign and an external system.I completed the setup in a Developer account, finished the 20 test connections and passed the go-live review (on the 2nd attempt).However, the integration still does not appear in our Production account’s “Apps and Keys” page.The Apps and Keys page of the Developer account shows our integration, stating that the Go-Live review has passed with a link to the Production account. When this link is used, I’m taken to the empty Apps and Keys page of our Production account.I submitted a ticket to DocuSign support about 2 weeks ago, and they have so far not been helpful at all.Any assistance that could be provided here would be much appreciated.Thanks.

I am attempting to populate the values in a custom tab (type: list) by making a call to a REST API we host.  The use case is that we are having residents of a senior living facility who are signing lease disclosures in Docusign, and we want them to indicate the name of the facility (from a list) and their resident ID from the electronic health records system they use at the facility.  Both of those lists are ever-changing, so they need to be dynamically updated as each envelope is created and sent.My question is, is there a way to dynamically populate a custom tab list by calling a REST API?

 Need help in SF with Docusign integrationRequirement: Want to prepopulate some custom fields value on template, i have set these custom field values in apex(using apex toolkit) class but i am not seeing these values in pdf. Development approach: I have already installed DocuSign(Docusign Apps Launcher) managed package in salesforce and uploaded DocuSign template(word format) in DocuSign portal. I have set the custom field values in apex code, Receiver is receiving an email with attached doc but he is not seeing custom field values post complete it also. Feel free to ask any doubts/more details.I am using below code:dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity(mySourceId));List<dfsle.Tab> envelopeTabs = new List<dfsle.Tab>();//Custom fields isResidentialenvelopeTabs.add(new dfsle.TextTab().withValue('ResidentialValue').withDataLabel('isResidential'));dfsle.Recipient myRecipient = dfsle.Recipient.fromSource(contact.Name,contact.Email,nu

We’re excited to announce the brand new connected fields extension, alongside our newest API, the Connected Fields API!With our new connected fields extension, you can go beyond the existing predefined data verification extensions (which verify specific types of values like email addresses and bank account numbers) and verify data in any format against your organization’s system of record. The Connected Fields API makes it easier for you to customize your agreements with data verification and connected fields extension apps by enabling you to perform real-time programmatic custom data verification for values in your eSignature envelopes. The API provides an endpoint, TabInfo:GetConnectedFieldsTabGroups, which returns the full definitions of your connected fields: every field type whose data can be verified using one of your account’s Extension apps. Check out the code example to learn more about how to use the API and see the connected fields reference implementation for an example of

1. After filling in the corresponding template in docusgin, is there a "save" or other status? Can the third-party system - Hesi obtain it? 2. After filling in the template and pushing it to Hesi for approval (non-sending status), is there a way to prevent the business party from modifying the contract template content in docusgin to avoid inconsistency with the approval content? 3. For fixed templates, because they are pushed to the third-party system - Hesi for approval, the system will automatically send the contract to the customer for signing, so can the send button of these templates be canceled or restricted? Prevent the business party from sending manually.

Problem:The redirect after signing url can only set through Account Settings.Current situation:Currently, when an envelope is created in our app, an email is sent to the user via DocuSign (Remote signing).A link is also generated where the user can access the Envelope through our app (Embedded signing). So we combine remote and embedded signing.This method works, but there is a problem regarding the redirect Uri definition when signing remotely.The redirect Uri is only taken from the account settings. A defined uri in the branding is ignored, as is a redirect uri that is specified directly during the API call. Additional Infos:In the envelope definition the embeddedRecipientStartUrl in the signer object is set to “SIGN_AT_DOCUSIGN” and the clientUserId is defined which is later used for the RecipientView link generation.

Hi, We have not specified any FrameAncestors or messageOrigins for displayFormat: “default”I can see a loading icon on the screen Are those required even for Default view??Thank you

How to implement 'Receives a Copy' using apex tool kit salesforce

Hi, I need a consultant to do an integration with a CV CRM. Who can help me?

Hello, I have used the Apex Toolkit to define the writeback of my envelope.The docs are correctly attached to the case and the status on the case is correctly updated.However, the doc title is not updated as specified in the writeback. It retains the original name. I need to add ‘_completed’ to the initial title when it is signed. Anyone encountered this issue or has an idea how to resolve this? ThanksCode Snippet :             myEnvelope.withOptions(new dfsle.Envelope.Options(                false,                new dfsle.Document.WriteBack(caseRecord.Id,  ‘Signed Contracts’, false, true),                new Map<String, Map<String, Object>> {                    dfsle.Envelope.STATUS_COMPLETED => new Map<String, Object> {                        'Case.Status' => 'Docs received'                    }                },                new Map<String, Map<String, Object>>()            ));

Hi everyone,I'm working with the DocuSign API to track the status of individual documents within a multi-document envelope. My goal is to determine whether each document has been signed separately, but I only see status tracking at the envelope level.I’ve tried the following: Used GET /envelopes/{envelopeId}/documents, but it only retrieves documents, not their status. Checked recipient statuses, but they apply to the whole envelope. Explored webhooks, but I’m unsure if they can provide document-specific updates. Questions: Is there a way to track individual document status separately? Would splitting each document into its own envelope be the best approach? Can DocuSign Connect provide document-specific events? Thanks in advance for your help!

I was wondering if anyone is using DocuSign within their Online Banking Portals. If you do, how are you doing this? What kind of forms are you using? It seems our online banking vendor is not on DocuSign’s list of vendors. Thanks, 

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of March 2025. Thread: Error when downloading the envelopehttps://community.docusign.com/esignature-api-63/error-when-downloading-the-envelope-23190Summary: The developer is trying to programmatically download envelopes that have already been completed using the EnvelopeDocuments: get endpoint. However, when they download the documents, they find that the fields and signatures completed by the envelope’s recipients are not appearing in the downloaded files.Answer: Any values of completed tabs will only appear in the downloaded documents if the eSignature sending settings are configured in a way that allows this. Under Sending Settings in the Fields and Properties section, be sure to select the checkbox labeled to When an envelope is sent, write the initial value of the field for all recipients. See the blog post Tabs deep dive: eSignature settings for more informati