eSignature API

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

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.

Hello Team,I have created 5 documents. I want to send these documents to different recipients. For Example: Document 1 -- To be signed by Signer 1Document 2 -- To be signed by Signer 1Document 3 -- To be signed by Signer 2Document 4 -- To be signed by Signer 3Document 4 -- To be signed by Signer 4 Is it possible to send these all these 5 documents in a single envelope via DocuSign Rest API?Thanks!!

I'm currently developing an app that sends envelopes directly. This means that there is no specific user who can be impersonated. Do I have to create a "system" user which is used for this or is there another possibility? 

Hello,I am developing an app that uses flows that use docusign connector to send envelopes in power platform. Till now I was using the docusign demo connectors and it was fine. Now that I wanted to change to production environment and I changed to normal Docusign connectors I can’t deploy because I get this error ‘Create and authorize oauth connection failed’. So do I need a premium docusign license on my developer account to deploy to production?  

Hola..  Hemos tenido una aplicación conectada con docusign y funcionaba bien, Pero se ha generado nuevamente las clavse privadas RSQ (que nos dieron tres una private key,  public  key  y un identificador).. Y ya no se conecta.Hemos ido a azure y hemos visto que existe una carpeta keys, y al edita private key.. no es la misma que generamos, hemos actualizado y todavia no podemos conectarnos, nos da el error 403  

Hello EveryoneI would like to request the implementation of a functionality that allows users to modify and delete address book entries within our application. This feature should be similar to the functionality in DocuSign under My Preferences -> Contact, where users can easily update or remove entries.Example:In DocuSign, when users navigate to My Preferences -> Contact, they have the options to modify or delete stored contact information. We want to replicate a similar user experience in our application for address book management to make it user-friendly and intuitive.Could you confirm if this implementation is feasible and provide feedback on how we could approach this? Please let me know if further details are needed.Best regards,  Akram Alam

For SOAP API ,how to update from Legacy authentication to App password authentication

HI Team, Can someone help me to Integrate DocuSign On my Application Below are the Details:-<add key="ClientId" value="" /><add key="Userid" value="" /><add key="AccountId" value="" /><add key="AuthServer" value="account-d.docusign.com" /><add key="RSAPrivateKey" value="”/>For Userid key - I used user ID from user profile For ClientId key :- I used Integration keyFor RSAPrivateKey :- I user RSA Keypair private key For AccountId key :- I used org

How do I correlate from my WebApp DocuSign REST calls to the Splunk docusign index?  Docusign Event ID looks like the best correlation but I can not figure out how to get it from the response on my WebApp activity. --Steve Sample searchindex=docusign sourcetype="docusign:monitor"| eval json_payload=_raw| spath output=userId input=json_payload path=userId| spath output=user_action input=json_payload path=action| spath output=user_device input=json_payload path=userAgentClientInfo{}.device{}.family| spath output=user_device_model input=json_payload path=userAgentClientInfo{}.device{}.brand| spath output=user_agent input=json_payload path=userAgent| spath output=user_agent_family input=json_payload path=userAgentClientInfo{}.browser{}.family| spath output=signers_recipient_guid input=json_payload path=data{}.RecipientInfo{}.RecipientId| spath output=signers_recipient_id input=json_payload path=data

Unable to Connect with Coupa.I am using the same Email to connect with Coupa, but it keeps throwing “password/email invalid”

Hi, Summary: status not refreshed after correcting an envelope, setting another invalid email via API Explanation:Tested in the demo acountI have created an envelope containing 2 signers, putting an invalid email in the first signer. Through the API, I can get the ‘autoresponded:smtp; 550’ status, so I know I must correct the first email address.Using the API,when I correct the email address giving another invalid email address, the status remains ‘sent’, no matter what I attempt to do (UpdateRecipients with resendOption to true, Update with resend option or even resend through the DocuSign website)… Am-I missing something ? When I correct the first signer address through the DocuSign website, the ‘failed’ status of the second invalid email address is shown :

Hi, I used the SDK for Java (Version 6.0.0) and i tried to use the function for Routing Order, but doesn´t works.  My Code IntStream.range(0, userSigners.size()).forEach(i -> {Signer signer = new Signer();signer.setEmail(userSigners.get(i).getEmail());signer.setName(userSigners.get(i).getName());signer.recipientId(String.valueOf(i+1));signer.setRoutingOrder(String.valueOf(i));signer.setTabs(tabs); signers.add(signer);}); Recipients recipients = new Recipients();recipients.setSigners(signers);recipients.setCurrentRoutingOrder("true");envelope.setRecipients(recipients); This is correct?

I'm unable to connect in production mode.

 Hello everyone, how are you?I'm having this problem when sending a file to my client.I believe it is because the Co-Buyer or Co-Seller fields are not filled in, how can I do to remove the requirement to fill them in?   

Hi Team,Could anyone help me with the following issue:I have to make the hyperlink clickable using createEnvelope API. The steps I have followed:Created one Anchor string on the PDF file with prefix #HREF. Configured that Anchor string as well with the same name. Then tried creating envelope with the above-mentioned file. When I have opened that envelope, I could see one link clickable but whenever I click on that link it is getting redirected to a blank page. Please refer to attached image below. Clickable Hyperlink

Hi Team,I am getting below error while invoking docusign  makeEnvelope  test@gmail.comcreatingEnvelopeAn uncaught exception occured!Error: Unauthorized    at Request.callback (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:696:15)    at /home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:906:18    at IncomingMessage.<anonymous> (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/parsers/json.js:19:7)    at IncomingMessage.emit (node:events:539:35)    at endReadableNT (node:internal/streams/readable:1345:12) This works fine for me in local, however the same is failing through an application deployed in cloud.I have added redirect uri

I’m trying to use the phone number auth for my python API. I’m already using the API to get the workflow ID and I’m getting this value:'c368e411-1592-4001-a3df-dca94ac539ae' However, I’m still getting this error:HTTP response body: b'{"errorCode":"IDENTITY_WORKFLOW_INVALID_ID","message":"The identity workflow ID specified is not valid."}' Any idea on this?Thanks!

In the past few weeks account-d Docusign is broken, it does NOT happen in account DocuSign website. We use Java API and have not changed a single line of code in over a year, but in the past few weeks the MS Word .docx that we send to get signed is showing to everyone the Content Controls that are in the document. This has never happened before, all content controls are hidden in production Docusign and was always hidden on account-d. But now in the past few weeks they are showing, something has broken on account-d.  

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"}