Developer

I created an app to prove the Docusign JS embedded signing with Focused View.  I am using C# at the server and JS/jQuery at the client.  I followed all of the steps in the article “How to request a signature using focused view” (https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view).Everything on the server side is fine, but when the JS code runs to load the document for signing, I get the following permission errors:Refused to frame 'https://apps-d.docusign.com/' because it violates the following Content Security Policy directive: "default-src 'self' https://js-d.docusign.com/". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to 'http://loc

I installed all needed libraries, including the one for ds types. It’s been extremely difficult to use. I haven’t been able to find working examples. I am at a loss. If anyone knows how to use NextResponse app router, typescript, and docusign to get a route.ts file that could send out an e-signature, I would be forever grateful. This is what I have till now ``` import { NextRequest, NextResponse } from 'next/server';import docusign from 'docusign-esign';import fs from 'fs';import path from 'path'; export async function POST(req: NextRequest) {  try {    const { signerEmail, signerName } = await req.json();     // Initialize the DocuSign API client    const dsApiClient = new docusign.ApiClient();    dsApiClient.setBasePath(process.env.NEXT_PUBLIC_DOCUSIGN_BASE_URL || '');     // Load the private key    const privateKey = fs.readFileSync(      path.join(pro

i have a platform that has 20+ fields i want to be able to autopopulate on a predefined template and create an envelope using the api. i have tried every possible way to try and get the fields to map and all of the debug logs look great, but still no fields are autopopulating. my data label values match the fields for creating the mapping and the format of the api calls looks perfect and is generating no errors, but still no fields being mapped.  are there limitations where field mapping will not work in a sandbox account.  any other ideas about what might be causing this issue.  any help appreciated.  debug log here. envelope looks good but nothing on fields mapped. DEBUG: Field Mappings Result{ "propertytitle": "stephanie and lili frieswyk2", "propertyaddress": "26735 rockwall parkway", "propertycity": "new braunfels", "propertystate": "TX", "propertyzipcode": "78132", "propertyprice": 789000, "propertyowneremail": "oneweekendsold@gmail.com", "prop

An Ruby on Rails application that I support is failing to send an envelope after the login/consent-grant step in the flow diagram.  I receive a response to my callback URL with a ‘code’ parameter set:

i have created the developer account in the docusign for e-signature api but it automatically deleted after 2 days every time, and try to login so getting the error no accout found and also integration is deleted, so how to fix it. 

I'm working on integrating DocuSign connect with Laserfiche I need to Provide DocuSign field names however, these fields, don't exist on my templates for the following data points: Document Name:Document Date:Document Worker:How would I provide field names to collect this data?Do these fields need to be added to each template? If so, is there an automated way to populate these fields and have them hidden? 

I have a docs file to sign about 246 pages, normally it works but starting from yesterday it only loads me the first 30 pages, then it is showing loading from page 30 onwards, so I can't click the Sign button. There is no change after 5 minutes so I think it is a bug and not a network issue. I also tried in incognito mode, VPN off/on but same result. There is no change from our code, we are using Auto-place with anchorString to auto place the sign tags.You can watch the attached video to see the detailed description of the bug

We have integrated DocuSign for a multi-signer workflow with 3 signers using our Node.js application. In most, cases, the signing process work as follows:Signer 1 → Signer 2 → Signer 3 (all signers complete the document one after the other)This is working fine for scenarios where all 3 signers are required.However, we have a specific use case where:1. After Signer 1 completes the signing, we need to  update the second signer’s information dynamically and Skip Signer2(in certain conditions).   Continue directly to Signer 3 to collect their signature2. In other cases, we want to proceed as usual, where all 3 signers complete the document in sequence.Questions:1. Is there a way to conditionally skip a signer(Signer 2) after the first signer has completed the signing process?2. Can we update the document or signer information dynamically(ex: update signer name, date of sign)3. What is the recommended

I’ve been using Docusign click api for a few months, specifically the elastic templates. Recently one particular template has started to return a 404 - File or directory not foun error. But this document aleready has responses. AccountId and clickwrapId seems to be fine too.Has anyone seen such error before?

I can’t tell from the documentation whether extension apps have an sort of UI component in the platform or if it is purely a step in workflows

We have built dozens of PowerForms over the years and want to do a comprehensive inventory of the fields within the PowerForms. We are wanting to retrieve the field names, field types and if the fields are required for all PowerForms. Is this possible via API?

We are using the embedded signing, so the users do not have to leave our app which means we are using the APIs to facilitate this. We are trying to automate the process of onboarding/auto-provisioning users into DocuSign so they don’t have to go to the DocuSign site first.  We have Auto-Provisioning turned on and it works when a user logs into the portal. My question is, should the auto-provisioning work through the API’s where if we search for a user's email, it will automatically add them if they exist within our domain. Or do we need to have a process that checks if a user exists in DocuSign and add the user if they do not.

Import in index.html<script src='https://js-d.docusign.com/bundle.js'></script> In signing page component:import { Component, OnInit, input, AfterViewInit } from '@angular/core';import { Input } from '@angular/core';import { ActivatedRoute } from '@angular/router';declare const DocuSign: any;@Component({ selector: 'app-focused-view-signing', imports: [], templateUrl: './focused-view-signing.component.html', styleUrls: ['./focused-view-signing.component.css']})export class FocusedViewSigningComponent implements AfterViewInit { integrationKey: string = 'xxxx'; // Replace with your integration key constructor(private route: ActivatedRoute,) { } ngAfterViewInit() { const url = this.route.snapshot.paramMap.get('url'); console.log('Input URL:', url);

Hello,I am hosting multiple apps that require signing, so I created a dedicated app that uses the DocuSign JS library to provide a focused view signing interface. This app is designed to be accessed via an iframe by my other apps. But it keeps giving this error: Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://localhost:4209"The signing app is hosted at https://localhost:4209, while the other apps are hosted on ports 4201 and 4206. The signing app works perfectly when accessed directly from the browser at https://localhost:4209, but it fails to load when embedded in an iframe within the apps hosted on ports 4201 and 4206.I have added all the required domains in the request. Here’s the C# code of the request for generating the urlvar recipientViewRequest = new RecipientViewRe

We need a list of envelopes where the recipient has used Print and Sign feature.  We place a documentType name value pair in documentFields array, but there is no programmatic way to know which envelopes have uploaded documents via the Connect callback interface JSON.There are a lot of other use cases for search. 

Hi! I just published a new YouTube video on how to streamline Docusign Web Forms by pre-filling them and tracking their status.You’ll learn:How to pre-fill Web Forms using URLs and APIs. Limitations of URL prefill methods and how to overcome them. Using automation tools for secure and trackable workflows. How to integrate databases for seamless Web Form pre-fill and status tracking.Watch the video to simplify your Docusign workflows! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign Partner

Hi, I’m wondering that can I modify the “Message from {xxx}” using API or website?I knew that there is email-subject and email-content can be modified in template setting, but I want to show business partners’ name on the “agree-to-use-eSignature” page

Hello,I’m encountering an issue when transitioning the DocuSign integration to my client’s production account. Instead of displaying the expected OAuth consent pop-up, I receive an error stating that the page cannot be found. Below are the details of the error:Error: "This page account.docusign.com cannot be found..."Associated URL: https://account.docusign.com/oauth/auth?client_id=9f87e104-a483-405b-ab66-d0bcad57bf62&scope=signature%20admin_consent%20manage_app_keys%20connect_hmac_api%20user_read%20account_read%20user_write%20cors_manage%20manage_system_signing_groups%20account_write%20admin_communication_read%20admin_communication_write%20organization_write%20organization_read%20account_product_read%20group_management_read%20group_management_write%20me_profile%20search_read%20search_write%20organization_data_feed_config_read%20organization_data_feed_config_write%20organization_monitor_config_rea

I’m testing the API call to add an envelope to be purged.  I have a completed envelope ID from one of our Dev environment.  I’ve been able to successfully change the purgeState from “documents_and_metadata_and_redact_queued” to “documents_dequeued” using the API Explorer from developers.docusign.com  When I try the same API call from Postman, I’m getting the following error:     "errorCode": "DOCUMENT_PURGE_FAILED",    "message": "Error adding documents to the purge queue. Only the sender may remove the envelope documents"I can make other successful calls using Postman.  I’m the same user; that sent the envelope.Any idea what the issue is in Postman?

Hello DocuSign Support Team,We are using the DocuSign Webforms API and need assistance with the following steps after a user completes and signs the webform:Once the form is signed, we want the signed PDF document to be automatically sent back to our system. The signed PDF should then be attached to a specific case in our system for record-keeping and further processing.Could you please provide guidance on how to configure this process using the Webforms API, specifically on how to retrieve the signed PDF and attach it to a case?

please update the link of DocuSign data residency:https://www.docusign.com/trust/privacy/data-mgmt-privacy FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultan

Hi, all! I’m recently encountering an issue where the access code prompt isn’t appearing for signers that I add during the “CreateSenderView” step of my workflow. Workflow: Person A creates an envelope through an external DocuSign integration and adds Signer A as a recipient of said envelope. Person A proceeds to the sender’s view on the DocuSign site. (This is done using envelopesAPI()->createSenderView()) Person A adds a new signer, Signer B. Signer B is assigned an access code. Person A returns to the external DocuSign integration and creates a recipient view for Signer A to sign. (This is done using envelopesAPI()->createRecipientView()). Signer A is prompted to enter their access code, enters, and completes signing.  Person A creates another recipient view for Signer B once Signer A has finished.  Signer B is not prompted for an access code and doesn’t see the fields added for them to sign.

Hi,I have a usecase where contracts are created using a salesforce workflow through a user and I am trying to purge those contracts via APIs. While purging documents I am getting an error that only the sender can add documents to purge queue.I am purging documents via APIs and docusign does not allow to add API user to act on behalf to docusign Users. Is there a workaround for this which would enable be to purge documents created by other users?

Hi Dev Folks,i have posted my problem here, can any one help me to solve that issueThanks.

Hi,I am implementing docusign envelope/ esignature api using docusign SDK,I have implemented CreateEnvelopeAsync() successfully, but if i had put wrong email address for recipient signer then recipient signer email bounced or autoresponded. in that situation i am updating recipient signer with sign here tabs, and recipient updated successfully. but when signer opens email and going to review envelope and to do sign then the sign here tab not displayed with AnchorString at specific AnchorYOffset and AnchorXOffset on the document.So please provide any solution.Thanks. below the code of c# .net core for update recipient and tab public async Task<RecipientsUpdateSummary> UpdateRecipientsWithTabs(string envelopeId, DocuSign.eSign.Model.Recipients recipients, UpdateRecipientsOptions options = null) {     try     {         RecipientsUpdateSummary updateSummary = null;         OAuthToken authT