Skip to main content
arrow-left Back to Docusign.com

Developer

Ask questions, share knowledge, and get help from other developers as well as our support team.

  • 1,149 Topics
  • 12 Replies
1149 Topics
sofian_solusign
Troubleshooter
sofian_solusignTroubleshooter
posted in General
How To Configure Docusign Agreement Actions

Hi! I just published a new YouTube video on how to automate workflows using Docusign agreement rules.You’ll learn how to:Automatically store signed PDFs in Google Drive, OneDrive, or SharePoint. Export recipient-entered data from Docusign forms into spreadsheets. Automatically send follow-up envelopes to the same recipients when a previous envelope is signed.Master seamless integrations to save time and reduce errors in your document processes. 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

1200
sofian_solusign
Troubleshooter
J
Newcomer
justinemNewcomer
asked in Go-live
Go Live Review failed

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!

1212
J
Newcomer
V
New Voice
versatilevatsNew Voice
asked in eSignature API
Template as an attachment in signing request email

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

373
Michael.Rave
Docusign Employee
I
Newcomer
ibabbsNewcomer
asked in Salesforce/Apex Toolkit
DocuSign Apps Launcher - Writeback only after Envelope Status is completed vs. once a recipient signs

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!

801
I
Docusign Employee
G
Newcomer
Gui-awkNewcomer
asked in Go-live
Go-Live HTTP 404 Page Not Found

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​​​??!!!

1461
I
Docusign Employee
G
Newcomer
GurneeshNewcomer
asked in eSignature API
Get all the documents using the user id

Is there a Docusign endpoint that could govern me all the agreements in the user account. I am able to authenticate the user and get the info for the user

472
G
Newcomer
L
Newcomer
lk1919Newcomer
asked in Docusign Connect
DocuSign Connect not sending document field values via webhook

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?

841
A
Active Voice
D
Newcomer
devSSNewcomer
asked in eSignature API
Identity verification not available in sandbox account

Our company is in the DocuSign Partner Program and we have a developer/sandbox account in DocuSign, some of our clients are looking for the feature to have the signature recipients to verify their identity with Bank ID. All signature requests are sent from client instances to DocuSign, I am looking to add the verification feature in our DocuSign integration but the “Identity Verification” is not available on our sandbox account under “Signing and Sending”. How can I get this enabled? 

511
A
Active Voice
T
Newcomer
techbroNewcomer
asked in Navigator API
Navigator API scope throwing consent required error

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

730
T
Newcomer
M
Newcomer
Maurice_1Newcomer
asked in Go-live
Assistance Needed: Issues with Go Live Process and Missing Integration Key in DocuSign

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

852
M
Newcomer
A
Newcomer
alin.alqutobNewcomer
asked in eSignature API
Dynamic Template Update via API for Multi-Signer Workflow with Azure Integration

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

841
Michael.Rave
Docusign Employee
G
Newcomer
Gui-awkNewcomer
asked in Go-live
Go-Live Issues

Hello guys, I need help ASAP!!I’ve been testing on test environment, made my 20 successful api calls and now i’m trying to Go-Live by clicking on Actions > Select Go-Live Account. Then I proceed to log in and i get a HTTP 404 NOT FOUND error.

560
G
Newcomer
neethujkp
Troubleshooter
neethujkpTroubleshooter
asked in eSignature API
Embedded Signing for envelopes originating from different platforms

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?

645
Michael.Rave
Docusign Employee
C
Docusign Employee
Community UserLegacy User
asked in General
Does anyone have a familiarity with.p7m encryption?

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.

14865
M
Newcomer
A
Newcomer
atifmuhammadNewcomer
asked in General
Looking to hire a certified DocuSign consultants for a single project

Looking to hire a certified docusign consultant that can help implement specific features on a set of templates that I can re-use for all my clients

804
R
Community Moderator
Inbar.Gazit
Docusign Employee
Inbar.GazitDocusign Employee
posted in General
Introducing the Docusign VS Code Extension: Now in Closed Beta

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

1120
Inbar.Gazit
Docusign Employee
K
Newcomer
KasthuriranganNewcomer
asked in General
Mail Not received to Recipient Mail box in Developer account

As part of the development process, I am sending an envelope to the recipient through the DocuSign developer account (r**************@********) The email is successfully sent from DocuSign, as I can see the email content in the Developer Account Console page. However, the recipient does not receive the email in their mailbox, even after checking the Spam folder.Initially, we suspected it might be a firewall issue. I also tried sending the envelope to my personal email ID, but it didn’t work either. Although the email is sent from DocuSign, it is not received in the mailbox.Could this be because we are using the developer account?

1081
D
Newcomer
J
Newcomer
John HNewcomer
asked in eSignature API
Custom font support for DocGen API?

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!

743
J
Newcomer
A
New Voice
ACOUNew Voice
asked in eSignature API
Increase the size of the signature window.

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

415
Michael.Rave
Docusign Employee
N
Newcomer
npHacksNewcomer
asked in eSignature API
Click API 401

I am following this code sample and kept running into many errors.One of the error was that it could not find body so realized to use const result = await accountApi.createClickwrap(accountId, clickwrapRequest); instead of the following as given in code baseconst result = await accountApi.createClickwrap(accountId, { clickwrapRequest });But now I am stuck at 401 error, unable to understand the error at all. {  statusCode: 401,  header: Object [AxiosHeaders] {    'cache-control': 'no-cache',    'x-docusign-tracetoken': '86….,    'x-docusign-node': 'DA...',    'strict-transport-security': 'max-age=31536000; includeSubDomains; preload',    date: 'Thu, 23 Jan 2025 19:04:23 GMT',    'content-length': '0',    'set-cookie': [      'BIGipServerpool_Demo_API_Click=!SQ…..=; path=/; Httponly; Secure'    ]  },  body: ''}I am adding fresh access token://DOCUSIGN_CLICK_API_BASE_PATH="https://demo.docusign.net/clickapi"const docusignClick = require("docusign-click");... this.dsApiClient = new docusig

90
N
Newcomer
D
Newcomer
dolenc_1Newcomer
asked in eSignature API
Localization email and signing by API

Hey, I try to localize email and sing compent by signing user and I send by API envelop body: {  "documents": [    {      "documentBase64": "{{document}}",      "documentId": "123",      "fileExtension": "doc",      "name": "document"    }  ],  "emailSubject": "Custom subject",  "BrandId": "brand id from portal",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "{{recipientId}}",        "routingOrder": "1",        "localePolicy": {         "cultureName": "es-ES",          "languageCode": "es"        },         "tabs": {                    "signHereTabs": [                        {                            "anchorString": "/sn1/",                            "anchorUnits": "pixels",                            "anchorXOffset": "20",                            "anchorYOffset": "10",                            "stampType": "Signature"                        }                    ]                }      },      { 

522
D
Newcomer
neethujkp
Troubleshooter
neethujkpTroubleshooter
asked in eSignature API
Embedded signing client userid for Docusign webapp

When defining an embedded signer, we need to provide a clientUserId along with the recipient's name and email. The clientUserId is a sender-defined identifier for the embedded recipient, enabling the generation of a signing URL for them. How can this be accomplished when envelope is initiated using the DocuSign web app and recipient should sign using embedded signing in a custom built mobile app

1933
Michael.Rave
Docusign Employee
K
Newcomer
kapil775Newcomer
asked in Go-live
Issue with Go Live

Hi All,My docusign app has passed the initial Go-Live review. As next steps for Go-live, I am performing the below actions,Click on Actions button next to the docusign App. Click on "Select Go-Live account". Accept Terms and Conditions. Update docusign prod email id in the next screen and click on "NEXT".However I am getting below message after clicking on "NEXT". I have verified that the Docusign prod email id is having access to docusign prod. Request you to please help with this issue.Error message:User is not assigned to this application. Snapshot of the error:Thanks,Kapil

701
E
Docusign Employee
A
New Voice
ACOUNew Voice
asked in eSignature API
Zoom buttons not visible

Hello,Using REST API , zoom buttons arent visible until a signature has been drawn on the document , how can i fix it please ?regards,Arthur

250
A
New Voice
K
Newcomer
Krishna0707Newcomer
asked in eSignature API
Issues Generating Recipient Views for Multiple Signers and Receiving Webhook Events

I am using the DocuSign API to create an envelope with a document that requires signatures from three different signers. My implementation involves the following: Embedded Signing: I need to generate recipient views for all three signers. However, I am currently only able to generate the view for the first signer. When I attempt to generate views for the other two signers, it doesn't work. How can I resolve this issue to allow recipient views for all three signers? Webhook Triggers: I have set up a webhook with specific events configured. I need to be notified when the first signer completes their signing so I can generate the recipient view for the next signer. However, I am not receiving the event that indicates the first signer has completed signing. Which specific event(s) should I configure in the webhook to ensure I get notified when a signer completes their signing? Are there additional steps required to ensure these events are triggered and sent to my webhook endpoint? Any g

776
K
Newcomer

Badge winners

Show All Badges
Code of Conduct

Docusign Community

Code of Conduct