Help Forums

Received this email with subject line:Important Update - Docusign Transactions Moving to Microsoft Azure, Action May be Required We currently have our Docusign integrated with Oracle NetSuite (SuitePeople) for our HR Onboarding. Is any action required on my end?

Hello,I am attempting to implement JWT Grant authentication for my DocuSign integration in a developer account (demo.docusign.net). I consistently receive the following error when making API calls (e.g., oauth/token endpoint):"Authenticatie mislukt (400): no_valid_keys_or_signatures"This translates to no_valid_keys_or_signatures.Here's what I've done so far:I have created an RSA Keypair within my DocuSign developer account for my Integration Key. I am using the Private Key from this newly generated keypair. I have confirmed that it's copied completely, including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- headers/footers, and that there are no extra spaces or missing line breaks. I have correctly set my CLIENT_ID (Integration Key), USER_ID (API Username), ACCOUNT_ID, and DOCUSIGN_BASE_PATH (https://demo.docusign.net) in my application's environment variables. I have performed the required user consent grant by navigating to the consent URL (https://account-d.d

Hi, I am using the C# eSign SDK and am trying to allow users to open a sender view for envelopes that they are not the sender on, but have been granted shared access to. i.e. User A creates a draft envelope and User B opens the sender view for that envelope.The documentation says I need to attach a header ( X-DocuSign-Act-On-Behalf) with the principal user id (User A’s id) as the value in order to act on their behalf.Here’s what I am doing generally in my code (language is Visual Basic). I am using the agent user’s (User B) access token and base uri:DSClient = New DocuSignClient(baseUri & "/restapi")DSClient.Configuration.DefaultHeader.Add("Authorization", "Bearer " & accessToken)DSClient.Configuration.DefaultHeader.Add("X-DocuSign-Act-On-Behalf", principalUserId)...EnvelopesApi.CreateSenderView(accountId, envelopeId) The problem is when I add the header and make the API call, I get an error back:{errorCode: “ACT_ON_BEHALF_USER_NOT_ALLOWED”,errorContent: "An 'Act on Behalf Of'

I receive notices that I have a document to sign; however, it tells me that the site can’t be reached and indicates that the connection was reset.  I can view the document but it gives the error when I click “sign”.  I even tried sending a document to myself.  I can send the document but it won’t even let me sign a document that I just created.

Is this change "Updated Home Page Experience" described in the 25.3.00.00 release notes, applicable to P11 module enabled accounts?

I read this help article, https://support.docusign.com/s/document-item?language=en_US&t=1756499814451&bundleId=izj1586134369853&topicId=xna1586134322115.html&_LANG=enus and it says at the bottom I should be able to create a text field for my signers in my Gen Template. Is this accurate? I do not have that option. Is there another way to add custom fields I want the signer to fill out on my Gen Template?  

We are creating a rather complex document / form for someone to sign.  They need to answer questions (yes/no and true/false) and are using conditional formatting for a few of them as well.  However, we would like to test out the form before sending it but it seems like the only way to test is to send it to ourselves.  Is there any way a document can be viewed/tested without going through the signing process?  It would be a big help!  Thanks.

Hello,I’ve reached out to our IT to help us with the requirements. They’ve responded with the below and recommended I reach out to you for a response:Your current Azure Network Security Group (NSG) configuration allows inbound traffic only on port 3389 (RDP). All outbound ports are set to default, which permits outbound internet access unless explicitly restricted.To ensure uninterrupted access to Docusign services, please provide the specific outbound ports used by the domains listed below, so we can validate and, if necessary, explicitly allow them in the NSG rules:demo-b.docusign.net na1-b.docusign.net na2-b.docusign.net na3-b.docusign.net na4-b.docusign.net eu-b.docusign.netOnce the required ports are confirmed, we will review and update the allow-list settings as needed, in accordance with the Docusign Trust Center IP and domain guidelines, before the December 31, 2025 deadline.Please advise on the specific ports required for outbound connectivity to the above domains.Thank you,Sv

I have selected 2 check boxes.  I have added one check box, clicked on the + sign and created a group. I have selected  “Select only one” under the validation tab.  When I send a test, it allows the signer to select both check boxes in the group. I have also tried selecting “at most one” under validation and the same thing happens. 

I’m doing some research to determine how my organization is using DocuSign.  I pulled the envelope recipient report just out of curiosity at first, because I thought it would be too detailed to be useful. However, I noticed that several recipients are getting large numbers of duplicates that I don’t think could possibly be from human error. For example, one recipient got the same document 141 times, as 141 different envelopes. I’m not having much luck talking to a human from DocuSign, but wonder what folks think. I also want to be able to determine if it’s an issue on our end, because we seem to have some automated sending...

Hello,I corrected an envelope to remove reminders. Upon completion, it said “sending”. Is it notifying all recipients?I am trying to avoid additional emails to recipients.Thanks!

docusign sign up error massage show ' your request can't be completed. Try again or contact support'

I am getting the following error in SF when attempting to save a template from DocuGenUnexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at input location [1,2] I have tried a very simple template with just some text and a Text field and I receive this error when I click on the Next button to save the template. Anyone have this issue and how can it be resolved?Thank you in advance for any suggestions.

Hello,I’ve seen a few questions on here about the frame around the signatures and initials, and the advice is to go into the admin account. However, I have a free personal account, so I’m not sure if this is a feature on my account. Is there any other way to remove this frame? It’s making it hard for me to read the other text.

Hello, I am working on a Docusign Webform connected to a template and I’ve run into an issue with field mapping. Specifically my Webform includes a “Phone Number Field” which is required under recipient connections (this is the phone number field type in webforms), but when I try to map it to a field on my template, it does not link. I believe this is because the phone number type field on the webform does not connect to a text field on a template. When I looked the template does not have a phone number validation field.  I have confirmed:the recipient roles match between the webform and template Other text and email fields map correctly between the webform and template The issue only occurs with the webforms “phone” type field. Could you confirm if the webforms “phone” fields are supported for mapping to template fields? If not, what is the recommended approach to solve this? If I replace the webform phone field with a text field, it will no longer map to my recipient connections unde

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My Azure web App Service to supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

I don’t know what to do! I signed up for Docusign Standard Edition for an initial 5 seats via Techsoup for $100 in March of 2024. On the Techsoup site is says:Perpetual License This donation provides a perpetual subscription for up to five users. It does not expire or need to be renewed.  Then in January 2025 I signed up for Docusign Standard Edition, 5 Additional Users, and on Techsoup is says: DescriptionThis product is only for organizations that are requesting or have already received Docusign Standard Edition.This donation allows organizations to add up to five additional user licenses to their initial subscription. You can request this offer up to four times to obtain access for up to 25 users total. Then this March, my organization just received a bill for $3000 minus a discount for $1500 for the initial five users, but leaving $1500 for the additional five users. When I go to open a case, it says that my account is not eligible to open a case. How can I actually contact Docu

​We don't need the last signer anymore and want to eliminate the unnecessary emails for that person.

Hello- I joined a new employer, and it appears we have never used templates before. What would be the best way to get this going? We do not have the option to save an envelope as a template either. 

Hi DocuSign Community,We’ve developed a system that integrates with DocuSign to access templates and send offer letters directly from our portal. In our setup, users log in to our portal with their DocuSign accounts, and from there they can access their templates and send offers through DocuSign using eSignature API.So far, we’ve been testing successfully using a Sandbox account. To move into production, we understand that we need a Partner Production account. We have already filled out and submitted the required form for this, but we haven’t received any response yet.Has anyone else experienced delays with this process? Is there a recommended way to follow up or escalate the request to get our Partner Production account enabled?Any guidance would be greatly appreciated.Thanks in advance!

I work at a credit union and use docusign often. The text that we put in the docusign message is not easily seen by members when they receive a message from us with instructions for what to do in the document and how to access it. Is there any way to increase the size and prominence of those messages?

Hello everyone,I’m encountering a problem when accessing the DocuSign Developer Portal:- URL: https://developers.docusign.com/platform/account/  - After logging in, the page stays completely blank (only the header appears).- In DevTools Network tab, the request to `/api/user/settings` returns HTTP 500.- On the console, I see the error:    TypeError: Cannot read properties of undefined (reading 'account_name')Steps already tried:- Tested in Chrome and Edge (both latest versions).- Cleared cache and cookies, used incognito mode.- Tried on different networks and devices.- Extensions like AdBlock are not the root cause.It seems the frontend cannot proceed without user settings.  Has anyone experienced something similar? Any workaround, or is there a direct way to reset or repair account settings?Thank you for your help! 

Hi everyone,I want to add multiple documents to one envelope. Each Document should only be signed once. Since all documents are duplicated from a template and I came up with the ideo of using a specific document propertie as signature anchor. But in my tests this did not work. (When I am using the same anchor in each document, each document has to be signed as often as documents are in the envelope)Has anyone an idea why this does not work or how it could work?Thank you all in advance.Best regardsJens

We host in-person meetings, and want the attendees of the meeting to sign the meeting document via a tablet that gets passed around.  We don’t know who the attendees/signers will be, or how many, but we want them to sign the document within our web application.  After a lot of experimentation with Docusign’s APIs, we’ve taken this approach:We create an envelope (POST to /restapi/v2/accounts/{accountId}/envelopes) with 100 allocated signers (the maximum allowed and hopefully more than will ever attend our meetings).  These are placeholder signers.  Our document also has 100 lines allocated for recording attendee information which feature anchor tags for recording the signature (\s1\, \s2\, etc.), anchor tags for the attendee’s name (\n1\, \n2\, etc.), and anchor tags for recording the attendee’s company (\c1\, \c2\, etc.)   As each attendee enters their information on the tablet, we call Docusign’s recipient-update API endpoint (PUT to /restapi/v2/accounts/{accountId}/envelopes/{envelop

I am very frustrated a I would like to cancel my subscription & get a refund. There seems to be no contact number or email address available to cancel.