Developer

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

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?

 send 3 documents in a DS envelope - Offer Letter (signatures) Non Disclosure Agreement (Signatures) Benefits Overview no signatures or field completion required.Candidates are saying they cannot see the last document which is a one page benefit summary.  I have no idea why, unless it is because that doc requires no signatures it is just informational?  Has anyone else had this?

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?

Hello,I’m currently integrating DocuSign into my ERP system using the API, and I’m working with a developer (demo) account.For several weeks, everything was working perfectly:Envelopes were successfully created via the API They were sent without any issues Recipients were receiving the email notifications and could sign documents normallyHowever, starting about a week ago, the behavior changed unexpectedly.Now:The API still works correctly (no errors returned) Envelopes are created and sent successfully Recipients are correctly assigned But no recipient receives any email notification at allTo troubleshoot, I have tried:Sending to multiple types of email addresses (personal, professional, temporary emails) Recreating a completely new developer account → it worked once for a single envelope, then the same issue occurred again

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.

Hello, I’m currently trying to understand the eSignature API (I’m new to docusign). Our UseCase is to create a template for a document we want to send out to customers for signature This template should contain “variables” that needs to be pre-filled before sending out to the signee (e. g. a Customer ID or Name) Sending should work via API.I created a template with several variables (I just put random variables for testing inside, they do not make sense) Within my API Call I am able to send out an envelope with the help of a template by { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email":

If you're building agent-driven workflows with Docusign and Salesforce, this is your starting point.This guide brings together the most relevant developer resources to help you connect agreement data to Salesforce, power Agentforce agents with real-time agreement intelligence, and design end-to-end workflows using Docusign IAM.👉 Have questions or want to share what you're building? Drop a comment below. We’d love to hear how you’re using Docusign and Agentforce together.Start with the architectureUnlocking Agreement Intelligence in Salesforce with Docusign IAM and Agentforce

Hi Team,We have a requirement where, based on a field update in Salesforce, we need to automatically void a DocuSign contract that has already been sent to the customer.I am new to DocuSign development and need guidance on the following:How to create a DocuSign Developer Account How to use DocuSign APIs to void an envelope that is already sent Best approach to integrate Salesforce with DocuSign so that, when a Salesforce field value changes, the related DocuSign envelope is automatically voided Any recommended best practices or sample implementations for this use caseIf anyone has experience with DocuSign + Salesforce integration or has implemented a similar scenario, your help or pointers would be greatly appreciated.Thanks in advance!

Hello everyone,I am currently integrating the DocuSign API for a client project and would like some guidance on the correct process to move from the developer demo environment to production.Here is what I have done so far.Step 1 – Create developer accountI created a developer account using my email: abc@gmail.com.Inside the developer dashboard I created an application and generated the required credentials:• Integration Key (Client ID)• Account ID• API base URL• RSA private key for JWT authenticationI have already tested the integration in the demo environment and API calls are working correctly.Step 2 – Purchase Developer Starter planNext I plan to purchase the Developer Starter plan from the DocuSign plans page:https://ecom.docusign.com/plans-and-pricing/developerThe p

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!

i am not seeing anything after successful login. tried multiple browsers incognitoconsole shows Uncaught TypeError: Cannot read properties of null (reading 'insertAdjacentHTML')Understand this error6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - WARN  2026-04-06T14:44:05.334Z Invalid eventBatchSize undefined, defaulting to 10e.consoleLog @ 6fe1b3b2-d77a1ad56503e866a7ae.js:1Understand this warning6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - WARN  2026-04-06T14:44:05.334Z Invalid eventFlushInterval undefined, defaulting to 1000e.consoleLog @ 6fe1b3b2-d77a1ad56503e866a7ae.js:1Understand this warning6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:05.445Z DatafileManager: Updating datafile from response6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:05.445Z PROJECT_CONFIG: Skipping JSON schema validation.6fe1b3b2-d77a1ad56503e866a7ae.js:1 [OPTIMIZELY] - INFO  2026-04-06T14:44:

Hi everyone, Via our DocuSign integration/ API, using recipients[].signers[].emailNotification.emailBody, we would like to customize the email message sent to each signer on a per-envelope basis as follows: - Embed protected images in that email message using CID (Content-ID). Is this approach supported by the DocuSign API? If not, we would greatly appreciate any suggestions or recommended approaches to achieve this functionality.Thanks!

Hi,I have a working DocuSign integration in the demo environment using JWT authentication and templates.When trying to move to production, I get the error:"These accounts don't support API integrations".I have already contacted sales multiple times but received no response.We are ready to go live and need API access enabled for our production account.What is the fastest way to enable this?Thanks in advance.

Hi everyone,I’m currently using the DocuSign eSignature API to create an envelope via Composite Templates. My setup involves two recipients with no signing order (parallel routing).To ensure tabs are visible to both parties, I have set the shared property to true for each tab within the inlineTemplates for the signers.The Problem: When the signing URL is opened, the shared tabs are appearing with a solid white background. I was expecting them to be transparent so they blend seamlessly with the document's underlying layout.My Questions: Is there a specific property I need to adjust / include to force transparency for shared tabs? Has anyone found a workaround to fix this? Any insights from the community would be helpful!Thank you,Quoc

Hello,>Working with the C# SDK<Using composite templates, i successfully created an envelope with 4 documents and 4 recipients (yay !)Document #2 is defined as display=”inline” and i added some tabs (SignHere, Text, DateSigned...) for recipient #1 and recipient #4 : works like a charm. Now my problem is with document #1, which is a supplemental document (display=”modal”). The goal is to set this document as “View and accept” only for recipient #4. Following the documentation I created a View tab and an Approve tab like this :Approve approveTab = new Approve() { DocumentId = "1", RecipientId = "4" };View viewTab = new View() { DocumentId = "1", RecipientId = "4", RequiredRead = "false", Required = "true", PageNumber = "1" };