Developer

I’m been researching how to use Composite Templates now for a few weeks, and I have yet to really make sense of this. Here is my specific use case. I have several server templates created that have product specific contract language, and I have opted to create a single signature page, which has signature blocks for the service-provider, and the client, along with 2 additional optional client signature blocks. Based upon the products sold to the client, the envelope would have 1, 2 or 3 contracts (server templates), along with the signature page (also a server template). Each contract/template contains tab data that would be pre-populated by the service-provider role and sent during envelope creation. All users will be sent all documents in the envelope, and expected to sign the signature page, in recipient order. I’ve attempted to use the eSign API explorer for create:Envelope to attempt to assemble some reasonable JSON, however this tool is terribly hard to use with long scrolling bar

we have a requirement to auto populate the date signed field with the date and time stamp when the user has signed the document. Please let us know how do we do this using the REST API for creating and sending the Envelope. we see that there is a DateSigned tab on the API, but it requires us to provide a X and Y position of the date Signed field. We are not sure of the X and Y positions of the date signed field on each document which we send. Can you please let us know if there is anything better than this field to use

I am using Docusign eSignature API and I have a template which has pre-fill tabs added that are being populated with values when Document envelope is being created via API. I am using this endpoint: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocumenttabs/update/And whenever values are updated, tab is duplicated, one empty and the other one with value. The reason for using pre-fill tabs is to display information for all signers. And the problem is that sometimes I reach tab limit and envelope fails to generate. How could I solve this?

Hi! I just published a new YouTube video on setting up the Docusign for HubSpot integration.You will learn the pros and cons of both the standard and custom integration methods, how to configure each setup, and how to streamline your document workflows to save time and effort. You can find it here: PS: join me every Wednesday at 9 AM PST during a free Q&A session. Click here to register! Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

hello everyone,we use the rest api (eSignature) to send documents by email and have them signed.but now we need a kind of double signature process. i mean the following: the document should be sent to 2 people. first person 1 has to sign and only when this is done, person 2 has to sign. it is important that person 2 is only allowed to sign if person 1 has already signed.how exactly can we realise this?thank you.

I’m building a contract management system using Node.js that integrates with DocuSign. When a contract is created from the frontend, an email is sent to the customer with a document to be signed. I’ve successfully set up a trigger event using DocuSign Connect, so that once the customer signs the document, DocuSign sends a payload to a specified URL (currently pointing to a test URL from WebHook.site).Now, I need to configure my Node.js application to receive this webhook payload, allowing me to process it and perform certain database updates after a successful customer signature. What’s the best way to achieve this integration?

Hi!In my Microsoft Custom Connector, I am using https://docusign.net/restapi/v2.1/accounts/1500/envelopes/{envelopeID}/views/sender as my request URL and it takes me to this page: URL: https://apps.docusign.com/send/prepare/114937d7-2643-4a12-aa4e6f959c/add-fields However, I am in need of my request URL to access the page before that one:URL: https://apps.docusign.com/send/prepare/114937d7-2643-4a12-aa4e6f959c/ 

Hello,I call the below code from a soap call. The user I want to change to is withind my users with admin permissions. The error I get is =======================================================================            <ErrorCode xmlns="missing in Web.Config">112</ErrorCode>            <ErrorReason xmlns="missing in Web.Config">This User lacks sufficient permissions.</ErrorReason>======================================================================= I already have the Allow sender to download form data setting enabled. Code: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.docusign.net/API/3.0">          <soapenv:Header>      <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">         <wsse:UsernameToken>            <wsse:Username>[integrationKey]email</wsse:Username>            <wsse:Pass

I have created a webhook that listens for any envelope created and calls the API i configured.My intention is to open the envelope based on the details received in webhook.But in the response the complete url is not available and it has only the url path , how to construct the base urlwe recieve envelope uri as /envelopes/<envelope-id>

Please add this error “REQUEST_ENTITIY_TOO_LARGE” in the article https://developers.docusign.com/docs/esign-rest-api/esign101/error-codes/troubleshooting-common-errors/ as this issue should be resolved in the DocuSign side.

Hello Everyone!I received a request to remove all DocuSign actions from my Power Automate workflows and replace them with Custom DocuSign Connectors instead. I am having trouble replicating the Generate Embedded Sender URL. My Custom Connector has all of the attributes like the actual DocuSign connector, but mine is missing the Output Embedded Sender URL. Any ideas on how to generate it?  

When launching a DocuSign signing session from a Salesforce Community site using Lightning Web Components, the signing session initiates correctly as per the guidelines from the DocuSign site with reference of link - https://developers.docusign.com/docs/salesforce/how-to/embedded-sending-signing/. However, I am encountering an issue where the template with prefilled fields is not appearing. I have set up field mapping in the template, but the mappings do not show up on the signing page.How can I achieve this using a Lightning Web Component (LWC) with Apex?

Hi everyone I ran into this issue hopefully someone can help me outIssueWeb App with  https://test.domain1.ioLaunches iFrame in modal window to https://test.domain2.io(different domains)The iFrame app launches Docusign using Focused View and client libraries from DocuSign for end user to sign. The launch will not work and there is an error in the console showing -Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://test.domain2.io" I am following this how-to:https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/ I also put both domains (https://test.domain1.io, https://test.domain2.io, https://apps-d.docusign.com) in  frameAncestors field when creating the recipient view URL. How can we pass https://test.domain1.io to the Docusign so it will properly configure the CSP? 

Hi Adam Minow, I am trying to access0000000@000000000Account #000000 this is developer account in DocuSign, but I received a message that says I am not an administrator for this account. Could you please grant me the necessary permissions, or log in on my behalf to assist with this request? they want to connect0000000@000000000Account #0000 how to connect this is user account(post edited due to personal information) 

We have a main account and a number of sub accounts. I am trying to use the API to generate a report on number of envelopes sent without having to run reports on each manually. I just got the API going and I am running the end point: restapi/v2.1/accounts/{account id}I am getting the following information back:  'planStartDate': '2023-07-26T17:00:00.0000000Z', 'planEndDate': '2024-07-25T17:00:00.0000000Z', 'billingPeriodStartDate': '2024-10-01T07:00:00.0000000Z', 'billingPeriodEndDate': '2024-11-01T07:00:00.0000000Z', 'billingPeriodEnvelopesSent': '119', which does not match our contract dates (7/25 was months ago). Nor does it match the number of envelopes sent during the last contact (certainly not if the billing period is only this month). Thoughts? Am I interpreting this data incorrectly, or is there a better endpoint I should be using?  

Hi! I just published a new YouTube video on how to send multiple documents for signature to different people using Docusign.You will understand how to automate the entire workflow, whether you're sending the same document to multiple signers or creating a unique process for each individual, plus how to simplify using templates and automation tools. You can find it here: PS: join me every Wednesday at 9 AM PST during a free Q&A session. Click here to register! Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hi All,I downloaded a quick start java app from docusign developer portal and it was working fine till last week. When i tested today, it is not working.  It does not throw any exceptions or error.  When running the main class, the program simply terminates without providing any message or error.  The file to sign will be fetched from a local folder, convert into base64 then send it to the API functions.  When it enters the below lines of code, the entire program simply terminates and no code below these lines are getting executed. EnvelopesApi envelopesApi = new EnvelopesApi(apiClient);EnvelopeSummary results = envelopesApi.createEnvelope(accountId, envelope); Can someone please guide me on this?  

Hi,I am currently integrating DocuSign Embedded into my web application, which supports two types of users: admins and normal users. Admins have the ability to send documents to users for signing, and I have successfully implemented this functionality.However, when a user logs into our application, I want to retrieve all the documents that they need to sign. In this context, the user is the recipient of the envelopes sent by the admin.I reviewed the DocuSign APIs and found that the process involves first retrieving all envelopes and then filtering them by recipients. However, I am unsure if this is the best approach.Could you please confirm if this method is correct, or suggest a more efficient way to achieve this?Thank you!

Is DocuSign imbedded in EPIC anywhere (as Dragon or Up To Date is)?

Hi,My account has already WhatsApp enabled and I’m trying to create an envelope via API with WhatsApp as the delivery method. I send the request, the envelope creates successfully (I receive a succesful response with the envelope link and I can also see it on my dashboard, but it just says “Waiting for” and I’m not receiving the WhatsApp message from DocuSign.Documentation is very poor on this subject, there are no real examples, no info about the country code or number format: Number must include the country code also? With plus or without plus sign? With one zero before the number, two zeros? So many questions...This is my envelope definition:I’m in Spain so the country code is 34.Appreciate any help, thanks!

Hi,I’m trying with PHP but always getting this error my code like this<?phprequire_once 'vendor/autoload.php'; use DocuSign\eSign\Client\ApiClient;use DocuSign\eSign\Configuration;use DocuSign\eSign\Api\EnvelopesApi;use DocuSign\eSign\Model\EnvelopeDefinition;use DocuSign\eSign\Model\Signer;use DocuSign\eSign\Model\Recipients;use DocuSign\eSign\Model\Document;use Firebase\JWT\JWT; $integrationKey = '9eaed807-bd9f-4d38-b858-37f6eccc6b73'; // Your Integration Key$userId = 'd4300ed6-aa42-47cd-b687-01c825726abd'; // Your User ID (GUID)$privateKey = file_get_contents('key.pem'); // Path to your private key$accountId = '8c637b59-afa2-4821-8c5d-981bacf4ddde'; // Your Account ID // Set the current time and expiration time$now = time();$expiration = $now + 3600000; // Token valid for 1 hour // Create the JWT payload$payload = [    'iss' => $integrationKey,    'sub' => $userId,    'iat' => $now,    'exp' => $expiration,    'aud' => 'demo.docusign.net',  //aud: Should be set to

We are successfully using the embedded view “default” style to allow our users to sign documents, and then proceed onto the next step. However, we do allow the user to refresh the page and get back into the “signing step”, and that works well, except if it has already been signed. When the document is signed, and the page is refreshed, we successfully show the document again, and this time instead of “Sign” or “Finish”, Docusign UX displays “Close”. When that “Close” is pressed, the “endSession” event isn’t triggered as normal, but the nested iFrame is destroyed. This workflow does works well with the “focused” style in all cases (meaning that by just changing “displayFormat” to “focused” it fixes the issue), however, we would like to use the “default” UX. How could we have “endSession” trigger when pressing “Close” on an already signed document?

Hello,As an inspection company in Portugal, we issue inspection certificates and are looking to integrate this process into our ERP system (Odoo). We aim to use Advanced Electronic Signatures (AES) or Qualified Electronic Signatures (QES) for these certificates. Could you please advise on the best solution and steps to implement this integration with DocuSign, and can we use this solution by the name of company instead of personnel identity?Thank you for your assistance.

We recently encountered an issue with one of our customers while using the following API: https://eu.docusign.net/restapi/v2.1/accounts/<Account Id>/envelopes/<Envelope Id>/recipients?resend_envelope=trueWe received the following error response: {"errorCode": "ENVELOPE_CANNOT_CORRECT_INVALID_STATE", "message": "This account may not have 'correct' permission, or the envelope state is not 'sent' or 'delivered'."}We have tested this in our sandbox/dev account and did not find any specific additional permission needed to perform this action. Could you please clarify what extra permissions or access rights are required to avoid this error? If possible, could anyone provide a screenshot from the DocuSign portal showing where to configure this permission? This would be very helpful.