Developer

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,                            }                        }              

I have a template that I would like to pass data into before sending for signature. i see some fields in the template now but can’t update them. I would also like to add new fields. I’ve looked everywhere but can’t figure out how to do that. Can someone point me in the right direction?I am using laravel php, and have built a service to the template in an envelop as well as a webhook that is updated when the document is signed, so I know I am close. I would say I was tearing my hair out about this but I am bald.

Hi TeamHow DocuSign manages the data of different customers in  Multi-tenant developer account for ISV . 

I’m trying to get the access token.URI: https://account-d.docusign.com/oauth/tokenheaderAuthorization: base64 encoded of integration and secret.bodygrant_type: authorization_codecode: Code from the auth response. But I got the reply {    "error": "invalid_grant",    "error_description": "unsupported_grant_type"} Any idea what I’ve done wrong?

I am trying make a http callout to the genAndConvertEnvelopes Api to generate a document and save it back to Salesforce and it is failing to due to the below error:System.StringException: Unrecognized base64 character:Apex code below can anyone help?public class docusignGen_And_API {       @InvocableMethod(label='docusignGen_And_API')    public static List<String> sendEnvelope(List<String> record) {        System.debug(record);          Id recordId = record[0];        System.debug(recordId);        gen_and_convert(recordId);        return Null;    }        @future(callout = true)      public static void gen_and_convert(Id recordId){                       String jsonBody = bodyJSON(recordId);          System.debug(jsonBody);         HttpRequest req = new HttpRequest();        req.setEndpoint('callout:{namedCredential/restapi/v2.1/accounts/{accountId}/envelopes/generate_and_convert');        req.setHeader('Content-Type', 'application/json');        req.setMethod('POST');     

I have an Outlook add-in that saves an email from a mail folder to a .MSG file and moves it to a case management system.  Some messages are not exporting. One common factor is DocuSign.  I’ve tested this successfully with my own DocuSign notifications (as a recipient). I’m wondering if DocuSign has a security setting that might be blocking the saving of the email as MSG.Is anyone aware of such a setting within DocuSign?

We have a record triggered flow that no user will be involved in. A web form will be coming in from our website and trigger the flow and if it meets certain criteria we want a DocuSign envelope to be sent to the two email addresses we have gathered in the process.  Again, we will not have a user clicking a button or interacting with the template/envelope at all.When I test my flow, I get no errors but I also cannot find the DocuSign envelope that was created. We are using the standard ‘Send with DocuSign’ apex action within the flow. Is there a way to troubleshoot the standard apex action?  

Hello! I have a node.js application. I need 1 template. At any time I will want to fill out the data in this template, after that create a link for the user to sign in DocuSign. Also I want to receive a call back after successful signing.I don’t understand how to implement it in node.js

We have created Docusign template in Docusign Developer account and fetched this template in Salesforce Org via Omnistudio docusign setup. The latest template was fetched in Salesforce org, we have invoked this template for e-signature in Omniscript Using Docusign envelope action element and have also invoked the respective data raptor transform which should ideally dynamically populate the data in Docusign Template when the data label is same as data raptor Transform Docusign Output field. Currently the values from DR Transform are not populated though DR transform is returning the required data.

We bought an account form docusign. we cant able to create apps or integration key in API and Keys.

Hi I am facing these kind of issues  {    "error": "invalid_grant",    "error_description": "no_valid_keys_or_signatures"}in jwt token to get Access tokeni give prpoer integration , secreat and private key but facing same issues so, how can i solve that oneSo any one have a sample application for jwt grant type , please send as the zip format

Error while requesting server, received a non successful HTTP code with response Body: {"error":"invalid_grant","error_description":"user_not_found"} getting in preproduction

Hi,I have recently signed up to the sandbox version of Docusign as I want to get up to speed with some of the functionality. A colleague of mine is also using the sandbox version as we would like to collaborate on some of tests. Unfortunately, despite numerous attempts to collaborate in the sandbox version e.g. add each other as contacts/users/send emails/share templates, we have not been able to do so. I would like to understand whether the sandbox version of Docusign allows colleagues to collaborate on it? If so, what steps do we need to take to ensure we’re both using / viewing the same version (as none of our attempts so far have worked)? Please note: we already have a Docusign account for our organisation (which we prefer not to run numerous tests on), hence the sandbox version is to try out different tests outside of the account. Thank you,Emma

My integration was working fine, but now I'm getting the following error:error: 'invalid_grant' error_description: 'no_valid_keys_or_signatures'Has the Docusign integration undergone any updates that I need to fix in my application?Everything was working fine, and the documentation doesn't have clear information about the error.This is the function and the error response when accessing results from:const result = await axios.post(https://account-d.docusign.com/oauth/token, {   grant_type: "urn:ietf:params:oauth:grant-type:jwt-bearer",   assertion: token }); **The token was generated correctly with no errors using the following code and using the private key generated in the application.**It seems that everything is okay with the token. It has an exp field and other fields are valid.{ "iss": "e928cdc2-424f-4f40-a5f0-a9de31184d91", "sub": "d19b282f-a65c-4302-b08e-3ea5cd7e3167", "aud": "account-d.docusign.com", "iat": 1711921494, "exp": 2532368131, "scope": "signature"}Code:try {