Developer

Hi Adam Minow, I am trying to access0000000@000000000Account #000000 this is developer account in DocuSign, but I received a message that says I am not an administrator for this account. Could you please grant me the necessary permissions, or log in on my behalf to assist with this request? they want to connect0000000@000000000Account #0000 how to connect this is user account(post edited due to personal information) 

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 just published a new YouTube video on how to send multiple documents for signature to different people using Docusign.You will understand how to automate the entire workflow, whether you're sending the same document to multiple signers or creating a unique process for each individual, plus how to simplify using templates and automation tools. You can find it here: PS: join me every Wednesday at 9 AM PST during a free Q&A session. Click here to register! Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hi All,I downloaded a quick start java app from docusign developer portal and it was working fine till last week. When i tested today, it is not working.  It does not throw any exceptions or error.  When running the main class, the program simply terminates without providing any message or error.  The file to sign will be fetched from a local folder, convert into base64 then send it to the API functions.  When it enters the below lines of code, the entire program simply terminates and no code below these lines are getting executed. EnvelopesApi envelopesApi = new EnvelopesApi(apiClient);EnvelopeSummary results = envelopesApi.createEnvelope(accountId, envelope); Can someone please guide me on this?  

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

We are successfully using the embedded view “default” style to allow our users to sign documents, and then proceed onto the next step. However, we do allow the user to refresh the page and get back into the “signing step”, and that works well, except if it has already been signed. When the document is signed, and the page is refreshed, we successfully show the document again, and this time instead of “Sign” or “Finish”, Docusign UX displays “Close”. When that “Close” is pressed, the “endSession” event isn’t triggered as normal, but the nested iFrame is destroyed. This workflow does works well with the “focused” style in all cases (meaning that by just changing “displayFormat” to “focused” it fixes the issue), however, we would like to use the “default” UX. How could we have “endSession” trigger when pressing “Close” on an already signed document?

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 I am trying to make a soap call through postman but I get an error that my username or password is incorrect. For username I use the email I have on Docusign and for the password the app password I created from the settings. Is this combination correct?XML body <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="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>myEmail</wsse:Username>            <wsse:Password>myPassword</wsse:Password>         </wsse:UsernameToken>      </wsse:Security>   </soapenv:Header>   <soapenv:Body>      <ds:RequestEnvelope>         <ds:EnvelopeID>MyEnvelopeId</ds:EnvelopeID>      </ds:RequestEnvelope>   </soapenv:Body></

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!!

Hi! I just published a new YouTube video on the three types of Docusign integrations with SalesforceYou will understand the differences between Docusign for Salesforce, Docusign Doc Gen, and Custom Integrations and how each method allows you to create, send, and track documents directly from Salesforce. You can find it here: PS: join me every Wednesday at 9AM PST during a free Q&A session. Click here to register! Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

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  

I can’t create a Docusign developer account - when filling out the form and submitting, the subsequent “clock” just spins and spins forever.  Have tried two computers and two different browsers.    I’ve seen some other mentions of this issue but no resolution.    Help??

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

If we have already have a envelopeId and we want to show the documents for signing in our single page app, do we have to communicate with DocuSign’s API?

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 organisation Account IdBut I am getting and not able to integrate can someone help me on thisThanksAkram

Hi Team,  I’ m integrating docusign Embedded Signing in React js Application.   I create below component : import React, {useEffect} from 'react';import PropTypes from 'prop-types';function DocumentSignUI({integrationKey, docUrl}) { useEffect(() => { const loadDocuSign = async () => { const docusign = await window.DocuSign.loadDocuSign(integrationKey); const url = `${docUrl}&output=embed`; const signing = docusign.signing({ url, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary button */ backgroundColor: '#333', /** Text color of primary button */ color: '#fff',

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{}.RecipientInfo{}.UserId| spath output=documentIdGuid input=json_payload path=data{}.envelo