Developer

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

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

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.

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.

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

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

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?

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

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"                        }                    ]                }      },      { 

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

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

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

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

One of our customer is using Docusign embedded signing within their app. The app release is being blocked by the app store because DocuSign is requesting location access. Could you please provide instructions on how to disable this request or share the appropriate documentation explaining why DocuSign requires location access?

Hey DocuSign Community!I'm developing a file archive extension and see that the Google Drive and Dropbox extensions in the App Center allow users to select specific storage locations (folders/drives) during the Maestro workflow configuration. (see screenshots) However, looking at the File Archive Extension documentation and reference implementation, I don't see how to implement this functionality. The action definition only shows a single URI parameter: "params": {"uri": "https://example.app/api/archive"}Any guidance on what needs to happen in the file archive extension to allow users to select storage locations would be great. Thanks in advance!   

Hello, my user reported an error message “Form Not submitted” and I added ?debug=1 to the end of the web form URL and received the below error message, anyone know what this message means and how to fix it? 

While upgrading my module to jdk21 and spring boot 3.3.1, getting error as below:Error Log:Forwarding to error page from request [/docusign/JWTtoken] due to exception [RESTEASY004655: Unable to invoke request: jakarta.ws.rs.ProcessingException: RESTEASY003215: could not find writer for content-type application/x-www-form-urlencoded type: jakarta.ws.rs.core.Form]: jakarta.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request: jakarta.ws.rs.ProcessingException: RESTEASY003215: could not find writer for content-type application/x-www-form-urlencoded type: jakarta.ws.rs.core.Form        at org.jboss.resteasy.resteasy-Is docusign 6.0.0, compatible with jdk21 and latest version of spring?

Getting the cors error while getting the access token. Please check the following screenshotCors ErrorAdded the origin URI’s in the Docusign APP.Enabled the CORS.Eventhough getting the error. Could you please help me in resoving it?

I’m using the DocuSign Node.js package to create an envelope in my Next.js application. I have imported the necessary classes from DocuSign as:  import { ApiClient, EnvelopesApi, EnvelopeDefinition, TemplateRole } from 'docusign-esign'; But, it seems like I am unable to use the “EnvelopeDefinition” method. I have it as:  // Prepare the envelope detailsconst envelopeDefinition = new EnvelopeDefinition(); The issue I’m having is that I get the message; “'EnvelopeDefinition' only refers to a type, but is being used as a value here.” when try to initialize the envelope definition. What am I doing wrong? Can someone please asssist?    

I’ve just installed Docusign eSignature for Salesforce: The trusted eSignature solution from the App Exchange. The account appears as properly connected to Docusign; however...when checking User Management, the only user (the admin) is set to an active status, but based on a Youtube tutorial, the radio button next to “Active” is not set to green. I wonder if this will affect me ? If so… how can solve this problem ?  

Getting error: JSON heap size limit exceeded while uplaoding document of 4.3 KB from Salesforce: At this line:                 myEnvelope = dfsle.EnvelopeService.sendEnvelope(myEnvelope, false);, this error is returned . Please suggest