Developer

Hello,I'm making an API call to DocuSign to automatically insert the "date signed" into the document.Below is the API request payload:"dateSignedTabs": [    {        "anchorString": "Date",        "anchorYOffset": "-1",        "fontSize": "Size12",        "name": "Date Signed",        "recipientId": "1",        "tabLabel": "date_signed"    }]The issue is that this results in placing the date everywhere it finds the string 'Date' in the document. I want to restrict it to only one place where the actual date is needed. Any suggestions or help? Thanks,Kishor

Hello Champs,Am trying to create envelope using CreateEnvelope method from EnvelopesApi class and getting error - Error calling CreateEnvelope:. Porject designed in Dotnet core. appreciate your help. thanks.

I am going to integrate eSignature into my application, but I found that it requires JDK 11 or later, while my application is running on JDK 8. However, I can't upgrade because it might lead to uncontrollable issues in production. What should I do?

I’ve been struggling with the best way to automate one of our form workflows with Docusign and the only way I’ve found to do it is with two separate templates. I’m hoping to get some tips on using conditional routing to simplify my solution.Here is a summary.I have a purchase request form with a possibility of 3 recipients.Requester Approver PurchaserIf the form is filled out by a VP, SVP, CEO, etc. the requester completes and signs the form (In this case, the requester is also the approver). Next, the purchaser places the order, adds notes to the form, and marks it completed.If the form is filled out by an employee who is not a VP, the requester completes the form. The form is then sent to a VP for approval and then the purchaser who places the order adds notes and marks the form complete.My current solution using the DocuSign API is.The requester clicks on a link from a page on our Intranet.If the requester is determined to be a VP or above,generate an envelope from the “VP Purchase

Prezados, Estamos utilizando a API, ainda no ambiente DEV, para download de envelopes. Vamos solicitar A implantação o ambiente de produção, mas estamos com uma dúvida. Na URL para requisição é informado o ID da conta do usuário e com isso eu consigo consultar os envelopes daquela conta, a dúvida é quando essa chave de API estiver no ambiente de produção eu poderei consultar o envelope de qualquer usuário da minha instituição ou apenas os envelopes vinculados ao meu usuário? Ressalto que tenho acesso de Admin. A URL que mencionei é:requests.get('https://demo.docusign.net/restapi/v2.1/accounts/account_id/envelopes

Hi docusign community,I'm working on creating some logic to dynamically update my template with different content. When I make a GET call to pull the custom fields I've added in template, I see this:GET Request results : { "textCustomFields": [ { "fieldId": "10351158661", "name": "templateUsageRestriction", "show": "false", "required": "false", "value": "allOptions" } ], "listCustomFields": []}Does anyone know what the 'templateUsageRestriction' means and how to extract the actual fields? Are there any settings needed in my DocuSign template? 

Hello, Below is the request payload for which I’m trying to create an envelope and send it to multiple signers, but the problem is creating the envelope with a single signer.{  "documents": [    {      "documentBase64":"JVwj===" ,      "documentId": "1",      "fileExtension": "pdf",      "name": "EmploymentContractDocuSign.pdf"    }  ],  "emailSubject": "Kindly review and sign the employment contract document for Person: Test 002.2:47",  "recipients": {    "signers": [      {        "email": "test@gmail.com",         "name": " kj",         "recipientId": "22",         "routingOrder": "2",         "isBulkRecipient": true      }    ],    "signers": [      {        "email": "Test002@yopmail.com",         "name": "Test",         "recipientId": "11",         "routingOrder": "1",         "isBulkRecipient": true      }    ]  },  "status": "sent"}

I’m trying to automate sending an envelope with multiple documents attached to it. However, when the email is sent, only the 1st document is seen.documents = []index = 1for pdf in listdir(flattenedFolder): if isfile(join(flattenedFolder, pdf)) and pdf[len(pdf)-4 : len(pdf)] == '.pdf': with open(join(flattenedFolder, pdf), "rb") as file: doc_docx_bytes = file.read() doc_b64 = base64.b64encode(doc_docx_bytes).decode("ascii") document = Document( # create the DocuSign document object document_base64=doc_b64, name = pdf[0 : len(pdf)-4], file_extension="pdf", document_id = index, order=index ) index += 1 documents.append(document)envelope_definition.documents = documents 

I am sending document using apex. Sending and signing is happening properly also, document is attaching back to salesforce record once signing is completed by all parties.I also want to update field in salesforce record based on envelope status. Like this:Envelope status ='Sent' then Document__c.Envelope_Status__c='Sent'Envelope status ='Completed' then Document__c.Envelope_Status__c='Completed'.I am giving these conditions in code like below:  myEnvelope = myEnvelope.withOptions(                new dfsle.Envelope.Options(                    null,                     new dfsle.Document.WriteBack(                        recordId,                         dfsle.Document.WRITE_BACK_NAME_ENVELOPE_STATUS_PDF,                         true,                         false                      ),                                         new Map<String, Map<String, Object>>{                        dfsle.Envelope.STATUS_SENT => new Map<String, Object>{                           

Hello,We are calling the eSignature API to retrieve the template ID used in an envelope (/envelopes/xxx/templates). Sometimes these calls return empty responses whereas envelopes were using a template - see below example : Green OK - Red KOCan someone explain why templates are not retrieved correctly ?Thank you !

Hello everyone.I would like to setup a meaningful rights role concept.I would like to have users who are “only” allowed to send simple signatures, but cannot make any other settings.There should be 3 users who can also send qualified electronic signatures, while others cannot. I would also like users to be able to send letters exclusively via API.Can this be done with the setting?Thanks - and have nice weekend

How do you create and send an envelope on behalf of another user using the REST API? 

I have a DocuSign developer/sandbox account and a production account. I want to explore web forms and SMS delivery with my sandbox account. How can I get these features enabled in my sandbox account?

I’m using Docusign Envelope events:Sent Delivered Voided Declined CompletedI do have a signer & a carbon-copy as well attached to the envelope. Now, the problem is Envelope-Delivered gets triggered only when all the recipients including the carbon-copy opens it. In my case, the recipient in the carbon-copy doesn’t open until unless its completed.So, I wanted to use Recipient-Delivered event such that we can get this event when any of the recipient opens it. So that I can monitor the signer’s status & can use it accordingly.So, my actual question is if the recipient in carbon-copy opens it after the signer has signed it, do we still get the delivered trigger??

Attached sample docx seems to be corrupted after signing and trying to open via microsoft work , the docx has been signed via eSignature APIS. 

Need to clone a DocuSign account via the API? Here’s an example... POST method to {{Admin Base URL}}/v1/organizations/{{Org ID}}/assetGroups/accountClone Body:{ "sourceAccount": { "id": "624e3e00-xxxx-xxxx-xxxx-43918c520dab" }, "targetAccount": { "name": "My Cloned Account", "admin": { "firstName": "Global", "lastName": "Admin", "email": "admin@asdfasdffdsa.com" }, "region": "NA" }} 

I represent an ERP from which my customers (Business) will emit signable documents.Currently, if my customer requires a Docusign integration, we ask them to create an appdemo account so that we (, logging in with their credentials, ) can create and configure the App & Key credentials, security settings, etc. Then, when the tests are finished, they have to provide another (this time, paid) account so we can link it with their previous development account.My intention is to create the App & Keys from my Docusign enterprise account for each of these customers whenever they require a Docusign integration. Then, when I finish the mandated 20 integrated tests, I would send them the OAuth link so they can login and authorize using their subscribed account.By doing that, I intend to keep all integration keys my ERP uses in a single, managed, account.Is there an issue here? Should I not be doing that? Is this behavior expected? And if not, what are the alternatives? 

Is it possible to use the custom fields as a placeholder inside email to fill some data dynamically. So that the creator of envelope just fills in the information in the custom field and it will be used in the email body/subject etc..

I'm using Power Automate to add checkboxes to a document. The requirement is to include three checkboxes, with only one selectable at a time. How can I achieve this?

We have a request to automatically generate a docusign gen template that contains merge fields from an opportunity then automatically send it.I found this video on YouTube https://youtu.be/cjOFo_j1PS0?si=FG-Sz0Qna9dUbfq5Which uses the genAndConvertEnvelope endpoint and provides a code example in the link but I’m new to Apex and stuck as to how to use the genAndSendEnvelope end point to go one step further and send the generated document via the api.Does anyone have any apex code examples they could share or any advice on how to do it please?I would like to do it with combination of flow and invocable apex where flow passes recordId, docusign templateId (with merge fields), recipient name and email as invocable variables to the apex class then use an at future method to make the callout to generate the document, create envelope, add generated document to envelope, set recipients and then send to recipient.Has anyone done something similar?https://developers.docusign.com/docs/docgensend-

There have been 2 updates to this product this week. The first worked best for me because my most recently used template was shown on the main page but now you’ve taken it away, again. Why must your progress always include more clicks for the user? The same happened with the Outlook Add-in, so I stopped using it.  If you are going to continually change the main page, you should include user preferences for defaults so we can see what we need and not have to register multiple, useless clicks to get where we need to go. 

HelloI'm trying to integrate the signature process directly into my application.On the server side, I'm using the PHP SDK, and on the front, I'm using Docusign JS.I manage to create an envelope, retrieve the URL and initialize my HTML element (following this documentation: https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/#docusign-js).The signature process works correctly.However, I'd like to add a verification of the signer's identity by sending him an SMS.So I added the "RecipientIdentityVerification" object in my PHP.Now I have an error in my console: Content-Security-Policy: The page parameters have prevented the loading of a resource at https://verify-d.docusign.net/App/Callback ("frame-src").I've tried modifying the content security policy by adding frame-src 'self' *.docusign.net but it doesn't change anything.However, when I open the URL returned by Docusign in a new tab of my browser, I'm redirected to https://verify-d.docusign.net/App/Callback t

​I want to use invocable apex and flow to automatically generate a gen template, add it to an envelope and send it.Does anyone have any code snippets/examples they can share on how to achieve this? 

I have a requirement to populate values from my database into the attached document in the template while sending to different users dynamically via API. Any insights?

Hello,We are DocuSign C# SDK.We are configuring recipient identity verification through phone authentication with IdentityVerification < Signers < Recipient < EnvelopeDefinition We have IdentityVerification = new RecipientIdentityVerification{                WorkflowId = _signatureSettings.PhoneAuthenticationWorkflowId,                InputOptions = new List<RecipientIdentityInputOption>                {                    new RecipientIdentityInputOption                    {                        Name = "phone_number_list",                        ValueType = "PhoneNumberList",                        PhoneNumberList = new List<RecipientIdentityPhoneNumber>                        {                            new RecipientIdentityPhoneNumber                            {                                Number = signer.Phone.Number,                                CountryCode = signer.Phone.CountryCode,                            }                        }