eSignature API

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();                docBase64 = Convert.ToBase64String(bytes);            }        }        // Add Template        var template = await templatesApi.CreateTemplateAsync(accountId, new

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 

Are these url s correct? $baseUrl = "na3.docusign.net/restapi";$consentUrl = "https://account.docusign.com/oauth/auth?response_type=code&scope=$scope&client_id=$clientId&redirect_uri=$redirectUri"; the JWT headers$payload = [        'iss' => $clientId,        'sub' => $apiUserId,        'aud' => 'account.docusign.com',        'scope' => 'signature impersonation',        'iat' => $now,        'exp' => $now + 3600 // 1 hour expiration    ]; $tokenUrl = "https://account.docusign.com/oauth/token";$config=$apiClient->getConfig();    $config->setHost('https://na3.docusign.net/restapi');

I’m getting “USER_AUTHENTICATION_FAILED: One or both of Username and Password are invalid. Invalid access token” when I call create_envelope.I know the access token is correct after it’s generated because “get_user_info” is returning the correct account id and username, but by the time I try to create the envelope, it says the access token is invalid.in the code below, after “request_jwt_user_token”, the print commands are displaying the correct account id and username.I have been stuck on this issue for a few days now and any help would be GREATLY appreciated!Code:import base64from cryptography.hazmat.primitives import serializationfrom docusign_esign import ( ApiClient, EnvelopesApi, EnvelopeDefinition, Signer, Tabs, SignHere, InitialHere, Recipients, Document,)from docusign_esign.client.api_exception import ApiExceptionfrom django.conf import settingsscopes = ["signature", "impersonation"]base_url = settings.DOCUSIGN_BASE_URLintegration_key = settings.DOCU

I am building a SMS extension app for workflow when customer add a step to send a SMS ,the custom UI will get open where he add the number to which he wants to send SMS and the message body? as well as I want to fetch the contacts from the DB which already present in my DB to show him in a dropdown options for sending message? 

When using the “combined” API option on Java SDK I don’t get the certificate of completion bundled on the PDF. But, If I use the “archive” option I get a ZIP file with the documents and the CoC.I need to get the CoC with the compleated action, how to do this? The documentation on the EnvelopesAPI to download documents  “getDocument" states:You can also use this method to retrieve a PDF containing the combined content of all documents and the certificate [...] To retrieve the combined content replace the `{documentId}` parameter in the endpoint with `combined` the blog says the same thing:If you choose to download a combined file, you can either get a single large PDF file that includes all your signed documents one after the other, or you can get a ZIP file that contains the documents inside. In either case the Certificate of Completion (CoC) is also included as the final document. The Certificate of Completion is a document that outlines all the activity pertaining to this particular

I'm working on a new application that has integration to Docusign to allow customer to sign documents using the embedded flow. The way it works is we generate the signature URL and show it inside a modal so customers can sign without leaving our application.So far so good. Everything was working properly until we promoted the application to production.All of a sudden we've started to see {"error": "consent required"} errors in the call that generates the access token that is used in the envelope api calls. Our application is written in Python and we are using the request_jwt_user_token function in the Python SDK. I'm clueless as to why this is working in staging but not in production. I've updated all the necessary parameters with their production values but I'm not able to authenticate successfully 🤔

I'm working with a template and I want to add an attachment to it, but this error is returned. Here's the code:  let document1;   try {    let response = await fetch(anexoFuncionario);     if (!response.ok) throw new Error('Erro ao baixar o arquivo');    let contentType = response.headers.get('content-type');    let fileExtension = 'pdf';     if (contentType.includes('image/png')) fileExtension = 'png';    else if (contentType.includes('image/jpeg')) fileExtension = 'jpg';     let arrayBuffer = await response.arrayBuffer();    let base64FileContent = Buffer.from(arrayBuffer).toString('base64');     document1 = new docusign.Document();    document1.documentBase64 = base64FileContent;    document1.name = 'Anexo do Funcionário';    document1.fileExtension = fileExtension;    document1.documentId = '2';   } catch (error) {    console.error('Erro ao processar o anexo:', error);    return res.status(500).send('Erro ao processar o anexo');  }   let signerFunc1 = docusign.TemplateRole.construc

I have a web app in PHP and JS for front. I am connecting to Dcusign through the JWT and exchanging it for an access token, but i keep getting this error "Decoding JWT did not workUnexpectedValueException: "kid" invalid, unable to lookup correct key in /html/htdocs/mrt_dgheorghe/vendor/firebase/php-jwt/src/JWT.php:477"The code for JWT looks like this: $payload = [ 'iss' => $clientId, 'sub' => $apiUserId, 'aud' => 'account-d.docusign.com', 'scope' => 'signature impersonation', 'iat' => $now, 'exp' => $now + 3600 // 1 hour expiration ]; $privateKey = file_get_contents($privateKeyFilePath); $jwt = JWT::encode($payload, $privateKey, 'RS256', $keypairID); //kid $publicKey=file_get_contents('publicKey.key'); try{ $decodedJWT=JWT::decode($jwt,$publicKey); print_r($decodedJWT); echo "This is the decoded JWT"; }catch(Exception $e){ echo "Decoding JWT did not work"; print($e);Is the kid the equivale

When fetching envelope details based on filters using ListStatusChanges, the request contains customField as the account number and folderIds as sentitems, with include = "custom_fields" (to retrieve other custom field values).Before executing this request, we call the token API, but the token creation sometimes returns a non-successful HTTP code, though not all the time.What could be the issue? We are implementing it as mentioned below.var _apiClient = new ApiClient(_baseurl);token = _apiClient.RequestJWTUserToken(_integratorKey, _userID, _baseurl, Encoding.UTF8.GetBytes(PrivateKey), 1, Scopes);TokenGeneratedAt = DateTime.Now;

Hello, We were getting ready to “Go-Live” with our first DocuSign integration but when we went to start the process, it is showing that we don’t have 20 consecutive Api calls. Upon closer review, it looks like the “GetUsers” endpoint (list | REST API | Docusign) is registering as Failed when it cannot find a user. This doesn’t make sense because it is still a successful call is it not? We are using this to check and see if the user exists before creating the signature request. If they do not exist then we call the user Add API.  Any insights into this? Is there a better approach that I am missing? Or do we just need to get past this initial fail and run multiple more tests to get to 20 consecutive successful calls?

Things I have tried so far -Define the connect configuration at the Docusign Admin to list all the events to trigger the webhook. - This approach works but it expects the callback url to be static. But I would require the callback url to be generated specific for the server environment.(dev.test.com/callback-url, stage.test.com/callback-url etc. ) Hence this is not an option for me. Tried to set the envelopeEvents and RecipientEvents in the envelope definition. like below but its not triggering the events on complete/decline of signing.  const envelopeDefinition = new docusign.EnvelopeDefinition(); envelopeDefinition.emailSubject = this.template.emailSubject; envelopeDefinition.documents = this.template.documents; envelopeDefinition.recipients = new docusign.Recipients(); envelopeDefinition.recipients.signers = [signer]; envelopeDefinition.status = 'sent'; let eventNotification = new docusign.EventNotification();

Our users do not appear to have the option to create dashboards. Is this a feature available and if so how do we get them set up so that they can?  Currently they just see the standard contracts dashboard but need widgets added to it, BUT all users do not need to see those widgets.

I have a template with three roles and the order I want to keep is:Role 1: Needs to View Role 2: Needs to Sign Role 3: Needs to SignMy ideal workflow consists of the role 1 viewing the document and only after the approval, the envelope is sent to role 2 and 3 for signatures. However, I noticed that as soon as the role 1 opens the envelope, role 2 also receives the notification.How can I prevent role 2 from receiving the envelope notification while the role 1 is still reviewing it? Should I actually set role 1 as Needs to Sign and request the consent via an Approve button? Thanks!

Hello, Is there an option to customize the email subject and instruction text to include for an Agency as a specified recipient via the API.Something like below: "Please fill in your details if you are the signatory for this contract. If you are not, please add the recipient's details who should be signing.Note: If you close this dialogue box without entering any details, you will need to reopen the email to add the assignee's information." Thanks,Swami

Hi Team, I want to fetch custom folder of all user(DS-Admin and DS-Sender) created under same account.While I am trying to all get folder with List API (/restapi/v2.1/accounts/{accountId}/folders?include=envelope_folders,template_folders,shared_tempalte_folders ) with this I am only getting admin folders. Please provide any solution to fetch list of Folder. Thanks,Sneha

Hello. We are hitting the /accounts endpoint to try get a few details about our subscription from the API, and but are receiving unexpected results.We are making a GET call to the /v2.1/accounts/{accountId} endpoint in order to report on billingPeriodEnvelopesAllowed. We are receiving a non-numeric value back, when we are were expecting to get the number of envelopes that are allocated to that account.  We subsequently attempted to make a GET call to the /v2.1/accounts/{accountId}/billing_charges endpoint to verify what was in the includedQuantity  and allowedQuantity values, which also didn’t return the expected result. My questions are:Is there a better definition for what should be returned in those values? Is there a known way to get the number of envelopes allocated to a given Docusign account via the API?

Our HR team is looking for a solution for getting new employees to sign the necessary documents. Would it be possible to create a workflow in Netsuite that sends a specific set of documents to a given email address for the employee to sign?

We're sending contracts to our clients and want the date to be automatically applied alongside their signature, without requiring a separate date field. How can we achieve this?We explored the ‘Signing Settings’ option in the admin portal but couldn’t find the "Show signing date in signature" option. Could this be related to our subscription plan, or can it be enabled by requesting support?

I have created document through rendering dynamic html content, and then converting into pdf through pdfkit library and sending though Api , after receiving  document on email  to review, and signing the document, I want to redirect to one of my application page, currently it is showing docusign signup page, but i want to redirect to my application page .I have somewhere read about redirectUrl concept, can anyone let me know full process for this.If any one can go through process to let me understand 

I’m looking into the possibility of merging together two (or more) server templates into a single PDF; currently I’m creating envelopes through Python and using Composite Templates. The envelope structure I have so far makes it so that each Composite Template results in a single PDF; each Composite Template has its own Server Template and/or Inline Template, depending on the specific template I need to use -- now, what I need (but isn’t working) is something like this (taken from another post): { "emailSubject": "DocuSign Widget Order, Signature and NDA", "emailBlurb": "Please let us know if you have any questions.", "status": "sent", "compositeTemplates": [ { "serverTemplates": [ { "sequence": "1", "templateId": "{{NDA Template}}" }, { "sequence": "2", "templateId": "{{Signature Template}}" } <-- this used to be a separate Composite Template object ], "inlineTemplates": [ { "sequen

I am referring to the IAM Core - Professional Edition plan.In our case, we intend to use the Salesforce Extension App along with Maestro. Do we need to purchase the DocuSign Salesforce Connector add-on ?

A former employee created a custom field integration to add the start date to a docusign agreement. I updated the Hubspot property to ACC Cohort Start date. It was previously just ACC Start date, and now nothing works. This is the connection on the Hubspot end:  This is the connection on the Docusign end:This is what the agreement form looks like in docusign:This is what the agreement form looks like when it’s assigned in Hubspot: Can anyone tell me what error I’ve made?

My SetupI have a user access request form built in Webflow that requires users to agree to terms and conditions. Currently, the form has a checkbox that users must check to indicate agreement.What I'm Trying to AccomplishI want to implement a legally binding electronic signature process where:The user simply checks a box to sign the terms and conditions This checkbox action is recorded as a valid electronic signature in DocuSign The signature is legally binding and creates proper audit records The entire process happens within my Webflow form without redirecting to DocuSignTechnical RequirementsThe form needs to maintain its current UX with checkbox-based acceptance Each signature needs to be properly recorded and verifiable Solution should work with Webflow's capabilities Must capture relevant metadata (timestamp, IP address, etc.) for legal validity (optional tbh)Specific QuestionsIs it possible to use DocuSign's API to record a checkbox click as an electronic signature? Can DocuSign

Hi Community,I have followed all the exact steps and configured docusign.I have provided all the table permissions, and all looks good except one error when I click on View and Sign button which is as attached. Error: “There was a problem opening the document. Please contact your administrator.” Please let me know what exactly is causing this issue and how can I resolve the issue.