Developer

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 

Hi Team, I am using the DocuSign feature in my current application. Currently, we have two servers, DEV and QA, and I have only one developer (demo) account.What I need is, if I trigger the mail through my DEV server using the integration key, it should trigger the DEV URL in the webhook whenever an event happens for that particular envelope ID. I need the same functionality in the QA server as well, without any conflicts. If I use the same integration key for both DEV and QA with different webhook configurations in the webhook connect feature, what will happen? Also, what is the best/relevant way to approach this scenario? Regards,Adarsh

I have this error when i’m trying to send an envelope:"errorCode":"ACCOUNT_LACKS_PERMISSIONS","message":"This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document ..."this is the production account. Testing in the developer account i never get that error. What is the soultion for this issue ?  

I tried integration with Onedrive but, Error page is shown.I used personal account on microsoft.how can i integration with onedrive on docusign? It’s error page screenshot. 

Hi, It seems Navigator API is new. so previously developer need to load their list of documents by using envelopes api ?Imnot sure as well why navigator qpi right now is only have retreive a list of agreements and have no different than list envelope documents here I’m developing social medias app where I need to create docusign accounts on our backend (this is done by admin-docusign API right?), so user’s data synced with docusign and can be open with any docusign’s app integrated app.