Developer

Goal: Embed signing in our web app via an iframe with a working change language function.When we render the signing URL in our webpage, in an iframe, and then we try to change the language as in the screenshot below:  We get  apps.docusign.com refused to connect error message Front-end logs shows also:Framing 'https://apps.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://apps.docusign.com". The request has been blocked.Have anyone faced this issue before, and is there a workaround to make this change of language function actually work in embedded signing?Account type: developer/demo. Thanks!

Hello, unfortunately the collaboration option does not appear when drafting a document. Information:- Trial user (meant to have access to trial Business Pro features, including collaborate)- Text field (in text field properties, no option for collaborate appears)- I haven't tried other fields because I am only interested in a collaborative text field- 5 recipients to sign, with a signing order applied- doesn't appear on my mobile app or mobile webbrowser (in desktop view) Please help asap.I have a document due to be sent for signing and without all the features to trial, how do I know if I want to progress with the paid version.

We have a case where we created a DocGen dropdown list in a template created in Word and using the Docusign Template Assistant.Our requirement is that we can populate the select field dynamically in the EnvelopesApi C# SDK.And that the dropdown needs to be editable for the signers.What is happening is that the value we set in the code appears on the document but only as a label. There is no dropdown on the sent document, only the read-only field.Is this even possible and if so, how? Thank you.We would assume that a dropdown presents selectable options to users. Is this expected behavior? If so, what is the use case for it?Code example is below.This is how we create the fieldreturn new DocGenFormField{ Label = "SomeLabel, Name = "FieldName, Type = "Select", Options = (this is a List of DocGenFormFieldOption with label and selected set. e.g. label = "option 1", selected = "False", label = "option 2", selected = "True".};Which is passed to this method. We know it is correc

Hi everyone,After completing the Go-Live process for our integration, I'm unable to complete JWT consent because our production account has zero registered Redirect URIs, and any attempt to add one fails.Setup:Integration Key created and verified on a Developer account, then promoted to Production via Go-Live RSA keypair generated successfully on the production app (visible under Apps and Keys → App Details) Authentication Method currently shows as "Authorization Code Grant" with zero Redirect URIs registeredThe problem:Going to Apps and Keys → [App] → Edit → Add URI → entering a valid HTTPS URL → Save consistently returns:"This integration key could not be updated. Please try again in a moment."Tried: multiple browsers, incognito mode, multiple URLs, retrying over several days. Same error every time.What I found in the docs:DocuSign's own "After Go-Live" guide states Redirect URIs should be configurable on the production account ("OAuth Management Account") directly. It also mentions

planning to integrate DocuSign eSignature with a SharePoint Framework (SPFx) web part.RequirementsUsers submit requests through a SharePoint Online site. Upon submission, a DocuSign envelope should be created automatically and sent to designated recipients for e-signature. The organization has a single dedicated DocuSign service account. SharePoint users are not DocuSign users and should not be required to log in to DocuSign separately. Recipients should receive DocuSign emails directly and complete the signing process through DocuSign. The signed document and envelope status should be stored and tracked within SharePoint. Due to project constraints, the current approach being considered is calling DocuSign APIs directly from the SPFx web part.QuestionsWhat is the recommended enterprise architecture for this scenario? Can a single DocuSign service account be used to create and send envelopes for all SharePoint users? How should authentication be handled between SharePoint Online, Micro

Hey Developers,I am trying to implement the DocuSign Embedded Focused View in a demo project (Just plain HTML and JS, with NodeJS backend), but I've run into an issue where the top header doesn’t go away. Screenshot below :  I am trying load the signing url in an i-frame.When looking at the official the Focused View example (here : https://docusign.github.io/app-examples/embedded-signing/) it looks incredibly clean and has no header at all. However, my implementation still looks like the standard embedded signing experience. Here is what I've done so far: I am using the docusign.js library. (<script src="https://js.docusign.com/bundle.js"></script>) I've set up the configuration object to target my container div. The token and return URLs are generating correctly without throwing backend errors. Here’s my code snippet : <body> <div class="signing-wrapper"> <h1>Internal App Checkout</h1> <p>Click the button below to sign you

We are using Signer Attachment tabs in a multi-recipient envelope. After completion, we can retrieve documents using Envelopes API, but there is no clear way to determine which signer uploaded which attachment. What is the recommended approach?

The Docusign Apex Toolkit provides predefined Apex methods, classes, and utilities, acting as an SDK. It encapsulates certain Docusign eSignature API functions, enabling developers to integrate Docusign and Salesforce features directly within their Apex code.While standard Docusign workflows use the Docusign eSignature for Salesforce UI, the Apex Toolkit grants access to Docusign eSignature API functionality. This access allows for greater customization and automation of workflows and processes. Templates are pre-defined, reusable document packages that streamline the process of sending documents for signature. They allow you to set up documents, recipient roles, merge fields, signing fields, and workflow settings in advance, so you don't have to configure them from scratch each time.This works great when you send an envelope from a template using the “Send with Docusign” button. However, there are a few caveats when sending a template using the Apex Toolkit as some settings defined on

I’m trying to request a phone call and it’s not working. I need to talk to support! I will not be renewing if it’s this hard to get support.

Hello,  I would really appreciate your help. Using the API, our envelopes are created and sent with the correct prefilled values. However, when our customers open the document for signing, one of the fields (“Title”) is covered by an editable textbox with some unrelated value.This is the document before signing (created with the correct prefilled valued, Name and Title):  And this is how customers see it when signing: The correct value (“1st Degree”) is underneath a textbox with “Staff”. We have no clue where it gets this default value from or how to edit out the textbox. I’ve recreated this field several times in the template and the issue still persists. This is what the template looks like: The backend is a simple POST request to DocuSign Base URL with this information: request_data = { "templateId": config["Processes"][process]["Template"], "templateRoles": [ { "email": signer_email, "name": signer_name, "roleNam

Hi,    Message: You have reached the maximum number of recipients permitted  for a single transaction in your account. Please ask your administrator  to increase your limit.  What we've tried:  1. Voided and deleted all envelopes on the account — error persists  2. Created a brand new developer account — same error occurs after ~20 envelopes  3. Verified only 4 unique recipient email addresses are used across all envelopes  4. Each envelope has exactly 2 signers, 0 CC — well within the documented 5-recipient per-envelope  limit  5. Billing & Usage page shows "Envelopes: Unlimited"  Account details:  - Environment: Demo (account-d.docusign.com)  - Account ID: *information removed due to PII*  - Integration Key: *information removed due to PII*  - HTTP User Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_452) (server-side integration)  Questions:  1. What is the cumulative recipient limit for developer accounts, and what is the timeframe  (daily/monthly)?  2. Is there a way to reset this

Hi!Just to report here so maybe the DocuSign team can review:The focused-view signing widget (signing_iframeless_mobile.js) fetches an Optimizely datafile (https://cdn.optimizely.com/datafiles/5V51g7L7XPgn5JrK1VcqS.json) during initialization. When that request fails, which happens for any end user running an ad blocker (uBlock, AdGuard, piHole, etc.) the widget shows its loading bar for ~30 additional seconds before rendering, even though the datafile request itself fails within ~2 seconds.The console shows [OPTIMIZELY] ERROR DatafileManager: Error fetching datafile: Request error early, then appLoadTime.end ~30 seconds later, immediately before the ready event.This Optimizely issue should not block the render for that amount of time.Classic (default) view mode works just fine.

Hello Everyone,I am currently exploring the integration of DocuSign with SAP SuccessFactors and would appreciate guidance from anyone who has implemented this solution.I would like to know:Is there a pre-delivered or standard extension/connector available for integrating DocuSign with SAP SuccessFactors? If yes, could you please share where I can find the documentation, installation guide, or configuration steps? If no standard integration is available for my use case, would the recommended approach be to develop a custom integration using the DocuSign APIs? For those who have implemented this before, what architecture did you use (standard connector, SAP Integration Suite/CPI, custom APIs, etc.)?Any best practices, lessons learned, or reference materials would be greatly appreciated.Thank you in advance for your assistance.

We are unable to use checkbox in the payload as it not recognizable inside the Oracle Integration Cloud iPaaS "checkboxTabs":[     {       "tabLabel": "Terms_And_Conditions",      "selected": "true"     },     {       "tabLabel": "Newsletter_OptIn",      "selected": "false"     }]

Hi DocuSign Community,We are testing the Navigator Agreements List API and wanted to confirm whether combining $search and $filter is currently supported.Request:GET /v1/accounts/{accountId}/agreements?$search=sample&$filter=status eq 'completed'Response:{"title": "Bad Request","status": 400,"detail": "The $search and $filter query parameters cannot be combined in the same request. Use $search for full-text search or $filter for structured filtering."}Observations: $search works correctly when used alone $filter works correctly when used alone Combining both returns 400 Bad Request However, in the DocuSign completed documents experience/UI, searching and filtering together appears to work correctly and returns expected results.We would like to confirm: Is this a current limitation of the Navigator Agreements List API? Is there any supported workaround to achieve combined search + filtering? Is support for combining $search and $filter planned for a future API version? Any c

I am using the createEnvelope endpoint using the structure envelopedefinition > compositetemplates > inlinetemplates > recipients > signers. For each of my signers, I want to customize the email body/message e.g. “Hi [Recipient1_Name], ...” but I don’t want this message to appear on the ERSD modal (see screenshot below) that pops up once they have completed two-factor authentication. I tried using the note string, but it has the same effect. Any thoughts that don’t mean updating this globally?   

It looks like the Agreement Manager - (formerly Navigator) API is currently a closed beta. How do I gain access?

Hi Team,I have created data labels for check box in DocuSign template and tried to populate check box data label through OIC. But we are not able to set the check box through value populated in check  data label.Attached documents for references.

Hi everyone,I'm facing a strange issue with DocuSign Demo connector in Power Automate.Everything was working perfectly fine, and suddenly, without any changes on my end, I'm getting this error when trying to send an envelope:❌ RECIPIENT_LIMIT_EXCEEDED - "You have reached the maximum number of recipients permitted for a single transaction in your account."The weird part is that my template only has 2 recipients:- 1 signer (Responsable)- 1 receives a copy (Demandeur)I ran the exact same flow twice within the same hour. The first run at 13:12 succeeded (status 200), and the second run at 13:57 failed with this error — same template, same configuration, nothing changed.I've already checked:✅ Admin settings → no recipient limit configured✅ Sending Settings → no restriction found✅ Monthly envelope usage → 26 envelopes, limit is UnlimitedHas anyone experienced this issue? Could it be a temporary throttling on Demo accounts after sending many test envelopes in one day?Any help would be appreci

We are experiencing an intermittent connectivity issue with the SAP SuccessFactors (SF) – DocuSign integration. Occasionally, when recruiters send offer letters from SuccessFactors to candidates through DocuSign, the system displays a connection/disconnection error.Observed Behavior:The issue is not occurring consistently and is difficult to reproduce. When the affected user refreshes the URL/page, the process resumes and works normally. No permanent failure is observed after the refresh. The issue has been occurring intermittently since October 2025.Request for Guidance:We would like to understand:What could cause these intermittent connection failures between SuccessFactors and DocuSign? Are there any known issues related to session timeouts, API connectivity, authentication tokens, or integration endpoints that could result in this behavior? What logs (Connect logs, API logs, envelope logs, or integration logs) should we review to identify the root cause? Has anyone in the community