Developer

Hi there!We currently are working toward adding a DocuSign integration into our App. Our workflow is quite simple and was implemented without issue into our Continuous environment using the eSignature API to create envelopes and Connect to listen to events happening to those envelopes. We use an OAuth2.0 Client to be able to authorize DocuSign to call our backend using a route listening to Connect calls and act on those events. Now that the implementation on Continuous has been successful we would like to implement it on other environments including our Test environment. Every environment use a different base url and a different OAuth client. In order to setup that we looked into the EventNotificaiton property of the envelope to be able to configure a custom url to send our events for that specific envelope. I’m still stuck on one last point, I need to be able to specify the OAuth2.0 configuration to use for that EventNotification. Is there a way to specify it? Thank you.

Hello, I am creating a form that requires to activate some fields, I know it is possible to achieve it with the rules. Is it possible to create a rule through the API?. Thanks.

Can anybody guide me to access legacy jar file - net.docusign.api._3.docusignconnect ?

Hi! I just published a new YouTube video on how to configure Docusign to collect payments and save customer payment methods during the signing process.You’ll learn how to:Integrate Stripe, PayPal, and other payment gateways into Docusign. Use formulas to calculate dynamic payment amounts. Set up conditional logic for payment methods like credit card vs. wire transfer.Streamline your payment collection process with Docusign! You can find it here:  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 EveryoneI am new to DocuSign and currently integrating it with MuleSoft using the "Envelopes Post Envelopes" API. I am sending the following payload, but the envelope is not being populated with the data I am passing. However, when I include xPosition and yPosition, the data appears in the envelope. My goal is to populate the fields using tabLabel instead, but it is not working. How can I resolve this issue?Template with Standard Text field Payload:{ "brandId": "d380fe66-xxxxxxxxxxxxx", "templateId": "63ebae68-xxxxxxxxxxxxxxxxxxxx", // Need full template ID "status": "sent", "compositeTemplates": [ { "templateId": "63ebae68-xxxxxxxxxxxxxxxxx", // Should match above "sequence": "1", "inlineTemplates": [ { "sequence": "1", "recipients": { "signers": [ { "roleName": "Signer1", // Match template

 PhoneAuthentication is received as null.Code used to add Authentication is below: orignalSigners.IdCheckConfigurationName = "Phone Auth $";                                    RecipientPhoneAuthentication recipientPhoneAuthentication = new RecipientPhoneAuthentication();                                    List<string> senderProvidedNumbers = new List<string>();                                    recipientPhoneAuthentication.SenderProvidedNumbers = senderProvidedNumbers;                                    recipientPhoneAuthentication.SenderProvidedNumbers.Add(t.PhoneNumber);                                    orignalSigners.PhoneAuthentication = recipientPhoneAuthentication; Trying to get Signer with Authentication using following code but the signer.PhoneAuthentication is received as null: System.Net.ServicePointManager.SecurityProtocol = (System.Net.SecurityProtocolType)3072;                accountID = this.GetAccountID();                EnvelopesApi envelopesApi = new Env

Hi Team,Actually we are using “#Automatically send to eSign”  flow in DocuSign. Previously it used to work but recently flow got broken and we are getting response as Draft from Docusign and not sending for Signature automatically even though we are providing anchor signature details in request body.Can you please let us know what might be the issue ?Thanks in anticipation!Regards,Bhaskari.

Hello,  I’m trying to display the embedded signing view using DocuSign's focus view, but I’m encountering an issue. Here’s the screenshot and the error message from the console log. This is occurring in my local environment.  Could someone please help me understand why this is happening? Below is an example of the code I’m using. I’d really appreciate it if you could point out anything I might be doing wrong. Thank you! 

I am working on a PoC for Integration with Docusign and using Embedded Signing with Focussed View because we have our website and don’t want Admins to go out of application context.I have 2 options to display the document to end user Load the document in the same application window by loading DocusignJS and passing it RecipientViewURL and ClientId. Cross Launch the RecipientViewUrl obtained by making CreateEnvelope and CreateRecipientView API calls.For my integration, I am making Docusign eSignature API calls from a backend service and passing on the URL to the frontend portal.I am also working on using Connect APIs to receive a callback when Envelope event is raised (completed, voided and declined). I want to understandWhat event is raised when the enduser views the Document but Does not perform any action and the URL expires. Close the browser without taking any action  If there’s no connect event raised, how can we handle the case when end user performs above actions and take appr

COMO ACHAR A API DO DOCUSIGN HOW TO FIND THE DOCUSIGN API  

Is there a way to translate the message in the AutoRespondedReason field when receiving a Connect callback or when calling the List Recipients API?I see no pattern in the text I receive from this field, sometimes it comes with the STMP error code, and sometimes it doesn’t, and I can’t show this message to the user of my system, because it is not easy to understand the real error that occurs.My APIs are in C#, it would be great if DocuSign could translate the error or give us a way to decode it.

I’m working on updating our Java SDK usage from 2.17 to 6.0.0 and API from v2.0 to v2.1. Given some signature changes I’m comparing with the API references to make sure I’m making the correct changes. We have a process to create templates, and we set a password to prevent accidental editing - in v2.0 it’s part of the envelope template definition (https://developers.docusign.com/docs/esign-rest-api/v2/reference/templates/templates/create/#schema__envelopetemplate_envelopetemplatedefinition). In v2.1 at some point I believe the fields in the template definition object were flattened to the envelopeTemplate object, including the `password` field (https://developers.docusign.com/docs/esign-rest-api/reference/templates/templates/create/#schema__envelopetemplate_password). However the documentation for that field (at that link) indicates that it’s the **user’s** password instead of the template password. I think that’s incorrect? I will at some point probably test this but it would be helpfu

deleted

Im integrating eSignature API using ASP .NET web api core and getting the below error after deploying it on our test site.  My test server supports TLS12 and I explicitly set it for http client handler in my api for DocusignClient.   Monitored the traffic using Wireshark and I could see my test server sends hello handshake, but I do not see the hello handshake from Docusign server, Any leads to resolve this issue greatly appreciated. Thank you Error Content: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.   --- End of inner exception stack trace ---

I have a flow to create envelope, add doc, add recipient, tag (as needed) and send. When I log into DocuSign, I have 2 accounts, a default and a group account for all the appropriate users. Since I need all users to trigger the flow, I changed the connections to all steps to reference the group account number. All step look good EXCEPT Create Envelope. This one gives me the following error: Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'docusign' operation 'GetCustomFields' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: {"errorCode":"USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT","message":"The specified User is not a member of the specified Account."}' I’ve tried creating a new connection and it is still upset. Any help is appreciated. Thanks :)

Hi community,I need some help with the Go-Live process. I’m trying to get my Integration-Key into production since round about a month. There is no problem with the automatich review (20 successful API calls, no polling). But there seems to be some sort of manual review when I try to promote the Integration-Key to a production account. The first two times I tried it took 10-14 days and in the end the review was declined. Today I created a new Integration-Key and tried again and it got declined within a few hours.I actually have no idea why the promotion is declined. I didn’t get a mail or any sort of information about the decline.While waiting for the promotion the first time I created a support ticket with our production account and I was told that there is no support on basic API plan.So what are my options? Currently we’re paying for an API plan that we cannot use.Best regards,Dominik

Hello, I’m trying to use the docusign rest api to create a signing url from a pdf. The problem i’m encountering is no matter whether i sent up a placeholder recipient or use a template to have a user create their own envelope they can sign i get auth blocked. the reason why i’m doing it this way is that A. users in my app may not have a pre-existing docusign account and i don’t want to add a cascade update for all event documents when they make one B. i don’t want our app to keep having to use the hosts docusign account to add people as recipients. all i need is a solution that opens a signing event in a url and the host can get those signed documents

Hi! I just published a new YouTube video on how to automate complex application forms using Docusign Web Forms.You’ll learn how to:Build a mobile-friendly credit application form with multiple layers of conditional logic. Capture incomplete submissions in case your signers don’t go through the entire process. Auto-export application form data into your CRM, eliminating manual entry. Implement ID verification to prevent fraud.Transform your credit application process with automation! You can find it here:  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 trying the trial version. Can I send an envelope to multiple people at the same time but have each person sign the document without other users seeing the signature? as if it were a single shipment.Has anyone done this in power automate(Microsoft365)?

Quando assinamos o contrato com a Docusign, deixamos bem claro que os documentos que enviaríamos aos clientes para assinar seriam enviados a um cartório para registro. No entanto, enviamos um documento e ele não foi aceito porque foi assinado pela DS Electronic. Eles aceitam o ICP BRASIL, mas nem todos os clientes possuem certificado digital. Quando entramos em contato com a Docusign, eles agora querem cobrar outro valor por uma assinatura qualificada, o que não foi o que nos foi dito quando assinamos o contrato. Precisamos urgentemente de uma solução para este caso. Estamos aguardando uma resposta. .

I am trying to call DocuSign Export API's and getting error "Unauthorized" below see below details for more : Code : (Azure Function C#) string url = $"https://api.docusign.net/Management/v2/organizations/ORGID/exports/user_list"; _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); var requestBody = new StringContent("{\"type\": \"organization_user_list_export\"}", Encoding.UTF8, "application/json"); var response = await _httpClient.PostAsync(url, requestBody); if (response.IsSuccessStatusCode) I'm trying to export all users list using DocuSign admin API, however I have provide the required consent but still getting "Unauthorized error"Below is the code (Azure Function C#) that i am using:string url = $"https://api.docusign.net/Management/v2/organizations/ORGID/exports/user_list"; _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); var requestBody = new StringContent("{\"

Hello, i’m following the steps in this doc https://developers.docusign.com/platform/auth/jwt/jwt-get-token/.and when i paste the jwt on jwt.io the payload come in this format:  "\u0001\u000b\u0000\u0000\u0000\u0001\u0000\u0006\u0000\u0007\u0000\u0000my�SL�H\b\u0000\u0000���SL�H\u0002\u0000M�%��O�B�'\u0015[�0É\u0015\u0000\u0001\u0000\u0000\u0000\u0018\u0000\u0003\u0000\u0000\u0000\u0005\u0000\u0000\u0000\u001d\u0000\u0000\u00002\u0000\u0000\u0000\r\u0000$\u0000\u0000\u00001dff3d9d-d24b-48b0-bd7b-96d282b4d7af\"\u0000$\u0000\u0000\u00001dff3d9d-d24b-48b0-bd7b-96d282b4d7af0\u0000\u0000my�SL�H\u0012\u0000\u0001\u0000\u0000\u0000\u000b\u0000\u0000\u0000interactive7\u0000}\u0012����5N����3t\u0016�" Even after verifying the signature with public and private key..  and if I try to use the JWT on https://account-d.docusign.com/oauth/token I still get:{"error": "invalid_grant","error_description": "user_not_found"}

I have a Node.js application where I create a DocuSign envelope. Currently, I use the Authorization Code Grant flow to manually obtain the access token and refresh token. However, the refresh token expires every 30 days if not used. Is there an alternative method that would allow me to avoid manually generating a new access token and logging in each time the refresh token expires?

Hey there, currently I’m integrating the bundle.js to my application to sign an agreement. I’m using a dialog to present this document, this dialog can be closed or opened, I was looking for a way to clean the event listeners of the signing but I can’t find any information about it.  I’m using React, there’s any way to remove the listeners associated when unmount the docusign embed document?

What scope parameter value should we use for the Authorization Code endpoint to ensure that the refresh token never expires? Currently, we have set the scope to "signature extended," but the refresh token still expires after 30 days.