eSignature API

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"}  We previously created the field with the label Custom1. But when we receive the template result on the mail tray the fields values are not appearing. The collaboration checkbox is also marked. Any solution?  Thanks in advance

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 to use with long scrolling bar

we have a requirement to auto populate the date signed field with the date and time stamp when the user has signed the document. Please let us know how do we do this using the REST API for creating and sending the Envelope. we see that there is a DateSigned tab on the API, but it requires us to provide a X and Y position of the date Signed field. We are not sure of the X and Y positions of the date signed field on each document which we send. Can you please let us know if there is anything better than this field to use

I am using Docusign eSignature API and I have a template which has pre-fill tabs added that are being populated with values when Document envelope is being created via API. I am using this endpoint: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocumenttabs/update/And whenever values are updated, tab is duplicated, one empty and the other one with value. The reason for using pre-fill tabs is to display information for all signers. And the problem is that sometimes I reach tab limit and envelope fails to generate. How could I solve this?

hello everyone,we use the rest api (eSignature) to send documents by email and have them signed.but now we need a kind of double signature process. i mean the following: the document should be sent to 2 people. first person 1 has to sign and only when this is done, person 2 has to sign. it is important that person 2 is only allowed to sign if person 1 has already signed.how exactly can we realise this?thank you.

Hi!In my Microsoft Custom Connector, I am using https://docusign.net/restapi/v2.1/accounts/1500/envelopes/{envelopeID}/views/sender as my request URL and it takes me to this page: URL: https://apps.docusign.com/send/prepare/114937d7-2643-4a12-aa4e6f959c/add-fields However, I am in need of my request URL to access the page before that one:URL: https://apps.docusign.com/send/prepare/114937d7-2643-4a12-aa4e6f959c/ 

Hello,I call the below code from a soap call. The user I want to change to is withind my users with admin permissions. The error I get is =======================================================================            <ErrorCode xmlns="missing in Web.Config">112</ErrorCode>            <ErrorReason xmlns="missing in Web.Config">This User lacks sufficient permissions.</ErrorReason>======================================================================= I already have the Allow sender to download form data setting enabled. Code: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.docusign.net/API/3.0">          <soapenv:Header>      <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">         <wsse:UsernameToken>            <wsse:Username>[integrationKey]email</wsse:Username>            <wsse:Pass

I have created a webhook that listens for any envelope created and calls the API i configured.My intention is to open the envelope based on the details received in webhook.But in the response the complete url is not available and it has only the url path , how to construct the base urlwe recieve envelope uri as /envelopes/<envelope-id>

Please add this error “REQUEST_ENTITIY_TOO_LARGE” in the article https://developers.docusign.com/docs/esign-rest-api/esign101/error-codes/troubleshooting-common-errors/ as this issue should be resolved in the DocuSign side.

Hello Everyone!I received a request to remove all DocuSign actions from my Power Automate workflows and replace them with Custom DocuSign Connectors instead. I am having trouble replicating the Generate Embedded Sender URL. My Custom Connector has all of the attributes like the actual DocuSign connector, but mine is missing the Output Embedded Sender URL. Any ideas on how to generate it?  

Hi everyone I ran into this issue hopefully someone can help me outIssueWeb App with  https://test.domain1.ioLaunches iFrame in modal window to https://test.domain2.io(different domains)The iFrame app launches Docusign using Focused View and client libraries from DocuSign for end user to sign. The launch will not work and there is an error in the console showing -Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://test.domain2.io" I am following this how-to:https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/ I also put both domains (https://test.domain1.io, https://test.domain2.io, https://apps-d.docusign.com) in  frameAncestors field when creating the recipient view URL. How can we pass https://test.domain1.io to the Docusign so it will properly configure the CSP? 

We have a main account and a number of sub accounts. I am trying to use the API to generate a report on number of envelopes sent without having to run reports on each manually. I just got the API going and I am running the end point: restapi/v2.1/accounts/{account id}I am getting the following information back:  'planStartDate': '2023-07-26T17:00:00.0000000Z', 'planEndDate': '2024-07-25T17:00:00.0000000Z', 'billingPeriodStartDate': '2024-10-01T07:00:00.0000000Z', 'billingPeriodEndDate': '2024-11-01T07:00:00.0000000Z', 'billingPeriodEnvelopesSent': '119', which does not match our contract dates (7/25 was months ago). Nor does it match the number of envelopes sent during the last contact (certainly not if the billing period is only this month). Thoughts? Am I interpreting this data incorrectly, or is there a better endpoint I should be using?  

Hi,I am currently integrating DocuSign Embedded into my web application, which supports two types of users: admins and normal users. Admins have the ability to send documents to users for signing, and I have successfully implemented this functionality.However, when a user logs into our application, I want to retrieve all the documents that they need to sign. In this context, the user is the recipient of the envelopes sent by the admin.I reviewed the DocuSign APIs and found that the process involves first retrieving all envelopes and then filtering them by recipients. However, I am unsure if this is the best approach.Could you please confirm if this method is correct, or suggest a more efficient way to achieve this?Thank you!

Is DocuSign imbedded in EPIC anywhere (as Dragon or Up To Date is)?

Hi,My account has already WhatsApp enabled and I’m trying to create an envelope via API with WhatsApp as the delivery method. I send the request, the envelope creates successfully (I receive a succesful response with the envelope link and I can also see it on my dashboard, but it just says “Waiting for” and I’m not receiving the WhatsApp message from DocuSign.Documentation is very poor on this subject, there are no real examples, no info about the country code or number format: Number must include the country code also? With plus or without plus sign? With one zero before the number, two zeros? So many questions...This is my envelope definition:I’m in Spain so the country code is 34.Appreciate any help, thanks!

Hi,I’m trying with PHP but always getting this error my code like this<?phprequire_once 'vendor/autoload.php'; use DocuSign\eSign\Client\ApiClient;use DocuSign\eSign\Configuration;use DocuSign\eSign\Api\EnvelopesApi;use DocuSign\eSign\Model\EnvelopeDefinition;use DocuSign\eSign\Model\Signer;use DocuSign\eSign\Model\Recipients;use DocuSign\eSign\Model\Document;use Firebase\JWT\JWT; $integrationKey = '9eaed807-bd9f-4d38-b858-37f6eccc6b73'; // Your Integration Key$userId = 'd4300ed6-aa42-47cd-b687-01c825726abd'; // Your User ID (GUID)$privateKey = file_get_contents('key.pem'); // Path to your private key$accountId = '8c637b59-afa2-4821-8c5d-981bacf4ddde'; // Your Account ID // Set the current time and expiration time$now = time();$expiration = $now + 3600000; // Token valid for 1 hour // Create the JWT payload$payload = [    'iss' => $integrationKey,    'sub' => $userId,    'iat' => $now,    'exp' => $expiration,    'aud' => 'demo.docusign.net',  //aud: Should be set to

Hello,As an inspection company in Portugal, we issue inspection certificates and are looking to integrate this process into our ERP system (Odoo). We aim to use Advanced Electronic Signatures (AES) or Qualified Electronic Signatures (QES) for these certificates. Could you please advise on the best solution and steps to implement this integration with DocuSign, and can we use this solution by the name of company instead of personnel identity?Thank you for your assistance.

We recently encountered an issue with one of our customers while using the following API: https://eu.docusign.net/restapi/v2.1/accounts/<Account Id>/envelopes/<Envelope Id>/recipients?resend_envelope=trueWe received the following error response: {"errorCode": "ENVELOPE_CANNOT_CORRECT_INVALID_STATE", "message": "This account may not have 'correct' permission, or the envelope state is not 'sent' or 'delivered'."}We have tested this in our sandbox/dev account and did not find any specific additional permission needed to perform this action. Could you please clarify what extra permissions or access rights are required to avoid this error? If possible, could anyone provide a screenshot from the DocuSign portal showing where to configure this permission? This would be very helpful.