eSignature API

Obtaining or errorHello everyone, my name is Nathan, I'm trying to deploy my integration with Docusign to production but I'm getting this error:Error message:The specified Integrator Key was not found or is disabled. Invalid account specified for user.Error code:PARTNER_AUTHENTICATION_FAILEDNote: I have already done Go Live, my app has already been approved and the environment variables have the correct production information.

My organization has a lot of existing Power Automate flows that use Adobe Sign.  I’d like to transition them to Docusign, but am hitting a huge obstacle.The flows currently work like thisGet MS Form response Populate a Microsoft Word Template (selects the doc and fills out all the template fields using the responses from the form) Send to Adobe SignThe template document referenced in step 2 has Adobe Text Tag fields such as {{Sig_es_:signer1:signature}} that identifies where Signer1’s signature should go.  I have not found any equivalent way to do this in Docusign.  I’m really surprised that this would be so difficult.  There’s no text tags I can add to the document that will tell Docusign where I want the signatures to go?  I attempted to make to something like this: 

Hi Team, We have implement Docusign integration with Dynamics with client, Currently the setup is in DEMO environment as we are still in Development and UAT phase. The workflow was working fine until day before yesterday, howeever it started throwing an error at Add Documents step. Object reference not setPlugin Trace logs has the same error as above.  Has anyone faced this issue? 

A few days ago, my work colleague created a developer account. Everything worked for several days without any problems, envelopes could be created and emails went out. Since yesterday no more emails have arrived. We have tried several email addresses with several providers, spam folders are empty. DocuSign says email is out but nothing arrives at any of them.I have also just created an account and generated a demo app for C#. The same behaviour, I enter the data in the console, a message appears that everything has been sent successfully, but nothing arrives at any recipient.Are there any problems with the test accounts at the moment?

I have a requirement to wrap the Print & Sign flow into my custom app. I need to be able to download the document for an offline Wet Signature and then Upload the signed document upon completion.I have set EnableWetSign to “true” on the EnvelopeDefinition.   I am not finding the Api calls to download and upload the document.  Do they exist and if so, where can I find a reference for these activities?

 anyone know what this means // how to create a new envelope despite this?

Hello DocuSign Community,We’re integrating DocuSign with our internal system via the REST API and encountered an issue with controlling permissions in Sender View.What works: We successfully create an envelope via API with attached documents. The envelope remains in created status, as intended. We then create a Sender View (embedded) using the CreateSenderView API call. Our goal:We want the sender to add tabs (fields) for other recipients, but not be able to: Edit or remove the document itself Add/remove recipients Change routing or envelope metadata What we tried:

Whether anchor tags work in PDF generated from EJS templates? Are there any known limitations in parsing anchors in dynamic PDF files? Any best practices for using anchor tabs in a dynamically generated PDF?

I'm trying to create an envelope using a template and then modify it to add Identity Verification. However, the envelope created earlier doesn't overwrite the existing signer role, even though I'm making the request with the same role name.Does anyone know why this might be happening or how to properly update the role?

I am trying to invoke create envelope endpoint using http request from my application and getting connection reset by peer.Following is the account id account_id: c4de313b-e2ac-4a31-9902-4253b58fb133 Exception :o.apache.http.impl.execchain.RetryExec : I/O exception (java.net.SocketException) caught when processing request to {s}->https://demo.docusign.net:443: Connection reset by peer   

Hi there,Scenario: I have an envelope template 5 recipients, and multiple documents 5-15, the documents contain fields using anchors, multiple fields are repeating inside documents (same Data Label), including fields like SignHere and FullName. Using API a draft envelope is created from template, with fulfilling value for tabs.Problem: Even if the total number of tabs not exceeding 450, while creating envelope we receive error `TAB_LIMIT_EXCEEDED`, when the tabs limit per envelope is 5000.Attempts: When I remove all fields, the creation works. After removing few documents from template (~180 tabs remain) it goes through.Since template creation is responsibility of law department, we can’t limit them in numbers of documents or fields used, (the DocuSign limits are ok)Any ideas how to investigate and what can be the issue of this problem?

Hello DocuSign Team, can you please help us with the pagination parameters( start_position or count) for DocuSign Rest API’s.

Hi everyone, I have been testing GET method for Envelope’s Documents to retrieve an integrated document using documentId = combined as it is guided here:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocuments/getHowever, as said in the title, I cannot exclude the comment history file from the combined document, and it is not like I expected. Are there any ways to acquire this?

I’m using eSignature client api php sdk, how can I set template prefilled tabs while creating an envelop ? Here is my code $invoiceNumberTab = new Text([ 'tab_label' => 'InvoiceNumber', // Must match prefill tab label in template 'value' => 'INV-20240508']);$prefillTabs = new PrefillTabs([ 'text_tabs' => [$invoiceNumberTab]]);$templateRole = new TemplateRole([ 'email' => 'signer@example.com', 'name' => 'John Doe', 'role_name' => 'Signer' // Exact match to template role]);$envelopeDefinition = new EnvelopeDefinition([ 'status' => 'sent', 'template_id' => 'TEMPLATE_ID', 'template_roles' => [$templateRole], 'prefill_tabs' => $prefillTabs]);$envelopeSummary = $envelopeApi->createEnvelope($account_id, $envelopeDefinition);echo "Envelope

 How do I change the sender's email ID and name in an envelope? I want to use a different organizational email ID instead of the one linked to the DocuSign account

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

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