eSignature API

I’m looking into the possibility of merging together two (or more) server templates into a single PDF; currently I’m creating envelopes through Python and using Composite Templates. The envelope structure I have so far makes it so that each Composite Template results in a single PDF; each Composite Template has its own Server Template and/or Inline Template, depending on the specific template I need to use -- now, what I need (but isn’t working) is something like this (taken from another post): { "emailSubject": "DocuSign Widget Order, Signature and NDA", "emailBlurb": "Please let us know if you have any questions.", "status": "sent", "compositeTemplates": [ { "serverTemplates": [ { "sequence": "1", "templateId": "{{NDA Template}}" }, { "sequence": "2", "templateId": "{{Signature Template}}"

I am referring to the IAM Core - Professional Edition plan.In our case, we intend to use the Salesforce Extension App along with Maestro. Do we need to purchase the DocuSign Salesforce Connector add-on ?

A former employee created a custom field integration to add the start date to a docusign agreement. I updated the Hubspot property to ACC Cohort Start date. It was previously just ACC Start date, and now nothing works. This is the connection on the Hubspot end:  This is the connection on the Docusign end:This is what the agreement form looks like in docusign:

My SetupI have a user access request form built in Webflow that requires users to agree to terms and conditions. Currently, the form has a checkbox that users must check to indicate agreement.What I'm Trying to AccomplishI want to implement a legally binding electronic signature process where:The user simply checks a box to sign the terms and conditions This checkbox action is recorded as a valid electronic signature in DocuSign The signature is legally binding and creates proper audit records The entire process happens within my Webflow form without redirecting to DocuSignTechnical RequirementsThe form needs to maintain its current UX with checkbox-based acceptance Each signature needs to be properly recorded and verifiable Solution should work with Webflow's capabilities Must capture relevant metadata (timestamp, IP address, etc.) for legal validity (op

Hi Community,I have followed all the exact steps and configured docusign.I have provided all the table permissions, and all looks good except one error when I click on View and Sign button which is as attached. Error: “There was a problem opening the document. Please contact your administrator.” Please let me know what exactly is causing this issue and how can I resolve the issue.   

I have been successfully using a composite template to add recipients to a server template.(see attached code) However, one of the recipients - Approver at routing order 3 is now a part of a conditional recipient group. (See attached image) When I now try to overwrite the recipient at routing order 3, i end up with two recipients at routing order 3 instead of one. (See attached image) I tried a workaround where I would simply update the recipient at routing order 3 using PUT method of the recipients endpoint in the REST api, however that did not work either.  How can I overwrite the recipient in the conditional routing group at routing order 3 using a composite template?  { "emailSubject": "@{variables('SubjectLine')"}, "status": "sent", "compositeTemplates": [ { "serverTemplates": [ { "sequence": "1", "templ

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? 

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.

 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

 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.SecurityP

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.

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 (

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

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

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("{\"typ

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

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?

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. 

Hello, This endpoint is listed on Docusign’s postman workspace, however I see no documentation for it. Is this a supported endpoint? Thank you!

Hello, We have an application using eSignature API for signing our collaborators’ annual assessments. The authentication flow is JWT Grant, and the impersonated user id I’m passing in the configuration file belongs to my user account.I was wondering since we purchased Branding option, is there any way to overwrite the account details of the Envelope Originator / Record tracking holder by the Company name in the Certificate of Completion.Or should I create a general Admin account and pass this user id in the configuration file?Thanks for your help.

We built a C# SDK API that is connected to our customer’s website, and is supposed to call DocuSign’s API. From time to time, the DocuSign API sends back an 500 error without any error message attached (it can happen at any part of the API, from the creation of the enveloppe to the sending of the mails). The API can then be recalled with the exact same infos given the first time and will work properly.The weird part is that when we used our API for tests purposes through swagger (we tested it for a very long time) that kind of 500 error never occured. After searching any kind of possible problem, I’m still completely clueless about where the error might be coming, any kind of idea is appreciated.If any information is needed i’ll do my best to answer asap, thank you in advance.