Developer

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

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 : In the envelope’s history, there a slight difference between :Correcting through the API displays a “Resent” status in the action columnCorrecting through the DocuSign website display an “Invitation resent’ status. (translated fro

Dear Colleagues,My name is Mikhail Pliss, and I am the CIO of the startup Solify.me. We are developing a platform for solar panel installations in the US market. We require a solution that allows our customers to electronically sign contracts with us within their personal accounts on our website. Would you be able to assist us in implementing this feature? We anticipate approximately 1000 customers per year, who are homeowners interested in installing solar panels. They will register on our website using their email addresses.Thank you for your time and consideration.Sincerely, Mikhail Pliss CIO, Solify.me

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?

Hi, I am working on setting up an integration with Docusign for Salesforce, the last thing I did was update the token, then I tried to send an envelope and got the error message:  The specified Integrator Key was not found or is disabled. Invalid account specified for user” in a demo account.Checked in salesforce that integration key is matching with integration key is matching DocuSign account integration key. The below url I am using is this, please advise. Thank youDocusign Account URL https://account-d.docusign.com/oauth/token

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, I have a Custom button calling screen flow in Salesforce. The flow is setup to “Send with DocuSign” as per below:  I have quite extension Screen documentation for errors, and the flow completes successfully:The envelope (related to the ID I’m using above) works when I execute it directly - however, when the flow completes, I don’t get any errors, it completes, but the Envelope is not sent. If I edit the envelope template ID slightly, the flow fails - so I knwo the ID is correct… Similiarly, I know the correct object is being sent through…Is it possible to get any feedback from the APEX action so I can tell if it worked or not. As you can see the flow is designed to create an object to hold all the responses from the docuemnt - but otherwise its pretty straight forward. I can use this object to track a status if one exists! 

Hello everyone, We have Salesforce and DocuSign integration, I have a requirement to setup a DocuSign envelope template on custom object and that record is created by a guest user via a form on a cloud experience site. I designed the Record-Trigger flow on creation a record with a condition as in the screenshot below:  The flow is running well, but the DocuSign component is not sending the envelope and i can see the following error message in the debug log : Failed to process batch for class 'dfsle.EnvelopeConfigurationBulkSend' for job id '000Ty00000jkmnU' caused by: dfsle.UnauthorizedException: You must have DocuSign sender permissions to perform this operation Class.dfsle.Permissions.verifyIsDocuSignSender: line 414, column 1Class.dfsle.Permissions.verifyIsDocuSignSender: line 408, column 1Class.dfsle.EnvelopeService.sendEnvelopes: line 782, column 1Class.dfsle.EnvelopeConfigurationBulkSend.execute: line 69, column 1 I know this is due to a Docusign limitation that is the Salesforce