Developer

Is there a way to automate medical consent forms.  Recently I have had to fill out and sign forms for my minor children for religious & civic organizations.  The forms have many check boxes and signature lines as well as text fields.  Both organizations sent them in PDF with the intent of parents printing them, manually filling them out, & returning them in person.  Returning them required standing in long lines while  volunteers visually checked them and verified they were properly filled & signed.  Then all the forms were gathered and put into a box and taken on the trips with the groups to various activities.  As a parent it is a little disconcerting that my child's medical info is on a piece of paper reviewed by volunteers and in a box somewhere.  My question is:   Is there some way to collect and automate that info on DocuSign?  Is there a way that DocuSign forms can populate a database which could be later linked to some sort of QR code on a bracelet so that the relev

Hello !  We have a integration project for Esignature. I see the OAuth configuration work on Connect RestAPI but for SOAP Connector, the authentification isn’t working.I didn’t find in a documentation if the OAuth works with legacy Connect (custom connect SOAP) Thanks,

Hello, I have an integration with my client’s custom software and DocuSign’s rest api. We are creating envelopes from a template. This all works well except we do not want the signer to have to answer the authentication questions before signing. We tried turning this off on my clients DocuSign account but the changes do not work when the envelope is created via the api. Support says we can turn off authentication via the api call but I do not see it anywhere. Can someone point me in the right direction?

How does one get full access control information for templates shared to the user currently logged in or impersonated using the eSignature API? An example use case is the following: an admin user creates a new group; GroupA, and adds User1 to that group, then shares a template, TemplateXYZ, to GroupA . When I am logged into the Docusign UI as User1,  I can see that I have shared access to TemplateXYZ. But there doesn't seem to be an eSignature API that can tell me this. When User1 calls the API to get info for TemplateXYZ (Templates:get) it doesn't return anything about its shared access. And yet there are API to update or delete groups shares for a specific template (Templates:updateGroupShare and Templates:deleteGroupShare).  The only other API I’ve found that seems like it should return the info I’m looking for is Accounts:listSharedAccess. According to its documentation I should be able to pass item_type=templates but that returns a bad-request error with additional message that I

I am looking to use DocuSign Connect to update the status of processes in Salesforce and, upon completion, save the signed PDF file in Salesforce.While I've been able to update the status using the object mapping feature between DocuSign and Salesforce, I found it difficult to save the PDF file post-signature using this method.To address this, I created a custom REST API in Salesforce and made it public via Salesforce Sites, allowing for public access to the API.Initially, I considered OAuth 2.0 as a way to validate the source of the requests, which brings me to my main question: although DocuSign Connect supports the Client Credentials Grant flow of OAuth 2.0, Salesforce does not. As a result, I abandoned OAuth 2.0 for validation.Instead, I implemented HMAC signature validation using the Connect Key, and Salesforce is now able to receive the requests.Is my understanding correct that OAuth 2.0 validation cannot be used with DocuSign Connect when the recipient is Salesforce?Reference: h

Hello Docusign community,I'm currently integrating Docusign's embedded signature feature into my React TypeScript application. I've followed the steps in the documentation and installed the necessary dependencies, but I'm encountering an error where 'docusign' is not defined. This error appears multiple times throughout my code (e.g., Line 112:26). Can anyone help me understand why this error is occurring and how I can resolve it?  here is an image of what is displayed in my browser console: Thanks !

Is it only the Authentication that will be end of life? can we still use the SDK from before and just change the authentication to 2.0 OAuth?I wanna know cuz were still using the v2.1, will this still work?

Hi! I just published a new YouTube video on Docusign Identity Verification.You will learn how to ensure signer authenticity with Docusign's identity verification tools. I'll walk you through setting up ID verification, acceptable documents, and secure authentication methods, with a live demo to see these tools in action. 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

Morning, in my team we are trying to implement an integration with DocuSign and according to the documentation, we need to setup an OAuth process. In order to do so, the steps we’ve followed are:Create a developer account Go to “Integrations” → “Apps and Keys” and create an app there with a secret key and also the redirect URIs and CORS configuration. As it is the first try, we used “http://localhost:3000” everywhere. We followed this link from the documentation: https://developers.docusign.com/platform/auth/authcode/confidential-authcode-get-token/ We’ve implemented a redirection from our frontend to get an authCode as stated in the documentation by calling https://account-d.docusign.com/oauth/auth with response_type=code,scope=signature cors,client_id={OUR_CLIENT_ID} and redirect_uri=http://localhost:3000 Afterwards, we are doing a POST request through axios to https://account-d.docusign.com/oauth with the parameters stated in the documentation (a header with Authorization: Basic {CO

Hi,I’m trying to send an envelope with multiple documents and each document needs to be applied a specific template.I’m looping through the documents and adding the specific serverTemplate based on the type of document.Here’s a snippet:The serverTemplate is determined by: However, it seems that the other template is being applied also to the document that it’s not meant for.Here’s the error:HTTP response body: b'{"errorCode":"TAB_PAGENUMBER_IS_NOT_IN_DOCUMENT","message":"The pagenumber specified in the tab element is not in the document that the tab refers to. Tab on Page 9 of Document 1 for Recipient 1"}' Any idea?Thanks!

Goal:I want to reflect the signing status of an Envelope in Salesforce using DocuSign Connect. The envelope is created using Salesforce Apex, and the signing status is received through a custom Salesforce REST API that is implemented with Apex.Issue:I have completed the DocuSign Connect setup, but no logs appear in the "Logs" tab, and even after completing the signing, no requests are coming to Salesforce.DocuSign Connect Settings:Listener Settings:Status: Active Connection Name: SalesforceStatusUpdate URL to publish: https://[mydomain].my.salesforce.com/services/apexrest/namespace/docusign Enable Logs: Checked Require Acknowledgement: CheckedData Format: REST v2.1 Event Message Delivery Mode: Send individual messagesTrigger Events:All checkboxes under Envelope and Recipient are checkedAssociated User/Group: All UsersIntegration and Security Settings:Include OAuth: CheckedOAuth 2.0 Settings:Enable OAuth: Checked Client ID: Configured Client Secret: Configured Authorization Server URL:

Dear Community, I am looking for a solution to an issue that we ran into recently while creating elastic templates.We created the elastic template following the documentation from Docusign, however, once we tried to create conditional rules, we noticed that we cannot drag and the document field into rule builder as shown in the video/gif in the documentation: Conditional Content (docusign.com)I have attached a GIF of the issue that we are experiencing. Is this a bug or are we doing something wrong?Best Regards,Shahir 

I am using C# docusign JWT SDK to authenticate. I am able to authenticate and get an access token back where I am able to successfully call GetUserInfo to get account information, but when I create an envelope from the downloaded example, and send that to the CreateEnvelope(account,envelope), it is generating a 500 error message with Stack Trace error…“at DocuSign.eSign.Api.EnvelopesApi.CreateEnvelopeWithHttpInfo(String accountId, EnvelopeDefinition envelopeDefinition, CreateEnvelopeOptions options)”My scopes are “signature” and “impersonation” What am i not doing correctly? Thanks

Hello, . 1. Go to https://account.docusign.com/,  and sign in with your TSC email address.2. If you are prompted to enter your TSC password after entering your TSC email address, please select the “USE COMPANY LOGIN” option instead of typing in your password. Continue to log in as usual.

I’m using the SDK C# and when sending a request Envelopes::GetDocument (link) to get the documents, this fails with error:"errorCode":"USER_AUTHENTICATION_FAILED","message":"One or both of Username and Password are invalid. Invalid access token" All other API calls before calling GetDocument are passing OK - for example when calling Envelopes::listDocument (before the GetDocument) to get the list of documents, that returns succesfully. But then with same starting point GetDocument fails.We do checks for token validity etc. before calling these methods and only GetDocument respons with error. What could be the cause and what should we consider?

Hi everyone,I’m able to send out envelopes for signature in Node.js via the docusign-esign NPM package, but my text fields are not populating for some reason.  I am referencing the documentation linked here.  I’ve tried both on our developer account as well as our production account.Here is my code for creating the envelope.  I am getting the label and ID for the text fields through the Docusign API, and I have double-checked the label is correct through the Docusign webapp itself.function makeEnvelope(args) { try { let envelope = new docusign.EnvelopeDefinition(); envelope.templateId = args.templateId; let text = docusign.Text.constructFromObject({ tabLabel: TAB_1_LABEL, value: 'test text field!', }); let textExtra = docusign.Text.constructFromObject({ font: 'helvetica', font_size: 'size14', tabLabel: TAB_2_LABEL, height: '23', width: '84', required: 'false',

Hi, I’m trying to use a Production Account of a client for Go-Live.However, my developer account does not have an administrator access to their account. The client refuses to give me a full administrator access because they are afraid that I’ll get access to all other unnecessary information.Is there any alternative to this?Thanks!

   This happens with every tab when I set them to true

Hello,We’ve just updated to the Embedded Signing flow. When loading up a document the embedded loader is appearing on the left of the screen. However, there is no way to modify this. Is there something we can pass or is there a bug with our container? Bellow are the screenshots and source code //running in the console$('div[data-qa="embedded-document-loading"]').style.width='100%';//updates the loader to show as centeredApplication Code://TSconst signingConfiguration = { url: this.url, //url from service displayFormat: 'default', style: { signingNavigationButton: { finishText: 'Submit', position: 'bottom-right' } }};try { const docusign = await DocuSign.loadDocuSign(clientId); const signing = docusign.signing(signingConfiguration); /** Event handlers **/ signing.on('ready', (_event) => { console.log('UI is rendered'); }); signing.on('sessionEnd', (event) => { console.log('sessionEnd', event); i

Could you please advise us on the alert and how to to mitigate it  

I’ve created a “demo” app under the primary credentials in which I’ve got a new process coded and working in the test environment up until the receiving of the signed document from docusign.Today in production we receive signed documents at a handler hosted by us (the creating/sending of envelopes today is done with a SOAP integration). This new integration is using the REST approach to create/send envelopes (again working in demo). I would like to test receiving these signed documents generated by the REST approach, but haven’t been able to find how to configure or even view our current webhook. It appears from what I’ve gathered that this is done at “https://apps-d.docusign.com/admin/connect”. I believe the reason I don’t see anything here on our production login is that our integration pre-dates much of what is available today.My question is I would like to add a webhook for this demo app under our primary login, is this possible? If so, where? If not, what is the approach Docusign

Hi! I just published a new YouTube video on how to use Docusign's document visibility feature.You will learn how to control who can view specific documents within a single Docusign envelope, ensuring confidentiality between different parties. You can find it here:  PS: Join me every Wednesday at 9 AM PST for 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, I have 2 questions about Starter plan for Developer API.https://ecom.docusign.com/en-GB/plans-and-pricing/developerPlease check the link for price plans. It says 40 envelopes per month and also 5 envelopes.I didn’t understand the difference. We expect to get 20-30 applications monthly.But I wonder what happens if we sometimes exceed 40 envelopes.Will the system block requests or there will be extra charge for the exceeded envelopes. Thanks

Asp.net MVC C# rest api when i run my code in localhost the code run properly but when in deployed code in server then show error PARTNER_AUTHENTICATION_FAILEDi