eSignature API

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 product

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?

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, I need a consultant to do an integration with a CV CRM. Who can help me?

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, 

I am using eSignature API with the C# SDK, working in developer/test mode. I have everything working really well, except for my Connect webhook isn’t getting event notifications. I have a working endpoint which tests well using CURL and a mock SIM payload. And the Admin Connect logs show ‘Success’ for every event. But my callback listener nor the server register any incoming requests. In my code I create a list of Envelope events and later add them to the Envelope object’s EventNotifications list object.List<EnvelopeEvent> envelopeEvents = new List<EnvelopeEvent> {    new(){ EnvelopeEventStatusCode = "Sent"},    new(){ EnvelopeEventStatusCode = "Delivered"},    new(){ EnvelopeEventStatusCode = "Completed", IncludeDocuments="true"},    new(){ EnvelopeEventStatusCode = "Declined"}};envDef.EventNotifications = new List<EventNotification> {    new EventNotification("SIM", EnvelopeEvents: envelopeEvents, RecipientEvents:

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

Our B2B software has an embedded e-Signature integration with DocuSign where we allow our software users to create envelopes and tag recipient fields for other software users.  Our integration utilizes a “system user” who authenticates to the customer’s DocuSign account and all subsequent envelopes are created and signed on behalf of that system user. For the error message: Account lacks sufficient permissions.  In-session permission required when specifying a captive recipient.the customer’s system user has the “DS Admin” permissions profile.  I welcome any ideas where the client’s DocuSign Admin can go to enable a “in-session permission”?

I have created a application in developer account and verified it after making 20 API calls. I am using JWT authentication. After that I logged in to my production account and granted access again using https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=<YOUR_CLIENT_ID>&redirect_uri=<MY_REDIRECT_URL>.I also updated the UserId and API Account ID. Now when I am trying to send document to sign using my application, I get error {"Error while requesting server, received a non successful HTTP code with response Body: {\"error\":\"consent_require

Hi Community,Does anyone use DocuSign with Lone Wolf here? I need help with my first e-signing and sending docs out for e-signing. According to Lone Wolf, my DocuSign account is already integrated with Lone Wolf. Lone Wolf reps are not trained for DocuSign support. I’ve put in a support request to DocuSign. If you’re so inclined, Help!   

When downloading the envelope via the application, the completed fields are not shown in the document and the signatures are not shown eithernote: I am using the development environment, my account is not yet in productionapp.get('/envelopes/:envelopeId/documents', async (req, res) => {  await checkToken(req);  const envelopesApi = getEnvelopesApi(req);  const envelopeId = req.params.envelopeId;   my code:  try {    const docs = await envelopesApi.listDocuments(process.env.ACCOUNT_ID, envelopeId);    res.json(docs);  } catch (error) {    console

Hi everyone,I need some help with the DocuSign Go-Live process. I’ve been trying to get my Integration Key (5adb2409-a79c-4616-8a0c-79de07f2d449) approved for production for over a month, but I keep getting declined without any reason provided.Here’s what I’ve done so far:✅ Read and implemented all troubleshooting documentation✅ Tried with multiple Integration Keys✅ Passed automatic review (20 successful API calls, no polling)❌ Go-Live manually declined multiple times (first two attempts took 3-5 days, latest one was rejected within hours)❌ No emails or notifications explaining the rejectionI’m stuck and don’t know what else to fix. Has anyone faced this before? How can I get feedback on why the integration is being declined?Any insights would be greatly appreciated!

Hello, I want to implement the CSC (Cloud Signature Consortium) API integration (TSP API with CSC), but i can't find any description. Could someone send me a link that describes the integration steps or a documentation? Example is also appropriate if available.

Hi everyone, Docusign newbie here. Not sure which category to post this in so apologies in advance on that one.I work for a MSP. Our client uses Dayforce HR platform. In order for docusign signature box to pop up in browser we want to assign an Azure policy.The HR website is https://us242.dayforcehcm.com:443Should I allow this URL https://na2.docusign.net/Signing/?insession=1&ti=f53d6cb0d3f64a96a295c0be724e7e9eor what should it be shorttened to?Thanks in advance!

I have installed Docusign App Launcher in my Salesforce developer org. I am using the generate_and_convert REST API to generate the documents and then I am sending these documents using sendEnvelope method of EnvelopeService ApexToolkit. I have the requirement of getting a list of documents as and when it comes and then updating them onto an Envelope and finally send the Envelope. For this I have created an empty envelope with a recipient and sent the Envelope with Boolean false.Contact myContact = [SELECT Id,FirstName,LastName,Email,Phone FROM Contact WHERE Name = 'Test Contact']; dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity('mysourceId'))    .withRecipients(new List<dfsle.Recipient> {        dfsle.Recipient.fromSource(            myContact.FirstName + ' ' + myContact.LastName,            myContact.Email,            myContact.Phone,            'Signer 1',            new df

Hello! I’m currently automating our contract generation process using DocuGen (DocuSign eSignature) but have recently encountered an issue. Specifically, when I populate a text field (e.g., {{test_field}}), the field no longer accepts line breaks. This functionality was working correctly about a week ago. Could you please advise me on how to resolve this issue? Thank you!

Hi everyone,I’m trying to integrate with the eSignature API with a product that has Docusign integration, but it might be old because it requires a PFX file.Is anyone able to help confirm whether integration with eSignature using a PFX file is still available?If so, does anyone know how to obtain the PFX file? We have the public and private key files, as well as the certificate, but the generated PFX (using open SSL) does not work.ThanksMike 

The files are downloading but the document does not show the signatures, the filled fields are blank. I want the complete document, with the filled fields and the signatures, can someone help me? my code:  app.get('/envelope/:envelopeId/documents', async (req, res) => {  await checkToken(req);  let envelopesApi = getEnvelopesApi(req);  const { envelopeId } = req.params;   try {    let results = await envelopesApi.listDocuments(process.env.ACCOUNT_ID, envelopeId, null);       res.json({      envelopeId: results.envelopeId,      docum

I created a template with a SignerAttachmentTab (optional) inside it on Docusign.Before creating an envelope, I get the SignerAttachmentTabs of a signer and override the value of the property Optional to make it become required.But when I sent an envelope, the UI was confusing me. There were 2 overlapping tabs.Do you guys know a better way to control the property Optional before creating an envelope?

I have been trying to place signature image directly without having the user to sign it. I have used sign here tabs and added stamp tabs in it. But in the received document, it is still expecting the user to manually sign it.I have researched enough,I am not finding any resource which solves my problem.here is the code took some help from AI. This does seem to work. Is it even possible to achieve this? If yes, how?```args = { "account_id": jwt_values["api_account_id"], "base_path": jwt_values["base_path"], "access_token": jwt_values["access_token"],}api_client = create_api_client( base_path=args["base_path"], access_token=args["access_token"],)env = EnvelopeDefinition( email_subject="Please sign this document set",)env.documents = []document2 = Document( # create the DocuSign document object document_base64=base64.b64encode(fi

I’m trying to generate a document with parameterized where i’m creating a template when it doesn’t already exist, generate the envelope, and update the fields.The fields in the document are being set as {{FieldName}} as suggested by documentation, but the GetEnvelopeDocGenFormFields() for the envelope is returning no fields and any attempt to use the update throws an error.i’ve added a simple version of my code bellow.How is the sender field parameterization supposed work?    public async Task TestCode()    {        var fileName = "test_document";        string docBase64;        using (FileStream fs = new FileStream($"E:\\{fileName}.docx", FileMode.Open, FileAccess.Read))        {            using (var ms = new MemoryStream())            {                fs.CopyTo(ms);                var bytes = ms.ToArray();                docB

How to reproduce my bug : Generate a enveloppeView Sign the enveloppe The signing.on(‘sessionEnd’) isn’t triggered I was a valid docusign integration and it works on dev environnment