What's happening inside the Docusign Community | January edition
Ask questions, share knowledge, and get help from other developers as well as our support team.
Recently Active
Hey Docusign developers! Here are resources we cover in our developer webinars to help start building. Developer Center developer account Quickstart ISVs get started Become a partner Stackoverflow developer support Docusign University developer blog developer YouTube developer webinars developer FAQs Docusign on GitHub Docusign Postman Collections SDKs and tools PowerForms Maestro API Navigator API extension apps Connect Webhooks, 2.0, OAuth Connect Templates and partner composite templates Happy coding!
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", "templateId": "@{items('For_each')?['hrsys_docusigntemplateid']"} } ], "inlineTemplates": [ { "sequence": "2",
I'm participating in a hackathon and building a project using Docusign's ID verification functionality. However, the API only seems to offer phone authentication as an option. Does anyone know why this might be happening and how I can enable other ID verification methods? Any guidance would be greatly appreciated!
I am using the navigator api for the docusign hackathon and i added the required scope but i keep getting Caused by: com.docusign.esign.client.ApiException: Error while requesting server, received a non successful HTTP code 400 with response Body: '{"error":"consent_required"}'and i just filled the request form for access to the navigator api beta but i don’t know how long it will take to getting approved considering timeframe, please i would appreciate your assistance
Hello! I have got a Go Live status: Review failed (See OAuth 2.0 migration options).After reading the doc I do not understand what we are doing wrong.Here are the 2 types of calls I do:/oauth/token/clickapi/v1/accounts/{accountId}/clickwraps/{clickWrapId}/agreementsWe have chosen JWT grant authentication.Can you help me understand what is wrong?Thanks a lot!
Hi,We have been working on getting an application up and running for our client, enabling them to send contracts for signing through DocuSign based on templates.Here is a summary of our progress:A developer account was created, and the application was written successfully. API test calls were successful, and initial testing went smoothly. We proceeded with the "Go Live" process, which initially seemed successful.However, during the second step of the process, we encountered an issue where our review was unsuccessful, but no specific feedback was provided.After reaching out to DocuSign support and going through several back-and-forth communications, we finally discovered the cause: we had missed filling out the power form. (If I recall correctly, this form used to appear when selecting the "Go Live" option, but with recent changes, it no longer seems to be offered during this process.)Once the form was completed together with the client, the production environment was properly bound to
Hi everyone,I'm working on a DocuSign integration where I want to use a template that dynamically updates as it progresses through a multi-signer workflow. Here’s the flow I’m trying to achieve:The initial template is populated with some hardcoded values for the first signer. Once the first signer completes and the envelope is redirected to the next signer, the template should dynamically update certain fields (e.g., names, amounts, or other placeholders) using data retrieved from an Azure Storage Account via API. This process should repeat for each signer, with the template being updated dynamically based on the signer’s role and data pulled from Azure.Steps I’ve Considered:Use the DocuSign API to create an envelope based on a pre-defined template. Populate initial tabs (fields) using the API (e.g., using templateRoles). Trigger a webhook or callback (via Connect) after each signer to: Retrieve data from an Azure Blob or Table. Update the envelope fields dynamically for the next sign
Hey everyone, hoping yall doing well!I’m trying to Go-Live but have not succed in these past hours. At the moment my app passed review and its saying “Promote to production” with a green circle on the side.So these are my steps while trying to get on production:1. Click on “Actions”2. Click on “Select Go-Live Account”3. Accept terms and click on “Accept”4. Open the pop-up5. Input email and password from my account (not the developer one) - eSignature Standard PlanAnd this is what I’m getting from it (HTTP 404 PAGE NOT FOUND): Can someone help me please??!!!
The CXO of a company needs to sign over 20 envelopes daily, which are sent from various systems like Salesforce, SAP and with the majority coming from Docusign web app. Currently, the CXO uses a mobile app for signing documents. The company has developed a new internal portal for employees, which includes functionality for managing approval processes. Now, the CXO would like to use the new portal to sign all of their pending Docusign envelopes. Is this feasible using embedded signing?
DocuSign support states that they do not support .p7m protocol, it is CAdES. DocuSign only supports PaDES. The envelopes are from Italy. They must use the following link to unencrypted https://vol.postecert.poste.it/verificatore/itWhen the docs are unencrypted, the original does not have signatures. The signatures are on a page that is blank except for signatures.
Hi, Anyone have any thoughts for ways or workarounds to only allow DocuSign to update Salesforce once an envelope is completed?We are using DocuSign Apps Launcher with Salesforce and using DocuSign envelope templates. The document first goes to recipient 1 who is required to make edits to the doc and sign it. Next it goes to an ‘Approver’ who has the option to approve or reject the document Once the Approver approves the doc, the envelope is considered completed and that is what appears in Salesforce. However, we don’t want Salesforce to be updated until the document is completed in case the first recipient had errors in the doc and now they need to be corrected? Any insights would be greatly appreciated!
We’re thrilled to announce the closed beta launch of the Docusign Visual Studio Code Extension, a new tool designed to empower developers with AI-driven assistance for building seamless integrations with Docusign’s platform.With this extension, developers can:✅ Ask Docusign-specific questions: Simply type @docusign followed by your question in the GitHub Copilot chat window to get instant answers on topics like authentication, SDK usage, or integration best practices.✅ Streamline authentication setup: Use the @docusign /getAccessToken command to generate access tokens directly within your IDE, complete with guided steps for creating and managing integration keys.✅ Explore and implement solutions faster: Leverage AI-powered guidance to build workflows, automate tasks, and integrate Docusign’s capabilities effortlessly. How to join the Closed Beta ProgramThis closed beta program is your chance to test and shape this new tool while gaining early access to its features. Interested?The ext
Hi there,We’ve been using the DocGen API (https://developers.docusign.com/docs/docgensend-api/) to create pre-populated documents using a word template. In our word-template we’ve been using a custom font family Ciutadella.We’ve been having mixed success with some generated documents (pdf output) looking accurate, and some seemingly using a different font or have issues with spacing or alignment.Are custom fonts support by this API / Docusign, and if so what steps do we need to take to ensure it can be successfully used?Thanks!
Hello,How can I increase the size of the signature window via the REST API ? I would like something like that : Moreover, is it possible to only enable focused window to avoid closing the modal when touching the screen outside it Regards,Arthur
I’m using DocuSign Connect to send a webhook to Zapier when a document is completed. When I review the output of the webhook sent to Zapier, I do not see the document field values. My custom connect is set up using REST v2.1 data format, SIM delivery mode, and data included is the following:Custom Fields Documents Attachments Document Fields Recipients Has anyone else had this issue or know a way I can adjust my configuration so that the output includes the document field values?
When using eSign API/SDK, can we somehow enable the option to attach the template PDF of the template/document to be signed via the developer console? If yes, then how?I know that after completing the signing process, the signer receives an email that contains the signed template. But in my case, I want to include the unsigned doc/template as an attachment in the sign request email sent to the signer!!
Back to Docusign.com
