Embedded Signing

We currently use a DocuSign button on the Salesforce Contact record to manually send DocuSign envelopes, and that process works correctly.We are now automating this workflow so Salesforce will:Automatically create a DocuSign envelope using a DocuSign Template Generate and store the recipient signing URL on the Contact record Sync that URL to Account Engagement (Pardot) Use the signing link inside Account Engagement emails However, we are unable to generate the signing URL programmatically, and we need assistance identifying the correct configuration or method to create the Recipient View (signing link) via Salesforce automation.

We're using the EnvelopeViews: createSender endpoint to embed the tagger/sender view in our application. We need to control the display language of the embedded sender view based on the user's account language.Following the documentation, we append the locale query parameter to the URL returned by the API: https://app.docusign.com/...?locale=deThis approach works correctly for the recipient view (createRecipientView) — the signing UI displays in the expected language.However, for the sender view (createSenderView), the locale parameter appears to be ignored entirely. The UI always displays in English regardless of the locale value.Our setup:Using the new API format with EnvelopeViewRequest (settings object with startingScreen: "Tagger", sendButtonAction: "redirect", etc.) The locale parameter is appended as a query parameter to the returned URL (e.g., &locale=de) Tested with multiple locale values (de, fr, etc.) — none ta

We are using Docusign JS library for embedded signing experience. In chrome browser, when we load the url, it is adding iframe in DOM and then opens modal to accept terms.In edge browser, it just hangs and never open the modal to accept terms with exceptions below.   

I'm using embedded signing in my app. It redirects from my web page to the DocuSign signing page, and after the user finishes signing, it redirects back to my web page. I want users to receive a completion email once they've signed, just like when they sign via email. Is that possible?  Do I need to modify the code, or can I do it through platform settings?  

Hi I am a new user to Docusign and have sent one document out for signature. A client has signed a contract but the wrong company name is shown in the signature box. I do not think this was a requirement specified when requesting signatures, how do I correct this?

​Hello,​I am trying to achieve a specific email notification workflow with the eSignature REST API, but I'm running into an issue.​My Goal:​I have an envelope with one embedded signer (clientUserId) and several CC recipients (carbonCopies). My desiredworkflow is:​The CC recipients should receive NO email when the envelope is sent.​After the embedded signer completes the signing, both the embedded signer and all CC recipients should receive the final "Completed" notification email.​What I've Tried:​I have tried two approaches, but both have failed:​Attempt 1: Using routingOrderI set routingOrder: 1 for the signer and routingOrder: 2 for the carbonCopies.​Result: The CC recipients still receive an email immediately when the envelope is sent. This email contains a "live view" link to the in-process document.​Attempt 2: Using suppressEmailsI kept routingOrder: 2 for the CCs a

Hi everyone, My name is Valeriya, and I’m a product manager at fintech startup that helps people refinance their high-interest credit card debt into one lower-interest loan, with a single monthly payment and a clear debt-free date. We’ve successfully tested the DocuSign API and SDK in the sandbox environment to enable digital loan agreement signing between our company and our clients. Here’s how it works in our app:1. The loan agreement is generated on our side and sent to DocuSign via API.2. The client receives a link to the signing ceremony directly in the app.3. DocuSign opens in the in-app browser, allowing the client to sign the loan agreement easily on their mobile device. We’ve now purchased a commercial plan under and want to move to the production environment.I’ve already completed the ISV Embed Developer Account form for our app. How can we get someone to: 1. Review our ISV Embed for

Hi everyone, My name is Valeriya, and I’m a product manager at fintech startup that helps people refinance their high-interest credit card debt into one lower-interest loan, with a single monthly payment and a clear debt-free date. We’ve successfully tested the DocuSign API and SDK in the sandbox environment to enable digital loan agreement signing between our company and our clients. Here’s how it works in our app:1. The loan agreement is generated on our side and sent to DocuSign via API.2. The client receives a link to the signing ceremony directly in the app.3. DocuSign opens in the in-app browser, allowing the client to sign the loan agreement easily on their mobile device. We’ve now purchased a commercial plan under and want to move to the production environment.I’ve already completed the ISV Embed Developer Account form for our app. How can we get someone to: 1. Review our ISV Embed for

What I wanted:I need to use both Remote Signing & Embedded Signing in a single DocuSign template (Single Signer). My goal is to redirect the user to a custom page once they complete the signing process, whether they sign through the flow page or via the email link I send for the signature in DocuSign.What I've already tried: I have tried implementing both BrandId (for remote signing) and ClientUserId (for embedded signing) in the same template. This approach is working fine for embedded signing, but I am facing issues with remote signing: The exception is thrown when using remote signing, and the user is not redirected to the custom page after signing. What I know: Signing Completed URLs can be set in In-session Landing Pages. In-session Landing Pages are an account-level setting

Hi,I am updating an embedded signing flow that uses a iFrame element on a page to use the Docusign JS method defined here (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/#docusign-js). I get the recipient URL and pass it to the following code:  var iframurl = "{{iframeUrl}}"; window.DocuSign.loadDocuSign('xxxx').then((docusign) => { const signing = docusign.signing({ url: iframurl, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary but

I’m getting the following permissions policy error when using DocuSign JS on my website. I’ve updated the page headers to set the correct Permissions Policy.{ key: 'Permissions-Policy', value: `geolocation=(self "https://apps-d.docusign.com")`} [Violation] Permissions policy violation: Geolocation access has been blocked because of a permissions policy applied to the current document. See https://goo.gl/EuHzyv for more details.(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2ready @ signing_iframeless_mobile.6672.js?cs=cfe5a6fc98b421a49266:2(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=e7c9df7fb0be52f728b3:2(anonymous) @ signing_iframeless_mobile.js?cs=d822fccc2:2(anonymous) @ signing_iframeless_mobile.5132.js?cs=36825c07c67f2dd22f3b

I am working on a project for a contract management system. The data resides on a SQL Server backend. I need to create Docusign Templates for many state-specific and generic contract documents. I am familiar with Salesforce merge fields, but I need the same capability for this project. I understand I may need to build a custom connector in order to connect to SQL Server databases. I need help or guidance on how to go about this.

We are currently using the DateSignedTab for the embedded signing. However, we are located in Kuala Lumpur, Malaysia, but the timestamp is showing SGT (Singapore Time. Is there any way to change the timestamp to reflect our current location? 

Hi, we are working on a DocuSign integration allowing users to sign documents in-app. We do have requirements to allow users to forward the signature to external users. We initially create the Signer record with a clientUserId (so the user can sign in-app using the embedded signature), and to forward the signature, we are trying to update the signer record with the external user info and remove the clientUserId value so Docusign would send out an email inviting them to sign the envelope. However, when updating the Signer, and not specifying the clientUserId (as the documentation mentions), the clientUserId persists. Updating the clientUserId to another value does work, but deleting it doesn’t. Any recommendations here?

Hi,I'm using the C# Quickstart project for embedded signing with the focused view, and I'm running into an issue when using agent recipients.Goal:The sessionEnd event should trigger when the agent completes their part of the signing session.What's Working: Embedded signing is working for both agent and signer. The ready event is triggered properly. The sessionEnd event does trigger correctly for signer recipients. Issue:The issue occurs only for agent recipients. After clicking the Done button on the completion popup, the iframe shows an error message. At this point, the sessionEnd event is not fired.This behavior happens consistently when the embedded recipient is an agent. Signer re

Hi, Couple of customers have complained that after embedded contract is showed, that page is grayed out and they can’t operate with contract, buttons are not clickable “Contract stays greyed out, I cannot scroll or read any other sections of the contract, cannot check boxes, cannot sign”Do you maybe have some idea why?

Hi, I am new to Docusign and I am working on a POC for integrating DocuSign Embedded Signing using Docusign JS  within a Vue.js application. I am using the DocuSign Python Quick Start project to generate the signing URL with a slight modification:Instead of redirecting after generating the signing URL, I print it to the console. I manually copy this URL into a static variable in my Vue.js app and load it Docusign JS ProblemWith a fresh signing URL:✅ I receive the ready DOM event callback.✅ The signing session renders successfully inside the <iframe>.✅ After completing the signing

Hi, We have not specified any FrameAncestors or messageOrigins for displayFormat: “default”I can see a loading icon on the screen Are those required even for Default view??Thank you

Hi,We have implemented Embedded Signing - FOCUSED View in our PWA (Progressive Web Application)In Browser its working fineIn Native app, its throwing cors error, and also I found out from the documentation that Docusign doesn't support localhost in prod.Host_Origin forAndroid: http://localhostIOS: capacitor://localhostSo, what are the options we have??Thank you

Hello; I have an iframe working on PCs and tablets, yet wen it runs on a mobile, it doesnt work fine…I can simulate de mobil device and it runs well: yet in the pyshical mobile device doesnt run. I can see the verification SMS mobile code requeriment and when the code is putted well, the iframe is all white.this is the iframe code: <iframe src="https://eu.docusign.net/Signing/MTRedeem/v1/8f1a8bab-a95b-4a55-b51d-6125de424ad7/eu?slt=eyJ0eXAiOiJNVCIsImFsZyI6IlJTMjU2Iiwia2lkIjoiYmJkYmJmODItODNkZi00ZmFiLWEyYTYtN2U5NmIwNGFkNzlmIn0.AQYAAAABAAMABwCAbUvJz1vdSAgAgA1dUPFb3UgYAAEAAAAAAAAAIQDpAgAAeyJUb2tlbklkIjoiYzMyZjkwZDAtOGYyMy00MzZhLWFlNTctN2Q1MDgxZGRkZjAxIiwiRXhwaXJhdGlvbiI6IjIwMjUtMDMtMDVUMTA6Mjg6MzUrMDA6MDAiLCJJc3N1ZWRBdCI6IjIwMjUtMDMtMDV

Hello,  I’m trying to display the embedded signing view using DocuSign's focus view, but I’m encountering an issue. Here’s the screenshot and the error message from the console log. This is occurring in my local environment.  Could someone please help me understand why this is happening? Below is an example of the code I’m using. I’d really appreciate it if you could point out anything I might be doing wrong. Thank you! 

I am working on a PoC for Integration with Docusign and using Embedded Signing with Focussed View because we have our website and don’t want Admins to go out of application context.I have 2 options to display the document to end user Load the document in the same application window by loading DocusignJS and passing it RecipientViewURL and ClientId. Cross Launch the RecipientViewUrl obtained by making CreateEnvelope and CreateRecipientView API calls.For my integration, I am making Docusign eSignature API calls from a backend service and passing on the URL to the frontend portal.I am also working on using Connect APIs to receive a callback when Envelope event is raised (completed, voided and declined). I want to understandWhat event is raised when the enduser views the Document but Does not perform any action and the URL expires. Close the browser without taking any action

Hey there, currently I’m integrating the bundle.js to my application to sign an agreement. I’m using a dialog to present this document, this dialog can be closed or opened, I was looking for a way to clean the event listeners of the signing but I can’t find any information about it.  I’m using React, there’s any way to remove the listeners associated when unmount the docusign embed document?

I have used embedded docusign in my implementation. Everything works fine but once user is done signing the envelope and clicks on “Finish”, it takes about 7-8 seconds for docusign to respond back with the sessionend event signing_completeSo user might get confused or think something went wrong as the screen looks like this.and after 7-8 seconds, we get the eventIs it possible for docusign to send the response within 2-3 seconds?Or else is there any event where we can show processing loader so that user is not confused?Thanks,Sweenal​​​​​​​

Hey everyone,I’m working on Next.js application and I want to create contract there and also i want edit them on my website also want to know about there status so can you guys please tell me step by step guide how can I do this?