eSignature API

Recipients are forced to drag & drop placeholders even though the PDF envelope contains all the docusign api tags. It should not force the recipients to drag and drop.This works as expected in my developer account but fails in my production account. I have checked the code multiple times and there does not seem to be issues with any of the related code. The pdf is being passed with all the tags.  

I want to use a different name and email ID for the envelopes I send using the DocuSign Envelope Sent API. I have tried adding a new user, setting 'Act as User' in the header, and passing the user ID of another DocuSign account. How can I do this?

I am using docusign free account to integrate it with my application , I have tries to create envelope and doing e-sign.I am getting the issue if a single recipient sign multiple times (more than 10) and finish. the signature is not visible on the document. Please help me out here , is there any limitation with free account or something i doing wrong. Please suggest. 

Hello,We are integrating DocuSign via the REST API. In our use case, we use the createSenderView method to allow an initiator to manually place signature tags in the document.However, the sender view also allows the initiator to: Replace or delete the documents, Modify the list of recipients (add/remove/change), Change the signing order, roles, etc. This is not acceptable for our workflow. We only want the initiator to place tags on the pre-uploaded document — and not be able to edit recipients or the document itself.Question: Is there a way (via configuration, permissions, roles, or account settings) to restrict what the user can do in the sender view?If not, could you please suggest an alternative approach where: The document is fixed (read-only), Recipients are fixed, The initiator can only place fields (tabs)? Thank you!

Set the ExpireEnabled, ExpireAfter and ExpireDateTime using Docusign SDK 8 for C# and its not taking the values. Key points :Using Docusing SDK 8 with C# Using developer accountI’m creating the envelope from a template.I changed the expiration days in docuSign settingsThese are the lines of code :   // Get the envelope definition after configuration var envelopeDefinition = config.GetEnvelopeDefinition(); // Set the envelope status to "sent". The signer will get an email from DocuSign envelopeDefinition.Status = "sent"; // Set expiration date envelopeDefinition.ExpireEnabled = "true"; // Enable expiration envelopeDefinition.ExpireDateTime = DateTimeOffset.UtcNow.AddDays(14).ToString(); envelopeDefinition.ExpireAfter = "14"; // Set expiration days // Initialize the EnvelopesApi client (reuse existing ApiClient) EnvelopesApi envelopesApi = new(this.ApiClient); // Create the envelope on DocuSign (it will not be sent due to the "created" status) EnvelopeSummary envelopeSummary = envelopesA

Using methods of DocuSign.eSign.dll in a Window Service , developed with C# and targeted to .NET framework 4.7.2 you got a seemingly endless number  of runtime exceptions like ‘Could not load file or assembly 'System.Memory, Version=4.0.1.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.’When you fix the the dependency exception e.g. for Microsoft.IdentityModel.Tokens.dll a new problem with Microsoft.IdentityModel.Logging.dll shows up and then with Microsoft.IdentityModel.JsonWebTokens.dll an so on.Even the latest version of DocuSign.eSign.dll (8.1.0.0) seems to depend on older or deprecated versions of system dlls.Has anyone already had to deal with this problem ? 

I’m getting this error when obtaining the access token through the /oauth/token endpoint:{"error": "invalid_grant", "error_description": "invalid_user_siteid"}I couldn’t find any info in the Troubleshooting Common Errors. What does this error mean and how do we address this? 

Received dependency version mismatch error while trying to import “DocuSign.eSign.dll” version 8.1.0.While downloaded “DocuSign.eSign.dll” (version 8.1.0) using .NET NuGet Package Manager, the version of “System.Numerics.Vectors.dll” downloaded was “4.1.4.0”. But when tried to import that “DocuSign.eSign.dll” (version 8.1.0) to our product, got an error as “System.Numerics.Vectors.dll” version “4.1.3.0” is missing.Unable to get any reference of the version 4.1.3.0 for “System.Numerics.Vectors.dll”.Please help to this dependency version mismatch error for “DocuSign.eSign.dll”. Error Message: “Could not load file or assembly ‘System.Numerics.Vectors, Version=4.1.3.0’ or one of its dependencies. The system cannot find the file specified.”

I am trying to create an application with DocuSign Connect. In DocuSign Connect I have enabled Include Basic Authentication Header, but still I am not able to make a call on the URL provided. I checked the logs on the server and the request reached the server but was rejected because of invalid credentials.I am able to make a call to the URL from postman with the same username and password. Am I missing some settings here? Is DocuSign not sending the authentication in the header as “Basic <Credentials>” or is it doing something else? Thanks in advance.

My integration key is currently in development and we’re getting ready to submit for review to move into production. However, we need to continue testing with they key until go live. Once the key is moved into production, will I still be able to use it in the test environment? How long does the approval generally take to promote the key to prod?

Hi everyone,I'm running into an issue when making API calls to DocuSign using our SOAP client. Specifically:Not all the tab values we're setting are being sent in the request. Even when we explicitly define certain tab types (e.g., RadioButton), they appear to default to simple text fields in the envelope.I've attached an example of a radio tab configured prior to the payload, along with a Fiddler capture showing the request being sent.Has anyone run into similar behavior or have suggestions on what to check? Any help is appreciated! Fiddler outputRadio Tab configuration 

Hello, In my Django app, we can create and edit a docuisgn template internally. I am using the embedded url. It works great, but there are a few tweaks. Safari does not like iframes for example. And the return url in dev mode can be a challenge. But in production it works. I am looking to harden the approach. I have added a few things like a side bar menu to help with guiding people through the process. Stuff like that. Does anyone have an experiences with this approach that they would like to share? thank you. Paul.

I am developing a React Native application where I need to implement document signing functionality for PDF files. The requirement is to allow users to upload a PDF from their device and sign it using DocuSign. However, I want to achieve this without creating or managing an envelope in DocuSign.Is there a way to directly sign a PDF document within my React Native app without involving the envelope process?

Hello,I'm currently using the DocuSign Java SDK (docusign-esign-java) version 6.0.0 to call the createEditView method from the TemplatesApi class, as shown below:templateViewRequest.setReturnUrl(returnUrl);templateViewRequest.setViewAccess("template");ViewUrl view = templatesApi.createEditView(accountId, templateId, templateViewRequest);I would like to hide the “Back” button on the Template Edit View screen.According to the API documentation, it's possible to customize the embedded view using the settings object (e.g., showBackButton, startingScreen, etc.), but the TemplateViewRequest class in the SDK doesn't seem to support setting this settings field.I would like to ask: Is there a way to set the settings parameter when using createEditView with the Java SDK? If not, is there a workaround or should we call the REST API directly using a custom HTTP request? Do we need to have a specific feature flag enabled on our account to use settings in view requests? Any guidance would be gre

We are using JavaAfter calling:net.docusign.api_3_0.AuthoritativeCopyExportDocuments authcopy = api.exportAuthoritativeCopy(eid)How do get I a checksum for api.acknowledgeAuthoritativeCopyExport?I’ve tried to use the Javscript example I found and covert to Java, but I am clearly missing something! var CryptoJS = require("crypto-js");var document1 = "<documentpdfbytes>";var coc = "<certificatepdfbytes>";// CryptoJSvar parseB64 = CryptoJS.enc.Base64.parse(document1);parseB64.concat(CryptoJS.enc.Base64.parse(coc));var shaB64 = CryptoJS.SHA1(parseB64);console.log("->", shaB64.toString(CryptoJS.enc.Base64));</certificatepdfbytes></documentpdfbytes>

Our company has two Docusign accounts, one of which is linked to Ironclad. Periodically, at random periods, the integration goes off and any signature process is stopped. We are obliged to log on to Docusign and relink the two apps. This behaviour is not normal, since a link validly affirmed should be permanent. If there is a periodic reset for whatever reason (e.g. security) this should be clearly stated so that the relinking of accoints can be made object of a procedure to ensure uninterrupted functionality. The issue is critical as it interruprs workflows and prevents the signature of contracts. Thank you in advance for your feedback.

Hello,We are trying to change the Account on which the Docusign eSignature/M-Files integration is running but we cannot.Right now the integration is live on Account A of a specific user and we want to move it to Account B of the same user.Even thought we changed the default account of the user and reauthenticated the user, it seems like the refresh token is still authenticated to Account A.Is there a way to force the expiration of the refresh token? Is the Connected App that we see on the user called “app.docusign.com Version 1.x” related?Thanks in advance,Christos Mouskos

When trying to download a document with the SOAP API I get: javax.xml.ws.soap.SOAPFaultException: Invalid Message SignatureI do have a signature on my accountThis occurs  using both requestPDF and exportAuthoritativeCopy APIServiceSoap api = Utils.getAPI(request);api.requestPDF(eid);api.exportAuthoritativeCopy(eid); Note: I can get the envelope:api.requestEnvelope(eid, false);  

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My server supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

I am creating an envelope using the API and adding multiple documents and using Auto-Place to add the “Sign Here” tabs. The anchor string is the same on both documents but I would like the tabs to only place on the document specified by the “DocumentId” on the tab. This does not seem to work.Here is example code using the C# SDK:Is it expected that the SignHere would be added to both documents? If so, how would I prevent that? var envelope = new EnvelopeDefinition(); Document doc1 = new Document { DocumentBase64 = doc1DocxBytesBase64, Name = "docusign-test", FileExtension = "docx", DocumentId = "1", }; Document doc2 = new Document { DocumentBase64 = doc2DocxBytesBase64, Name = "docusign-test2", FileExtension = "docx", DocumentId = "2", }; envelope.Documents = new List<Document> { doc1, doc2 }; var signer = new Signer(); signer.Name = "Test Name"; signer.Email = "test@test.com"; signer.RecipientId = "1"; SignHere signHere1 = new SignHere { AnchorString = "\\s1\\", Docume

Unable to execute ExportAuthoritiveCopy SOAP call.Get the error This User lacks sufficient permission when execute ExportAuthorativeCopy SOAP call in Java Attempting to use JAVA SOAP API in the development environment.My user account is:lucas@vsac.org I am able to perform other actions without issue but when I try to runt eh following code for ExportAuthorativeCopyAuthoritativeCopyExportDocuments authoritativeCopyExportDocuments = api.exportAuthoritativeCopy(envelopeId); I get an exception.javax.xml.ws.soap.SOAPFaultException: This User lacks sufficient permissions. Envelope:a3cd69ed-b1d8-4528-a919-0f207fb9ac92, User:9002d798-6e25-4350-b873-37f01801f058 My account appears to most all permissions needed but when I look in the development user admin screen and I'm not find anything for Authoritative Copy. The on-line Documentation says. eSignature SOAP API:Authoritative Copy in SOAP requires two features to be enabled for your account.The first is called Auto Authoritative Copy.This feat

Hi. We have a free developer API account and are using our API calls prior to going live. When sending a document to sign via DocuSign, the signer isn't able to sign from her own DocuSign account. When document is sent, there is nowhere for her to log in to her own DocuSign account to sign the document. She is only able to sign the document with a generic signature. Is this because we are only testing in the free developer API account? Once we go live, will the signer be able to log in to her DocuSign account to sign the document using her uploaded signature? Thank you. 

ok, this is my case. I’m using a template with a text fields that pre filled them using docusing sdk for C#. When i create the signerUrl using CreateRecipientView method, all is ok; but when I use CreateSenderView and the status is “sent” those text fields are empty. So, basically I want to those text fields (like, name, office, phone number) even when the status is sent or completed. Even I get the PDF document using “GetDocument” and it does not shows the text fields. Should I use another field different than a text field?The main idea is to somebody else (different than the signer) to review the document (signed or not)

Hi everyone,I’d like to automate a process between HubSpot and DocuSign where a document is sent out for signature to an external recipient (e.g. a client), without me, as the sender, being required to sign it.Here’s the situation: I’m using HubSpot to trigger workflows. I want HubSpot to automatically trigger a DocuSign envelope when a condition is met (e.g. deal stage changes). The envelope should go only to the external signer. I, the internal sender, do not need to sign the document, and ideally shouldn’t have to interact with the envelope manually. I'm concerned because my user is secured with 2FA, and I want to make sure I can still automate this securely. My questions: Is it possible to use the DocuSign integration (or API via middleware like Zapier/Make/Tray.io) to send a signature request without the sender being a signer? How would you structure the envelope and workflow to make this happen securely? Does the 2FA requirement on my account limit these automations i

i have docusign production account. can with one app created in it. is there an option to create another app ans use it to send envelopes.but app1 and app 2 callbacks should not overlap with each other