eSignature API

Hi All,In my document i have an anchor string “I:” in multiple places and the connector is adding at all places where it finds “I:”, but when I try to enter some values in those text boxes, same value is being taken automatically in every text boxes in the document. Sample ImageI entered - Test2 in the first text box and same value is being auto populated in other two text boxes as well. Can anyone help me on the same? RegardsSasikanth

Hi Community ,while integrating with UiPath application , while first time authentication with DocuSIgn getting below error  Redirect URI was provided while creating integration key i.e http://localhost Let me know if anyone help me to fix this ! 

I’m trying to open a new tab from my application, allowing to an user sign an agreement. I have follow the tutorials, consult the API, test it with the API Explorer, and I’m not getting that the sign appear in the returned URL. I make two requests:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/list/ https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createrecipient/The first one gives me all information I need to make the second one:{userName: “name”,email: “valid@email

In the developer console, I can download a csv file with a  envelope.Is there a rest api that can download the csv?  

Hello, We’ve been asked to integrate eSignature in one of our internal web applications (named Talent) so our users can sign electronically during annual assessments.I’m in charge for integrating DocuSign in Talent using Authorization Code Grant flow. I have followed the example provided in GitHub and added another AuthenticationScheme in the client as the default one is already used.However, I met a CORS issue when calling DocuSign as a preflight request was sent before the original request and failed as the header “Access-Control-Allow-Origin” was missing.In my first attempt, I tried to enable CORS in the integration application from DocuSign “My Keys and Apps”, not working, then I implemented a CORS middleware following Microsoft documentation, but it didn’t solve my problem. So I need some guidance to implement the authentication to DocuSign correctly.The architecture of our application is 3-tier architecture: one client-server web application

I had a scripted CUstom button, then undeployed this script and disabled it in the Config page.  Now there is only 1 custom button enabled, the UI Custom button.  I am not sure how or what the trigger was added on the UI custom button and now hides it whenever the button is clicked (signing into Docusign).   How do we make the “SS Send Credit App” button not hidden on the Customer form after logging into Docusign?  or which scripts may have been impacted? 

Hi team,i have this error:Error:"Error while requesting server, received a non-successful HTTP code [400]"Response Body:O:8:"stdClass":2:{s:5:"error";s:13:"invalid_grant";s:17:"error_description";s:16:"issuer_not_found";}We have created both the public and private keys, using the private key for authentication. We have also used the user ID and Integration Key, and the connection server set to account-d.docusign.com. It seems that we do not have the necessary permissions to connect.Could you please assist in resolving this issue?Thank you!

I tried to follow these page to get the access token from JWT.this is what i dofollow this link https://account-d.docusign.com/oauth/auth?response_type=code&scope=impersonation signature click.manage click.send&client_id=xxxxxxxxxxxxxx&redirect_uri=http://localhost Click allow access Got redirected through 

Product - ESignature.On the API, can i create an envelope with out having a signer. I want to build a feature for secured file drop.

I want to use the DocuSign API to send different custom emails to different recipients of the same envelope. I gather this can be done in normal cases using the emailNotification parameter when creating a signer recipient, but I’m sending custom-branded HTML emails using an email resource file. When I try sending a test envelope with the parameter - "signers":[{..."emailNotification":{"emailBody":"TEST EMAIL BODY","emailSubject":"TEST EMAIL SUBJECT"}}] - it’s ignored and I get the regular branded email from my resource file.Is there a way to create separate emails for different recipients of the same envelope while using an email resource file? Should I be able to insert custom text within EnvelopeActivation_HtmlBody in the resource file using [[Data:emailnotification.emai

Hey there,I’m looking to create documents dynamically using the DocuSign API. Since the content of these documents is generated dynamically, the number of pages can vary significantly. I would like to know if there is a solution that allows for automatically placing a signature field at the end of each page, regardless of the total page count.Is there a method or feature within the API that enables this functionality? Thank you in advance

I have signer and witness. When signer starts signing, he gets popup window to enter witness information.The Envelope has Witness name and email populated.Q1. How to do this if I don’t have Witness info to populate envelope?Q2. How to do this if I don’t have Second Signer info to populate envelope?I found this:Is it possible for the signer to assign someone as a witness? | Community (docusign.com)The reference link is dead, however.So not sure what to do with Agent.Working in C#.

Hi y'all.I am creating an automation (using Node.js) for a client. The client is in the construction business and need to sign some PDF forms along with their customers.The first document is the county's permit. Where the customer (property owner), the constructor company (my client) and a notary needs to sign.My automation is already fulfilling and pdf template with data that comes from X sources. After this step, I will required the customer's (property owner) signature. My PDF has a signature field: `Signature4`, as you can see in the image. I am usign docusign-esign SDK for Node.js, and I am already able to authenticate and create the envelope.For now, the recipient number 1 (the property owner) is set to be a temporary email that I have here. In production, this is going to be the rea

I'm working on a Docusign integration, on our use case the document(s) to sign are submited to an ERP by UserA and are to be signed by UserB. UserB should be notified by email that he/she has a document to sign and have access to a link that allows him/her to access Docusign and sign the document. We're planning to use the 'remote signature request or remote signing' eSignature approach (as documented in https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-email-remote/). Is it the right approach for our use case?

Hello Team,We have a usecase where in we need to send multiple documents to different set of recipients.Doc 1 --> Signer 1, Signer 2, Signer 3 | Carbon Copy to User1, User2  Doc 2 --> Signer 1, Signer 4, Signer 5 | Carbon Copy to User2, User3Doc 3 --> Signer 4, Signer 2, Signer 6 | Carbon Copy to User1, User3Doc 4 --> Signer 5, Signer 2, Signer 1 | Carbon Copy to User4, User5The signers and carbon copy users should see only those documents for which they are signers or CC and other documents should not be visible to them.We have explored the Recipient Document Visibility but this cannot be used as Signers and CC users will be overlapping in our use case.Have explored Bulk send also but there we are sending same document to multiple recipients.So for our case we will have to create separate Envelopes for each of the Document, with signers and CC users. Is it possible to create and send multiple Envel

Hi Community,I have a question related to authenticity and potential misuse of ISV license e-sign. If the ISV license and contract signing is done by a partner with the customer at the partner location using the tablet screen (collection of e-sign) and thereafter enabling customer to click the acceptance of terms on the document, is there a possibility of misuse of the e-sign collected by the partner in future as they had collected the e-sign and potentially stored it in their system? Also only post completion of the signing at partner location, the customer has got the completed document emailed to them. Please advise, thanks!  

How to configure Envelope to have First signer sign in Focused View and Second one sign through the Email sent after the First one? I can have one signer sign in Focused View and Two Signers sign through the Email. Can’t do First focused and Second email.Working with c#.

What’s the BaseURL should be used in if we want to use the docusign admin api.I have tried all the ways please help me out.

Hi everyone,I’ve implemented DocuSign in my Laravel application, and I’m currently using JWT Grant Authentication for sending documents to clients for signing. The integration is working fine, but I’ve encountered an issue: When I send envelopes with documents for clients to sign, initially, I have to manually provide consent via the DocuSign consent page.Since my application is designed to function as a backend microservice that sends documents automatically via triggers, this manual consent process interrupts the flow. I’d like to ask if there’s a way to automate this consent process, so the documents can be sent without the need for manual intervention.Is there any configuration or API feature that allows automatic consent or pre-authorization for the app, or any best practices around this when using DocuSign in such a backend service?Thanks in advance for any advice or suggestions!

Hi All,Our admin setting is currently set to "Any Recipient Must Authenticate On Any Envelope."I want to automate a process where, after an envelope is sent, only the signers are required to authenticate, while Carbon Copy recipients are not. I understand that an envelope can only be corrected after it's sent, so my question is: how can I correct an envelope using the API, and is it possible to update the authentication requirements for CC recipients? I haven't found a way to do this directly in DocuSign.

Can we download the IDV Evidence using API while envelope is still in progress

Hello everyone!I'm using the eSignature API, and recently all my code has been running into issues with the RSA Private Key. I tried running the standard QuickStart code, but it has the same problem. The error message is: ValueError: Unable to load PEM file. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details. MalformedFraming.All my code used to work just fine, but now this issue keeps happening. Has anyone else experienced the same problem?

I have a document with five signers and would like to retrieve the partially signed document after the first two signers have completed their signing. Is it possible to obtain the partially signed document through the API?

Hello,  We are unable to fill the customfields of a template when we try to send an envelope on Docusign API REST.The endpoint we are using is: {{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesThe body is the following: {  "templateId": "xxxxxxxx-4240-4951-bdb1-f43315509f6e",  "templateRoles": [    {      "roleName": "Signer",      "name": "Test Name",      "email": "test@test.com",      "tabs": {        "textTabs": [          {            "tabLabel": "Custom1",            "name": "Custom1",            "value": "Esto es el custom 1",            "documentId": "1",            "pageNumber": "1"          }        ]      }    }  ],  "status": "sent"} 

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