Developer

Web Form In our travel form we use a formula to pull information from the form to act as the email subject.  I find the inconsistent use of underscores.The information being pulled from the form is from the Web Form Field API reference name and that information does not allow spaces:Travel Start DateAPI reference Travel_Start_Datethere are underscores in place of the spaces for the API referenceWhen you use the information in the formula, the underscores need to be removed:[[ECF:Travel Start Date]]When the email comes from Docusign there are underscores where the spaces used to be. Email subject 2026/05/14_Initiator_Firstname_Lastname_Travel_Destination_NameI’m not sure where this development evolved but the inconsistencies of underscore for spaces v

One of the recipient email addresses is no longer valid (inactive/incorrect email). The envelope status in Salesforce changes to "Sent", but DocuSign later fails for that recipient because the email address is invalid.Because Salesforce already marks the process as sent, we are unable to stop or handle  business process correctly.We want to know:How can we capture recipient email bounce/invalid recipient errors from DocuSign? Is there a webhook or DocuSign Connect event available for invalid recipient/email delivery failure? How can we send this failure information back to Salesforce automatically? What is the best practice to update Salesforce records when a recipient email becomes invalid after envelope sending? Has anyone implemented Apex REST + DocuSign Connect webhook for recipient delivery failures?

Hello DocuSign Support,We have completed the Go Live process successfully and are now in production, but every OAuth token exchange request is failing with the following error:  "error": "invalid_grant"  "error_description": "unauthorized_client"This has been confirmed via direct Postman testing with a correct request structure. Our technical team has ruled out all client-side configuration issues. We believe the root cause is that API access entitlement is not active on our production account. On our current IAM Starter plan, API access is listed as "Contact sales."We need the following resolved as quickly as possible:1. Confirm whether API access can be activated on our current IAM Starter plan or whether an upgrade is required.2. Provide pricing for the appropriate plan that includes full production OAuth token issuance.3. Activate API entitlement on production account ID 2********* immediately.This is blocking a live

I’d like to come back to the topic of getting shared access to DocuSign. Previously, we were granted shared access without the information that the access was for the entire profile and no old files could be hidden or deleted, due to that to protect some of the data, we revoked the access. However, upon checking possible solutions, Google says for DocuSign folders can be created with specific permissions, so it seems we could create a new folder for future documents only and grant access to others to that folder solely. The other option would be to move the old documents to a folder that would be restricted from view. Can you please explore these options and let me know if this solution would be possible? 

Hi everyone,I'm trying to connect to the DocuSign hosted MCP server (mcp-d.docusign.com/mcp) from an MCP client that follows the standard OAuth discovery flow, and I'm seeing what looks like an RFC 8414 deviation that I'd like to confirm before assuming it's an issue.The flow my client is doing is: Fetch https://mcp-d.docusign.com/.well-known/oauth-protected-resource. Returns 200 JSON, lists https://account-d.docusign.com as the authorization server. Per RFC 8414, fetch https://account-d.docusign.com/.well-known/oauth-authorization-server for the AS metadata. This is where I'd expect a JSON metad

I have had several people who were not able to access a DS agreement that I sent at all. She tried 3 different browsers, cleared cookies/cache etc.  Does anyone have any idea why this happens and what I might be able to do to fix this?  The first 2 signers in my organization were able to sign and when it gets to the third one - not in my organization she could not get to the document.  I double checked the email it was correct and she was using a computer and not on a phone.  I don’t want to make my first 2 signers sign again as they are executives and it is a bad look.  Is there another way around this?

Hi everyone,I currently have one application running in production, and now I want to promote another application from my Dev account to Production.Can a single DocuSign production account handle multiple applications/integrations?If yes, what impact could this have on the existing production application (API keys, integrations, users, limits, etc.)?If not, what is the recommended approach for running multiple applications in production? Should we create a separate DocuSign production account, or is there another best practice?

Hi Team,We are facing an intermittent issue while integrating with DocuSign using the Node.js SDK.Issue DescriptionWe are calling the createEnvelope API from our Node.js application. In some cases: The API call times out (60 seconds) on our side However, the envelope is successfully created in DocuSign within ~7–10 seconds A webhook (Connect event) is also received successfully The problem is that the API response is not received by our applicationExpected BehaviorThe createEnvelope API should return a response with envelopeId once the envelope is created.Actual Behavior Envelope gets created successfully Webhook is triggered But the API call results in:

[Posted originally on Partner Innovation Community, but this is probably a better place to post]Hi all — Rafa from Simple Proof here 👋 Quick intro: we're a DocuSign ISV partner. We've built an Extension App that generates cryptographic proofs of completed envelopes and anchors them to the Bitcoin blockchain. In plain terms — when an envelope completes, we hash the final signed PDF and create a tamper-proof timestamp that anyone in the world can independently verify, forever, without trusting us or DocuSign. Our customers include government agencies and election authorit

Hi all,First post here so be patient with me :)I created a template a few pages long with signature and date of signing lines.The workflow is:Fill out form on web app Web app uses form data to replace text in a word file (agreement) and in turn, sends form data (recipient) and document to DocuSign to create envelope. The template is also set in code for use.Intended outcome:Client opens document, clicks to sign and date - job done.Actual outcome:Client opens document, nothing to click - no signature or date fields present.Envelope Inspection:Looking at the document in the created envelope, the signature and date fields are not there (although the template is applied). The document does not show page breaks in this view either.Manual Test:I clicked “Use” on the template, entered recipients and clicked next - signature fields are there

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!

https://support.docusign.c> Document file limit:om/s/articles/DocuSign-Document-and-Envelope-File-Size-Limitations?language=en_US)Hello, I have a question similar to In my envelop, we send the following files which I converted to base64 : ```Size Name299k 69e772f5b28637.57190393.pdf.b64521k 69e772f5cf6a18.49898668-1.pdf.b64521k 69e772f5cf6a18.49898668.pdf.b641.5M 69e772f5f03d22.08961500.pdf.b644.1M 69e772f6b8acf3.84730872.pdf.b641.0M 69e772f7bc72c.pdf.b644.0M

Hi DocuSign Community,I am currently in the planning phase of integrating DocuSign eSignature into our real estate agency platform, which consists of a Laravel-based web portal and a Flutter mobile application (iOS & Android). I have a few questions regarding licensing and API integration that I hope the community or DocuSign team can help clarify seeing the email support only for trial/paid account. Even the chat doesn't work for me no matter how i tried to initialise it.---LICENSING & PLAN QUESTIONS1. We are planning to use a single DocuSign account/license across our platform, where multiple agents will be sending documents to clients for e-signature on a daily basis (after each case submission). Is this allowed under a single license, or does each agent require their own?2. What is the envelope (document) sending limit per month or per year under the Standard or Business Pro plan? If agents are sending documents daily, is there a risk o

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

It is quite important to allow closing vulnerabilities, could one please review and accept this pull request https://github.com/docusign/docusign-esign-php-client/pull/253 to allow make our system safer and also make your system safer since it’s related to the communication between the two.

Hi DocuSign team,I'm stuck in a loop trying to enable SMS and WhatsApp delivery on my developer sandbox account. I've been advised to open a support case, but support.docusign.com won't authenticate me. What I need:  Enable SMS and WhatsApp delivery on account 7ba44489-edcb-4415-9dd9-3632e018480c.What I've tried:  1. Viewed a post on this community with the same request. The reply     redirected me to open a support case.  2. https://support.docusign.com → Log in     - Tried "eSignature and IAM Applications" category → password       rejected every attempt (same credentials that work on       apps-d.docusign.com and developers.docusign.com).     - Tried "Docusign Partner" category → same rejection.  3. Attempted to sign in at developers.docusign.com and navigate     to a support form from there — no developer-specific case     portal is exposed afte

Hello Team,I need to integrate DocuSign's signature and editable text functionality into a React Native application. I haven't found any tutorials, guides, or SDKs to help implement this. Could you please provide guidance on how to achieve this functionality in our application?

I have a template that has a single signer that is a signing group. I need to create an envelope from this template using API calls.  The API requires an email and ends up creating a new signer in addition to the signing group that’s in the template. Is there a way to create the envelope so it only has the signing group as the single recipient?

Can’t get past this in my APEX code: Method does not exist or incorrect signature: void getEmbeddedSigningUrl(Id, System.Url) from the type dfsle.SigningService.More context: String returnRedirect = 'https://<someURL>/s/paperwork-complete'; Url signingUrl = dfsle.SigningService.getEmbeddedSigningUrl(myEnvelope.id, new Url(returnRedirect)); return signingUrl.toExternalForm();

We would like to integrate an Aadhaar-based e-Signature API into our application, where as developers we can send a PDF document and allow the end user to complete Aadhaar e-sign on it.Could you please provide guidance on the following: How to use the Aadhaar e-Sign API for uploading and sending a PDF for signature The complete integration steps and workflow involved How the end-user authentication (Aadhaar OTP/biometric) is handled in the process Steps to configure and enable this feature in a demo/sandbox account for testing Any required API credentials, documentation, or prerequisites to get started We are currently in the initial integration phase and would like to test the functionality in a demo environment before moving to production.Kindly share the relevant documentation, API references, and onboarding steps.Thank you.

Hello.i’m working with a microservice API to connect my applications with Docusign APIs.I have an issue that my client web application are not alowed send document to my API for business rules reasons.There is any option to upload the document within a empty envelope over a presigned URL, that my API generates in Docusign APIs and then my web client just upload the document directaly?I have searched over API documentation but didnt found anything

Is it possible to set reminders and different reminder frequencies for each user? In other words, so that all the envelopes sent by a user have different reminders and frequencies. ¿Es posible establecer recordatorios y frecuencias de recordatorios diferenciadas por usuario? Es decir, para que todos los sobres que envíe un usuario tengan unos recordatorios y frecuencia diferenciados. Would it be possible to include in the API the option to choose the reminder frequency for each envelope? ¿sería posible incluir en la API la posibilidad de elegir la frecuencia de recordatorios por sobre? Is it possible to include in the API the ability to send copies without requiring a signature? In other words, in Docusign we can decide whether the person receives only a copy or, conversely, must sign—would this be possible in the

I want to create an envelope that would contain multiple documents using envelopes endpoint of docusign api. Here is the main requirement Sending multiple documents in a single envelope Once all the signatures are captured for all documents receiving the webhook callback Confirming that: All signed documents are returned Currently we are creating a single document per envelope and while creation we send custom field with a documentId. This field is returned in the webhook call from Docusign which help help us with downstream process. If we are able to receive multiple signed documents in a single webhook call, is there a way to have the unique identifier for each document in the response from webhook?

My integration key shows as Live in the developer portal, but when I try to authorize against production (account.docusign.com), I get 'The client id provided is not registered with Docusign.' My production account also shows no integration keys available. Go Live form was signed and counter-signed (Envelope ID: 132D960E...). This has been unresolved for over a week

It looks like the new SP cert has a different key from the 2026’s. - The pub keys(modulus) are different.2028 Docusign SSO Self-Signed CertificateOur IDP (Oracle IDCS) doesn’t allow to import multiple signing certs for an SP. It would have been transparent if the cert was renewed with the same key but it doesn’t seem the case. I’m thinking that I might as well tell the business team that we need to react after DocuSign has started using the 2028 cert,  but it’d be great if I’ve missed something and anyone can suggest a way to make the transition without an interruption.