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

eSignature API

Find answers to your Docusign eSignature API questions.

  • 447 Topics
  • 978 Replies
447 Topics
O
Newcomer
OBEROLENewcomer
asked in eSignature API
Updating the options in a custom field on a template using REST

Probably a n00b question for you guys, but i am in a little time pickle. I am a seasoned developer with little to none experience with docusign (one day 😉), but i cannot get a good handle on how to go about the following. We have templates being used in my corp Now and then there are changes in our organizations masterdata I need to update the listitems on the templated documents being sent for signing What is the correct way of doing this? Suggestions, blogs, youtubes and other are appreciated -Ole

1814
O
Newcomer
F
Newcomer
fbanikNewcomer
asked in eSignature API
Question about the envelope sent by API

Hello guys! I've integrated Docusign with TOPdesk. I'm able to create a base64 document and send this document via email. However, when I look within the Docusign platform, this document doesn't appear. What could I be doing wrong? But, here, I can’t see anything...

804
F
Newcomer
S
Newcomer
ShopBackNewcomer
asked in eSignature API
How to update Template's Custom Field via REST

Hi, I’ve created a template and added a few custom fields on the template. I’ve applied a template on an empty envelope but I can’t seem to to able to update the custom fields on the envelope. When I pull a list of custom fields on the envelope, all I’m getting is this. { "textCustomFields": [ { "fieldId": "11074686122", "name": "templateUsageRestriction", "show": "false", "required": "false", "value": "allOptions" } ], "listCustomFields": []} Is it possible to update there custom fields before sending it to the end user? Best regards, Matt

1584
JohnSantos
Valued Contributor
S
Newcomer
ShopBackNewcomer
asked in eSignature API
Is it possible to preview a draft envelope before sending it?

Hi, I’m trying to create a preview of a draft envelope so the sender can confirm all the data and fields are correct before sending the envelope. I tried using the createSenderView API to get the URL for the Sender View. However when I try to access the URL its saying Login Unsuccessful redeem console code : RestApi Error . Transaction Id: xxxx From what I’ve read online, the supposed URL is supposed to be this domain “https://demo.docusign.net” but I’m getting this instead “https://apps-d.docusign.com”. Is there some configuration/setting that I’m missing? Regards, Matt

1461
Leandro.Reis
Docusign Employee
K
New Voice
karanvir93New Voice
asked in eSignature API
DocusignApi - Date Tab set date range

How to disable future dates in the datepicker (using Date Tab) using docusign api? How to set the date’s start date based on other date’s end date?

1142
K
New Voice
D
Newcomer
Dileep_123Newcomer
asked in eSignature API
Routing Order for embedded signing (Error - RECIPIENT_NOT_IN_SEQUENCE)

Hello everyone, I’m encountering an error while specifying routing order. when I mentioned routing order as 1 & 2 for two signers it is throwing an error "errorCode\":\"RECIPIENT_NOT_IN_SEQUENCE\",\"message\":\"The token for an out of sequence recipient cannot be generated. And when i changed routing orders as 0 & 1, then it was working. Is there any particular sequence or any mistake in the previous routing order?? And even though it worked, the second signer can open the link before the first signer which is incorrect to the routing order!! this is my payload for that request. { "recipient": { "signers": [ { "email": "test101@gmail.com", "name": "test-101", "clientUserId": "101", "signHere": { "anchorXOffset": "250", "anchorYOffset": "500", "documentId": "1", "pageNumber": "1" }, "routingOrder": "0" },{ "email": "test102@gmail.com", "name": "test-102", "clientUserId": "102", "signHere": { "anchorXOffset": "250", "anchorYOffset": "500", "documentId": "1", "pageNumber": "1" }, "routing

3075
B
Docusign Employee
R
Newcomer
RadiNewcomer
asked in eSignature API
UNSPECIFIED_ERROR

Hi all, I want to create envelope but I receive the following error: errorCode":"UNSPECIFIED_ERROR","message":"Cannot find recipient with ID '1'. The code: EnvelopeDefinition envelopeDefinition = new EnvelopeDefinition();envelopeDefinition.setTemplateId(properties.getTemplateId());TemplateRole signer = new TemplateRole();signer.setEmail(“test@gmail.com”);signer.setName(“Test Test”);signer.clientUserId(“123456789”);signer.setRoleName("signer");Tabs tabs = fillTabs();signer.setTabs(tabs);envelopeDefinition.setTemplateRoles(List.of(signer));envelopeDefinition.setStatus("sent"); EnvelopesApi envelopesApi = new EnvelopesApi(getApiClient());EnvelopeSummary summary = envelopesApi.createEnvelope(accountId, envelopeDefinition); Is there something I do wrong? What can be a reason for this error?

2452
R
Newcomer
R
Newcomer
rentaloNewcomer
asked in eSignature API
How to Create a Template with Variables in Curly Braces and Use It with the API

Hello, I would like to know how to create a template in the DocuSign dashboard using variables with curly braces, without using the drag-and-drop fields. Specifically, I want to define variables in the template like `{RecipientName}`, `{SignDate}`, etc., and then use this template with the API to populate these variables dynamically when sending documents for signature. Could you please provide detailed instructions or documentation on how to achieve this? Thank you!

750
R
Newcomer
V
New Voice
vashuNew Voice
asked in eSignature API
Anchor String not populating value from JSON payload

Hello Everyone, I have a quick query regarding the anchor string feature of DocuSign. I have a web app that allows users to select documents to preview them first. If everything looks good, they can proceed with e-Signing. To achieve this, I have set up two templates in my DocuSign account: Preview with Viewer role: This sends the envelope to the current logged-in user for previewing. If everything looks correct, The user can then proceed with the e-Signing process using the second DocuSign template with the Signer role. Everything is working in the flow as expected, except for the part where the user wants to preview the envelope. The user is receiving the envelope, but the documents within the envelope have empty anchor string values. However, when the user actually sends the envelope for e-signing(Signer Role), we can see that the anchor string values are populated correctly in the documents under the envelope. I'm wondering if this is by design, or if there's something I'm missing

2242
V
New Voice
V
New Voice
vashuNew Voice
asked in eSignature API
Anchor strings not populating dynamic data for role Viewer

Hello everyone, I'm encountering an issue with my HTTP request to DocuSign's create envelope function, and I'm unsure if it's by design or if something is broken. In my development DocuSign account, I have two templates: one for preview with just one 'Viewer' role, and another for e-Signature with a 'Signer' role. Sometimes, users want to preview documents before sending them for eSignature. In such cases, they select the preview option, and I make a call to my first template with the 'Viewer' role, and they receive the envelope in their email to preview it. Everything works fine up to this point. However, when users open the documents, they don't see any data corresponding to the anchor strings I've configured in the JSON payload for DocuSign. On the other hand, when users actually send the envelope using the second template, they can see the anchor strings properly populated at the desired locations. So, I'm a little confused. Is it by design that envelopes with 'Viewer' roles can't

1203
V
New Voice
P
Newcomer
PrabuNewcomer
asked in eSignature API
Docusign Create

How to create an envelope with allowMarkup enabled using docusign Rest API? I am facing issues while creating an envelope. Docusign error: CANNOT_ALLOW_MARKUP: Account does not have permission to set Allow Markup." This error occurs only for few templates. Can someone help me in fixing the issue.

694
P
Newcomer
M
Newcomer
mcanizalesNewcomer
asked in eSignature API
SMS Authentication Phone Number Validation

Is there any kind of data validation on the DocuSign side for the EnvelopeRecipient smsAuthentication.senderProvidedNumbers array? Does this field assume the values in the senderProvidedNumbers array are valid phone numbers? We are working to support both international and domestic phone numbers, and wanted to know if there was any kind of formatting or other validation logic for this field, i.e. adding a “+” for international numbers, to account for.

2261
JohnSantos
Valued Contributor
K
Newcomer
KishorJayannaNewcomer
asked in eSignature API
dateSignedTabs

Hello, I'm making an API call to DocuSign to automatically insert the "date signed" into the document. Below is the API request payload: "dateSignedTabs": [ { "anchorString": "Date", "anchorYOffset": "-1", "fontSize": "Size12", "name": "Date Signed", "recipientId": "1", "tabLabel": "date_signed" }]The issue is that this results in placing the date everywhere it finds the string 'Date' in the document. I want to restrict it to only one place where the actual date is needed. Any suggestions or help? Thanks, Kishor

3561
Michael.Rave
Docusign Employee
K
Newcomer
kiranNewcomer
asked in eSignature API
Envelop creation Failure

Hello Champs, Am trying to create envelope using CreateEnvelope method from EnvelopesApi class and getting error - Error calling CreateEnvelope:. Porject designed in Dotnet core. appreciate your help. thanks.

831
S
Docusign Employee
V
Newcomer
VaughnBNewcomer
asked in eSignature API
Purchase Request Routing - Requester may sometimes be an approver.

I’ve been struggling with the best way to automate one of our form workflows with Docusign and the only way I’ve found to do it is with two separate templates. I’m hoping to get some tips on using conditional routing to simplify my solution. Here is a summary. I have a purchase request form with a possibility of 3 recipients. Requester Approver Purchaser If the form is filled out by a VP, SVP, CEO, etc. the requester completes and signs the form (In this case, the requester is also the approver). Next, the purchaser places the order, adds notes to the form, and marks it completed. If the form is filled out by an employee who is not a VP, the requester completes the form. The form is then sent to a VP for approval and then the purchaser who places the order adds notes and marks the form complete. My current solution using the DocuSign API is. The requester clicks on a link from a page on our Intranet. If the requester is determined to be a VP or above, generate an envelope from the “VP

512
V
Newcomer
L
Newcomer
Lincoln BastosNewcomer
asked in eSignature API
API eSignature users

Prezados, Estamos utilizando a API, ainda no ambiente DEV, para download de envelopes. Vamos solicitar A implantação o ambiente de produção, mas estamos com uma dúvida. Na URL para requisição é informado o ID da conta do usuário e com isso eu consigo consultar os envelopes daquela conta, a dúvida é quando essa chave de API estiver no ambiente de produção eu poderei consultar o envelope de qualquer usuário da minha instituição ou apenas os envelopes vinculados ao meu usuário? Ressalto que tenho acesso de Admin. A URL que mencionei é: requests.get('https://demo.docusign.net/restapi/v2.1/accounts/account_id/envelopes

541
JohnSantos
Valued Contributor
S
Newcomer
sachinpowarNewcomer
asked in eSignature API
templateUsageRestriction

Hi docusign community, I'm working on creating some logic to dynamically update my template with different content. When I make a GET call to pull the custom fields I've added in template, I see this: GET Request results : { "textCustomFields": [ { "fieldId": "10351158661", "name": "templateUsageRestriction", "show": "false", "required": "false", "value": "allOptions" } ], "listCustomFields": []} Does anyone know what the 'templateUsageRestriction' means and how to extract the actual fields? Are there any settings needed in my DocuSign template?

1881
Alexandre.Augusto
Docusign Employee
K
Newcomer
KishorJayannaNewcomer
asked in eSignature API
Multiple recipients - need help on adding the multiple recipients on a envelop

Hello, Below is the request payload for which I’m trying to create an envelope and send it to multiple signers, but the problem is creating the envelope with a single signer. { "documents": [ { "documentBase64":"JVwj===" , "documentId": "1", "fileExtension": "pdf", "name": "EmploymentContractDocuSign.pdf" } ], "emailSubject": "Kindly review and sign the employment contract document for Person: Test 002.2:47", "recipients": { "signers": [ { "email": "test@gmail.com", "name": " kj", "recipientId": "22", "routingOrder": "2", "isBulkRecipient": true } ], "signers": [ { "email": "Test002@yopmail.com", "name": "Test", "recipientId": "11", "routingOrder": "1", "isBulkRecipient": true } ] }, "status": "sent"}

982
J
Docusign Employee
A
Newcomer
Aymeric.PNewcomer
asked in eSignature API
eSignature API - Envelope templates empty response

Hello, We are calling the eSignature API to retrieve the template ID used in an envelope (/envelopes/xxx/templates). Sometimes these calls return empty responses whereas envelopes were using a template - see below example : Green OK - Red KO Can someone explain why templates are not retrieved correctly ? Thank you !

875
A
Newcomer
R
Newcomer
RyanTranNewcomer
asked in eSignature API
Create and Send envelope on behalf of another user

How do you create and send an envelope on behalf of another user using the REST API?

10622
T
Docusign Employee
J
Newcomer
jay1994Newcomer
asked in eSignature API
Docx file corrupted after signing - This PDF file is encrypted and can't be opened

Attached sample docx seems to be corrupted after signing and trying to open via microsoft work , the docx has been signed via eSignature APIS.

1901
Alexandre.Augusto
Docusign Employee
J
Newcomer
JohnDeoNewcomer
asked in eSignature API
Is it possible to use the custom fields as a placeholder inside email to fill some data dynamically. So that the creator of envelope just fills in the information in the custom field and it will be used in the email body/subject etc..

Is it possible to use the custom fields as a placeholder inside email to fill some data dynamically. So that the creator of envelope just fills in the information in the custom field and it will be used in the email body/subject etc..

651
Alexandre.Augusto
Docusign Employee
J
Newcomer
jnjnjnjnjnjnjnjnjnNewcomer
asked in eSignature API
adding check boxes

I'm using Power Automate to add checkboxes to a document. The requirement is to include three checkboxes, with only one selectable at a time. How can I achieve this?

1463
Michael.Rave
Docusign Employee
M
Newcomer
MaxNewcomer
asked in eSignature API
How to populate the fields values from my database into a document template and send it to different email addresses?

I have a requirement to populate values from my database into the attached document in the template while sending to different users dynamically via API. Any insights?

831
Alexandre.Augusto
Docusign Employee
J
Newcomer
JeffKaufmanNewcomer
asked in eSignature API
Template fields in API

I have a template that I would like to pass data into before sending for signature. i see some fields in the template now but can’t update them. I would also like to add new fields. I’ve looked everywhere but can’t figure out how to do that. Can someone point me in the right direction? I am using laravel php, and have built a service to the template in an envelop as well as a webhook that is updated when the document is signed, so I know I am close. I would say I was tearing my hair out about this but I am bald.

1471
Alexandre.Augusto
Docusign Employee

Most helpful members this week

Badge winners

  • 1st Question Posted
    Pedro4679has earned the badge 1st Question Posted
  • 1st Reply Posted
    Ma.Cubiohas earned the badge 1st Reply Posted
  • 1st Question Posted
    Emarshallhas earned the badge 1st Question Posted
  • 1st Question Posted
    NimACChas earned the badge 1st Question Posted
  • 1st Reply Posted
    jenny.martinhas earned the badge 1st Reply Posted
Show All Badges

Popular tags

Code of Conduct

Docusign Community

Code of Conduct