Skip to main content
arrow-left Back to Docusign.com

eSignature API

Find answers to your Docusign eSignature API questions.

  • 637 Topics
  • 1,308 Replies
637 Topics
P
Newcomer
Pallavi H PNewcomer
asked in eSignature API
Legacy authentication to App password authentication

For SOAP API ,how to update from Legacy authentication to App password authentication

841
Leandro.Reis
Docusign Employee
A
Newcomer
akram.alamNewcomer
asked in eSignature API
DocuSign Integration Issue

HI Team, Can someone help me to Integrate DocuSign On my Application Below are the Details:-<add key="ClientId" value="" /><add key="Userid" value="" /><add key="AccountId" value="" /><add key="AuthServer" value="account-d.docusign.com" /><add key="RSAPrivateKey" value="”/>For Userid key - I used user ID from user profile For ClientId key :- I used Integration keyFor RSAPrivateKey :- I user RSA Keypair private key For AccountId key :- I used organisation Account IdBut I am getting and not able to integrate can someone help me on thisThanksAkram

461
karan.kaushik
Docusign Employee
S
Newcomer
Steve E.Newcomer
asked in eSignature API
API, Splunk and the elusive Event ID

How do I correlate from my WebApp DocuSign REST calls to the Splunk docusign index?  Docusign Event ID looks like the best correlation but I can not figure out how to get it from the response on my WebApp activity. --Steve Sample searchindex=docusign sourcetype="docusign:monitor"| eval json_payload=_raw| spath output=userId input=json_payload path=userId| spath output=user_action input=json_payload path=action| spath output=user_device input=json_payload path=userAgentClientInfo{}.device{}.family| spath output=user_device_model input=json_payload path=userAgentClientInfo{}.device{}.brand| spath output=user_agent input=json_payload path=userAgent| spath output=user_agent_family input=json_payload path=userAgentClientInfo{}.browser{}.family| spath output=signers_recipient_guid input=json_payload path=data{}.RecipientInfo{}.RecipientId| spath output=signers_recipient_id input=json_payload path=data{}.RecipientInfo{}.UserId| spath output=documentIdGuid input=json_payload path=data{}.envelo

211
E
Docusign Employee
A
Newcomer
AniNewcomer
asked in eSignature API
Unable to integrate esig with Coupa

Unable to Connect with Coupa.I am using the same Email to connect with Coupa, but it keeps throwing “password/email invalid”

672
A
Newcomer
R
Newcomer
RicoNewcomer
asked in eSignature API
Status not refreshed after envelope correction and resend via API

Hi, Summary: status not refreshed after correcting an envelope, setting another invalid email via API Explanation:Tested in the demo acountI have created an envelope containing 2 signers, putting an invalid email in the first signer. Through the API, I can get the ‘autoresponded:smtp; 550’ status, so I know I must correct the first email address.Using the API,when I correct the email address giving another invalid email address, the status remains ‘sent’, no matter what I attempt to do (UpdateRecipients with resendOption to true, Update with resend option or even resend through the DocuSign website)… Am-I missing something ? When I correct the first signer address through the DocuSign website, the ‘failed’ status of the second invalid email address is shown : In the envelope’s history, there a slight difference between :Correcting through the API displays a “Resent” status in the action columnCorrecting through the DocuSign website display an “Invitation resent’ status. (translated fro

630
R
Newcomer
R
Newcomer
Rogerio GomesNewcomer
asked in eSignature API
Current Routing Order Problems

Hi, I used the SDK for Java (Version 6.0.0) and i tried to use the function for Routing Order, but doesn´t works.  My Code IntStream.range(0, userSigners.size()).forEach(i -> {Signer signer = new Signer();signer.setEmail(userSigners.get(i).getEmail());signer.setName(userSigners.get(i).getName());signer.recipientId(String.valueOf(i+1));signer.setRoutingOrder(String.valueOf(i));signer.setTabs(tabs); signers.add(signer);}); Recipients recipients = new Recipients();recipients.setSigners(signers);recipients.setCurrentRoutingOrder("true");envelope.setRecipients(recipients); This is correct?

150
R
Newcomer
I
Newcomer
IiroNewcomer
asked in eSignature API
Issues in production

I'm unable to connect in production mode.

131
E
Docusign Employee
V
Newcomer
vhaiekNewcomer
asked in eSignature API
“At least one recipient is missing valid contact information.”

 Hello everyone, how are you?I'm having this problem when sending a file to my client.I believe it is because the Co-Buyer or Co-Seller fields are not filled in, how can I do to remove the requirement to fill them in?   

420
V
Newcomer
V
Newcomer
Vignesh BalaNewcomer
asked in eSignature API
How to make hyperlink clickable in PDF using CreateEnvelope API?

Hi Team,Could anyone help me with the following issue:I have to make the hyperlink clickable using createEnvelope API. The steps I have followed:Created one Anchor string on the PDF file with prefix #HREF. Configured that Anchor string as well with the same name. Then tried creating envelope with the above-mentioned file. When I have opened that envelope, I could see one link clickable but whenever I click on that link it is getting redirected to a blank page. Please refer to attached image below. Clickable HyperlinkRedirected Page  Then I have tried passing values to the Custom Fields while creating the envelope but still the issue remains same.Configured Custom FieldAny help to achieve this would be much appreciated.Thanks in advance.Regards,Vignesh Balasubramanian

991
E
Docusign Employee
P
Newcomer
PrateekNewcomer
asked in eSignature API
Error: Unauthorized while creating envelope

Hi Team,I am getting below error while invoking docusign  makeEnvelope  test@gmail.comcreatingEnvelopeAn uncaught exception occured!Error: Unauthorized    at Request.callback (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:696:15)    at /home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:906:18    at IncomingMessage.<anonymous> (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/parsers/json.js:19:7)    at IncomingMessage.emit (node:events:539:35)    at endReadableNT (node:internal/streams/readable:1345:12) This works fine for me in local, however the same is failing through an application deployed in cloud.I have added redirect uri in apps and keys section of the developer account as below,http://localhost:3000/https://sample-domail-xxxx/Please note the url on cloud is https Additionally i have enabled all the https methods available.Please suggest the resolution.

331
Leandro.Reis
Docusign Employee
K
New Voice
kensevNew Voice
asked in eSignature API
Python API: Phone Number Authentication

I’m trying to use the phone number auth for my python API. I’m already using the API to get the workflow ID and I’m getting this value:'c368e411-1592-4001-a3df-dca94ac539ae' However, I’m still getting this error:HTTP response body: b'{"errorCode":"IDENTITY_WORKFLOW_INVALID_ID","message":"The identity workflow ID specified is not valid."}' Any idea on this?Thanks!

1164
A
Active Voice
M
Newcomer
Mark SpritzlerNewcomer
asked in eSignature API
account-d Website has a bug and is showing MS Word Content Control objects

In the past few weeks account-d Docusign is broken, it does NOT happen in account DocuSign website. We use Java API and have not changed a single line of code in over a year, but in the past few weeks the MS Word .docx that we send to get signed is showing to everyone the Content Controls that are in the document. This has never happened before, all content controls are hidden in production Docusign and was always hidden on account-d. But now in the past few weeks they are showing, something has broken on account-d.  

306
M
Newcomer
O
Newcomer
omsigdocNewcomer
asked in eSignature API
Unable to fill customfields sending envelope

Hello,  We are unable to fill the customfields of a template when we try to send an envelope on Docusign API REST.The endpoint we are using is: {{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesThe body is the following: {  "templateId": "xxxxxxxx-4240-4951-bdb1-f43315509f6e",  "templateRoles": [    {      "roleName": "Signer",      "name": "Test Name",      "email": "test@test.com",      "tabs": {        "textTabs": [          {            "tabLabel": "Custom1",            "name": "Custom1",            "value": "Esto es el custom 1",            "documentId": "1",            "pageNumber": "1"          }        ]      }    }  ],  "status": "sent"}  We previously created the field with the label Custom1. But when we receive the template result on the mail tray the fields values are not appearing. The collaboration checkbox is also marked. Any solution?  Thanks in advance

210
O
Newcomer
L
Newcomer
LysintNewcomer
asked in eSignature API
API Signature : OAuth 2.0 on legacy Connect. (SOAP)

Hello !  We have a integration project for Esignature. I see the OAuth configuration work on Connect RestAPI but for SOAP Connector, the authentification isn’t working.I didn’t find in a documentation if the OAuth works with legacy Connect (custom connect SOAP) Thanks,

421
J
Docusign Employee
J
Newcomer
jrcellinNewcomer
asked in eSignature API
Envelope Signature Authentication via API

Hello, I have an integration with my client’s custom software and DocuSign’s rest api. We are creating envelopes from a template. This all works well except we do not want the signer to have to answer the authentication questions before signing. We tried turning this off on my clients DocuSign account but the changes do not work when the envelope is created via the api. Support says we can turn off authentication via the api call but I do not see it anywhere. Can someone point me in the right direction?

271
E
Docusign Employee
M
Newcomer
mbuselliNewcomer
asked in eSignature API
Getting the groups a template is shared with via eSignature

How does one get full access control information for templates shared to the user currently logged in or impersonated using the eSignature API? An example use case is the following: an admin user creates a new group; GroupA, and adds User1 to that group, then shares a template, TemplateXYZ, to GroupA . When I am logged into the Docusign UI as User1,  I can see that I have shared access to TemplateXYZ. But there doesn't seem to be an eSignature API that can tell me this. When User1 calls the API to get info for TemplateXYZ (Templates:get) it doesn't return anything about its shared access. And yet there are API to update or delete groups shares for a specific template (Templates:updateGroupShare and Templates:deleteGroupShare).  The only other API I’ve found that seems like it should return the info I’m looking for is Accounts:listSharedAccess. According to its documentation I should be able to pass item_type=templates but that returns a bad-request error with additional message that I

241
E
Docusign Employee
K
New Voice
kensevNew Voice
asked in eSignature API
Python API Automation Composite Template: Other server templates is being applied to other documents

Hi,I’m trying to send an envelope with multiple documents and each document needs to be applied a specific template.I’m looping through the documents and adding the specific serverTemplate based on the type of document.Here’s a snippet:The serverTemplate is determined by: However, it seems that the other template is being applied also to the document that it’s not meant for.Here’s the error:HTTP response body: b'{"errorCode":"TAB_PAGENUMBER_IS_NOT_IN_DOCUMENT","message":"The pagenumber specified in the tab element is not in the document that the tab refers to. Tab on Page 9 of Document 1 for Recipient 1"}' Any idea?Thanks!

832
K
New Voice
C
New Voice
cweeksNew Voice
asked in eSignature API
docusign 500 error when trying to Create Envelope

I am using C# docusign JWT SDK to authenticate. I am able to authenticate and get an access token back where I am able to successfully call GetUserInfo to get account information, but when I create an envelope from the downloaded example, and send that to the CreateEnvelope(account,envelope), it is generating a 500 error message with Stack Trace error…“at DocuSign.eSign.Api.EnvelopesApi.CreateEnvelopeWithHttpInfo(String accountId, EnvelopeDefinition envelopeDefinition, CreateEnvelopeOptions options)”My scopes are “signature” and “impersonation” What am i not doing correctly? Thanks

29911
Hengfeng Ge
Frequent Contributor
M
Newcomer
Marybi.MalminNewcomer
asked in eSignature API
How to create a new user in Esignature via API?

Hello, . 1. Go to https://account.docusign.com/,  and sign in with your TSC email address.2. If you are prompted to enter your TSC password after entering your TSC email address, please select the “USE COMPANY LOGIN” option instead of typing in your password. Continue to log in as usual.

251
E
Docusign Employee
O
Newcomer
Olivia_DeveloperNewcomer
asked in eSignature API
Create envelope with Text Tabs populated via API, in Node.js

Hi everyone,I’m able to send out envelopes for signature in Node.js via the docusign-esign NPM package, but my text fields are not populating for some reason.  I am referencing the documentation linked here.  I’ve tried both on our developer account as well as our production account.Here is my code for creating the envelope.  I am getting the label and ID for the text fields through the Docusign API, and I have double-checked the label is correct through the Docusign webapp itself.function makeEnvelope(args) { try { let envelope = new docusign.EnvelopeDefinition(); envelope.templateId = args.templateId; let text = docusign.Text.constructFromObject({ tabLabel: TAB_1_LABEL, value: 'test text field!', }); let textExtra = docusign.Text.constructFromObject({ font: 'helvetica', font_size: 'size14', tabLabel: TAB_2_LABEL, height: '23', width: '84', required: 'false',

1554
O
Newcomer
P
Newcomer
Pallavi H PNewcomer
asked in eSignature API
How to mitigate alert - This app has used legacy authentication in the last 10 days.

Could you please advise us on the alert and how to to mitigate it  

362
P
Newcomer
V
New Voice
VasNew Voice
asked in eSignature API
Managing Multi-Region Integration for a DocuSign Application - Account and Deployment Considerations

Hello I have one integration App deployed on PRD.Endpoint /oauth/userInfo returns me account with host: https://eu.docusign.net.What if I want to cooperate with accounts from different regions?Should I have accounts on each region and apps for them?Should I create new apps for regions on my one existing account?Is it possible my current app will be able to connect with accounts from all regions? BR

801
E
Docusign Employee
T
Newcomer
thuiNewcomer
asked in eSignature API
Programmatic way to authenticate and send out PDFs for signing

Hello. I’m trying to create a back-end system that can automatically retrieve an access token without any user interaction so that it can send out documents for signing. The samples I’ve encountered PDFs for signing have required me to authenticate using my developer account. Is there a way to get an access token programmatically without any user interaction?I appreciate any help you can provide.

691
R
Docusign Employee
I
Newcomer
ionmoraru_toptalNewcomer
asked in eSignature API
get signer attachments via api

Hey,I’m sending via API to a signer an envelope created from template, which has fields to fulfill including attachments (multiple)I need to separate the attachments that are added by the signer, sometimes it’s just one page, sometimes multi-page documents.I already https://www.docusign.com/blog/developers/getting-signer-attachments-using-the-esignature-rest-api and I don’t get desired outcome.What I have noticed is that once the signer add any attachment it’s added to the document as new page, and there is not ID I could use to distinguish which page is from initial document, or is an attachmentHow can I separate the initial document and each attachment filed?

875
Hengfeng Ge
Frequent Contributor
C
Newcomer
Colin KennedyNewcomer
asked in eSignature API
Docusign JS 'translation' error

Hi all,I’m using the following JavaScript in my application:async function startSigningCeremony(signingUrl) { // Set the clientId to your application's Integration Key let clientId = "28ef2184-4fc9-4ae0-b77b-a055fb0727ac"; // Integration key // Check if signingUrl and clientId are provided if (!signingUrl || !clientId) { throw new Error("signingUrl and clientId must be set"); } const signingConfiguration = { url: signingUrl, displayFormat: 'focused', locale: 'en', style: { branding: { primaryButton: { /** Background color of primary button */ backgroundColor: "magenta", /** Text color of primary button */ color: "white", } }, signingNavigationButton: { finishText: "Agreed!", // default is Submit // 'bottom-left'|'bottom-center'|'bottom-right', default: bottom-right

881
C
Newcomer

Badge winners

  • 1st Question Posted
    TB25has earned the badge 1st Question Posted
  • 1st Question Posted
    Gabi.Schiesslehas earned the badge 1st Question Posted
  • 1st Question Posted
    REFAhas earned the badge 1st Question Posted
  • 1st Question Posted
    REHhas earned the badge 1st Question Posted
  • 1st Question Posted
    JDCovinohas earned the badge 1st Question Posted
Show All Badges
Code of Conduct

Docusign Community

Code of Conduct