Developer

import axios from "axios";import docusign from "docusign-esign";import fs from "fs";import path from "path"; const getAccessToken = async () => {  const apiClient = new docusign.ApiClient();  apiClient.setOAuthBasePath("account-d.docusign.com");   const privateKey = fs.readFileSync(    path.join(process.cwd(), process.env.NEXT_PUBLIC_SIGNUP_CLIENT_SECRET || "")  );  const response = await apiClient.requestJWTUserToken(    process.env.NEXT_PUBLIC_SIGNUP_CLIENT_ID,    process.env.NEXT_PUBLIC_SIGNUP_USER_ID,    ["signature"],    privateKey,    3600  );   return response.body.access_token;};where i can find these issues? tried to use this, but have error AUTHORIZATION_INVALID_TOKEN 

Hi! I just published a new YouTube video about simplifying your sales process with Docusign and Pipedrive integration.You’ll discover:The limitations of the standard Docusign for Pipedrive integration. How to enhance workflows using third-party integrations like Docusign on Pipedrive. A fully automated custom integration using Make.com to generate documents, track statuses, and sync data seamlessly—no manual steps needed.Learn how to save time and streamline your sales process with automation. You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

we create sendview url and got the ip address is 20.236.201.80.So we nslookup it:nslookup apps.docusign.comServer: 223.5.5.5Address: 223.5.5.5#53 Non-authoritative answer:apps.docusign.com canonical name = apps-geo.docusign.com.akadns.net.apps-geo.docusign.com.akadns.net canonical name = apps-na.docusign.com.akadns.net.Name: apps-na.docusign.com.akadns.netAddress: 20.236.201.80 but we not find this ip in the Docusign endpoint IP addresses of https://www.docusign.com/trust/security/esignature. for these near range is only include: IP range: 20.236.201.102 - 20.236.201.103 CIDR notation: 20.236.201.102/31  we not find this update in the recently Release Notes.please update the new range which need update. thanks. FreeLink🌍 DocuSign Partner | Partner Profile🏆 2024 APAC Reseller Growth Partner of the Year🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant.📊 DocuSign Community Leaderboard Top 5 contributor.🚀 Ex

I have use case where I need to uniquely identify a recipient. With REST API, it works fine. However, with SOAP, response does not return RecipientId as documented.https://demo.docusign.net/api/3.0/dsapi.asmx?op=RequestStatus<RequestStatusResponse xmlns="http://www.docusign.net/API/3.0"> <RequestStatusResult> <RecipientStatuses> <RecipientStatus> <Type>Signer or Agent or Editor or Intermediary or CarbonCopy or CertifiedDelivery or InPersonSigner or SigningHost</Type> <Email>string</Email> <UserName>string</UserName> <RoutingOrder>unsignedShort</RoutingOrder> <Sent>dateTime</Sent> <Delivered>dateTime</Delivered> <Signed>dateTime</Signed> <Declined>dateTime</Declined> <DeclineReason>string</DeclineReason> <AutoRespondedReason&

We are currently leveraging DocuSign keys within Oracle Integration Cloud (OIC) for a KYC process. In our current setup, the email notifications accompanying envelopes sent to customers display a single "From" address corresponding to the account configured for this process.The challenge arises when we involve multiple departments in our workflows. We have developed separate processes for various stakeholders, including Sales, HR, and others. Each department would like their envelopes to display a unique "From" address specific to their role or function.Could you please confirm if it is possible to configure multiple "From" addresses for envelopes based on the process or department? If so, we would appreciate guidance on the best approach to implement this functionality.

We are rolling out Dayforce and paid for the DocuSign IAM Professional package. We were asked to create a Developer account to demo the application during testing. We have set up the external integration in Dayforce to point to the admin user account and id and base URL. Everything was working. Now Dayforce is Live and we were instructed to go into Dayforce external integrations and Click for oAth Setup and Export Tokens. Clicked and it now matches the tokens in the External Integration area in DF and our DocuSign account information in Apps and Keys. However it is not working. I am not sure if we need to do something else?

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://localhost:49618/05e7fec…/browserLinkSignalR/…ationData.browserId&browserId=b7e3-320d&clientProtocol=1.3&_=1728595245739' because it violates the following Content Security Policy directive: "default-src 'self 'https://js-d.docusign.com/". Note that

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(process.cwd(), process.env.NEXT_PUBLIC_DOCUSIGN_PRIVATE_KEY || '')    );     // Request JWT user token    const results = await dsApiCli

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", "propertycounty":

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:https://elided-host.edu/auth/docusign/callback?code=eyJ0eXAiOiJNVCIsImFsZyI6IlJTMjU2Iiwia2lkIjoiOGFlYzFjZjQtYmE4NS00MDM5LWE1MmItYzVhODAxMjA3N2EyIn0.AQoAAAABAAYABwCAQhCGVSDdSAgAgM6WzVUg3UgCAD4nwjoJTdpMt_Th1QcGWaMVAAIAAAAYAAEAAAAFAAAADQAkAAAAZmQxZjg5YjItNjZkNi00MGRlLWFhYzctNGFhMTgzNzBlOTY5IgAkAAAAZmQxZjg5YjItNjZkNi00MGRlLWFhYzctNGFhMTgzNzBlOTY5MACAQhCGVSDdSBIAAgAAAAsAAABpbnRlcmFjdGl2ZQcAAABtYW5hZ2Vk.EIkNnGHh1iLCYF1i5JXeyfzU26B7Fx5bJao7X1_3WSJ-N56AoFAy8JA3MLbEWjWtesbXWXplU5HkIN9TyGWYqdwplswU6ai2F5pWnHy1ntHXJr-p2OFGSb7UApcMU4l2Bd-hx3TITt4zgz-YpEfJ6aZT1xoFrkhNFsrwyjpS7LbmGXLxbIKiv61rVi-09l1kem0-V8CufYuaQusnOKWIwlSCSpLXttRumLR4MUGLdTJ5AHEO5LXuKejdojD-M-P9iiTP8VRjnVSp50zi31vLeK6ghyT_ZQEeTs7aqoXIT8afi945JEExuLsIBURdQkIoQLqU0N_jftccaQlGm-YgzA&state=3066440d77f347fa1c1096f597dee488c55609163cc571

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 approach for implementing such conditional workflows with DocuSign’s API’s? 

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); DocuSign.loadDocuSign(this.integrationKey) .then((docusign: any) => { const signing = docusign.signing({ url, displayFormat: 'focused', style: { branding: {

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 RecipientViewRequest { ReturnUrl = request.ReturnUrl, ClientUserId = "1234",

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 PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

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_read%20organization_monitor_config_write%20organization_monitor_events_read%20notary_read

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?