eSignature API

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);

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. 

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?

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?

Dear all, I need to configure for US colleagues the next API connection. I look for the following but for all available US Pen in DocuSign : {"signatureProviderId": "412","signatureProviderName": "transsped","signatureProviderDisplayName": "Trans Sped SAFE/eIDAS digital certificate","priority": "2","isRequired": "false"}Normally I use the API explorer tool but it doesn't catch the US pensDigiCert US Signer Held Notary U.S. USAID PIV PIV Smart CardsRegardsolivier 

Hi All, I am having a basic query related to Docusign API. This query is more of API related rather than Docusign related, however still posting here as it concerns Docusign. I am following this video for querying docusign API. Here at timestamp 5:44 the API body is passed as ‘x-www-form-urlencoded’(snapshot attached). However, I am making this API call using my automation tool(Uipath) which lacks the ‘x-www-form-urlencoded’ interface similar to postman. It is possible to pass the body as JSON instead of ‘x-www-form-urlencoded’? I tried passing JSON body as below but it didn’t work. {“grant_type”: “authorization_code”, “code”: “<code>”} Thanks! 

Hello everyone!I’m developing an integrator to send documents from our ERP to DocuSign for digital signatures. The email sending is working, but I’m encountering an issue with WhatsApp sendingMy project uses Node.js with TypeScript, so I’ve typed the recipient using the interface exported from the @types/docusign-esign library. However, this interface doesn’t include the “phoneNumber” attribute, which is needed to send the phone number object as shown in the example project (see the images below).My Project:Node.js eSignature REST API Example: Could this be a missing attribute in the library’s interface?

I have an app key setup and live in production. When a user clicks a button on my page I create an envelope and send a PDF with a request to Docusign for the user to sign. This has been working for several years. Is it possible to use the same app key to send a different PDF for signing, or do I have to create a separate app key?The return URL will be different for the other PDF, but it looks like I can add multiple return URLs to the app key configuration.

I am following the tutorial from this page: How to get an access token with Implicit Grant | DocusignI have an href to the following URL: https://account-d.docusign.com/oauth/auth?response_type=code&scope=impersonation%20signature%20organization_read%20user_read%20account_read%20dtr.profile.read&client_id=#redacted#&redirect_uri=https://localhost:7054/dsauthWhen I follow this href I am directed to log in and grant permission.  I am successfully redirected back to

I have made a number of API submissions during PoC process, these have been delivered either to the Sent or Drafts folders. I have gathered the envelopeId’s and can access the envelopes directly, however they do not appear in the Agreements view. (The latest viewed one does appear if I navigate to Sent/Draft via the info on the envelope detail view, but it only shows the one envelope). How can I see a list of all my Drafts?  PS> Is it possible to select and send multiple drafts at once?

Is is compulsory to create a developer account and then migrate to production after submitting app for review? Can I create app in production environment directly to use DocuSign API?

Hello,I am trying to implement a counter-signature functionality in DocuSign sandbox env and encountering an issue where the envelope does not transition to the "Completed" status as expected. Below is the workflow I am attempting to implement and the problem I am facing: Template Setup: My template has two roles: Customer (Role 1): Configured as need to sign, with required text fields and a signature field. This role has a routingOrder of 1. Company (Role 2): Configured as need to sign, with required text fields only. This role has a routingOrder of 2. Envelope Creation: At the time of envelope creation, I programmatically fill all required text fields for the company role using the API ( also try to fill text fields after the customer signature compl

Hi All, I am working on creating an envelope using API explorer in developers.docusign.com. I am able to send the document if I am not attaching any tabs to the document. However I am getting the below error if I am attaching tabs to the document. Kindly assist me with this issue. I have updated the url and body of my request. {  "message": "Bad Request",  "response": {    "err

Hello, I am working on developing a web application that requires integration with Docusign to request signature of some documents, just to put you in context my application sends an SMS to a user and depending on the user's response the document signature request must be sent, the request must be sent by SMS and also the entire envelope creation process must be done in my API without requiring user intervention, so I want to know if this project idea is reasonable and what authentication method I should use for this project. I would greatly appreciate if you could help me with this question. I only have to add that my API is being developed using NodeJs. Thanks in advance.

Hello,I have a problem When I build my envelope with additionalNotification,I want a SMS notification but the Docusign API say that my vountry_code is not present. But I made that (in PHP) :                         $additionnalNotification = new \DocuSign\eSign\Model\RecipientAdditionalNotification([                            "secondary_delivery_method" => "SMS",                            "phone_number" => [                                "country_code" =>”33”,                                "number" => “625589878”                            ]                            ]); The country code is the country code of france. I get: Error while requesting server, received a non successful HTTP code [400] with response Body: O:8:"stdClass":2:{s:9:"errorCode";s:34:"INVALID_PHONE_NUMBER_FOR_RECIPIENT";s:7:"message";s:73:"The Phone number is invalid. Country code is missing. Recipi

Hi,I have a DocuSign template that includes field tags in the document. I need to attach another document to this template document. The reason for this is that the template page serves as a common page that must appear at the end of all other documents. Is it possible to attach an additional document to the existing template document using DocuSign API?Thanks!

We use Docusign eSignature APIOne of our customers needs to set up a QES, and some of the signatories have last names with diacritical marks (e.g., a slashed "o" or umlauts).Could this potentially cause any issues with identity verification?

Hello,I’m currently sending some documents to be signed in french language.I have templates host in my api resources in HTML format. I use openhtmltoolpdf to format my html documents as pdf. My freemarker templates contain some form fields to enable recipients to fill all the info with any PDF reader.I use some DocusignDate and the html attribute data-pdf-form-field="true" then request docusign to transform the pdf fields with transformPdfFields.The recipients receive the form well formatted except the date fields.When i change the regional settings of my admin account, the format of date fields is well updated but the validation is not working anymore.  May anyone help me please ? Regards,Antoine

Dear Support,We are getting this error on a production account. This is happening after the consent was provided. The token is successfully retrieved using method RequestJWTUserToken. But GetUserInfo/CreateEnvelope return error.Error while requesting server, received a non successful HTTP code with response Body: {"error":"internal_server_error","reference_id":"c02eb179-6bba-474c-8a25-94d3772219cb"}Thanks,Tahir

Hello Everyone!We deployed Docusign embedded signing into our own system. We do know that our users can change their signature style, using templates, drawing, and images during the Signing process. We would like to develop a maintenance page in our system so that our users are able to change their signature before the Signing process. Afterward their signature style will be used in the Signing process on the other day Is it possible to do that? How can we do it? Looking forward to your guidance. Thank you

Our company needs to integrate payments with Stripe into an agreement signing process. The business wishes to restrict payments to only ACH transfers. Is there a way to set this?The AllowedPaymentMethods property of the PaymentDetails, seems to be where this may be set, and it accepts a List<string> of allowed payment methods. I could not locate any documentation for the correct value to allow ACH transfers. Any idea of what that value may be, or if there is another way to restrict the payment type allowed?