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

eSignature API

Find answers to your Docusign eSignature API questions.

  • 492 Topics
  • 1,058 Replies
492 Topics
z3nkarun
Newcomer
z3nkarunNewcomer
asked in eSignature API
EnvelopeViews: createSender: Preview - Does it not work with Docusign JS

I see this documentation of docusign JS embedding to get the event just for Signing view. Is this not relevant for when we create Preview urls of Envelope? I have created and envelope and opening up a preview within an iframe. I wanted to catch events directly in my parent window but doesnt seem to be working. 

412
z3nkarun
Newcomer
A
Newcomer
aliciaNewcomer
asked in eSignature API
Create Drawn Signature using C# API

Hi,Im using the Docusign eSignature REST API (c#) to create envelopes for recipients for signing.I require my recipient to either sign the document by selecting a signature or by free hand drawing signature. Currently only the option to select a signature is showing, I see no option to choose to draw as well as select a predefined signature. I have gone into the Settings page then Signing Settings and configure the Signature Adoption configuration, and enabled the option for drawn eSignatures as suggested here :Drawn Signature | Community but this didn't work for me.This is my code: - as you can see i just have one signature achor , and one signed date achor.  SignHere signHere = new SignHere  {      AnchorString = "**signature_1**",      AnchorUnits = "pixels",      AnchorYOffset = "10",      AnchorXOffset = "20"  };  DateSigned mydate = new DateSigned  {      AnchorString = "**signed_date**",      AnchorUnits = "pixels",      AnchorYOffset = "2",      AnchorXOffset = "20",      FontS

693
K
Docusign Employee
M
Newcomer
ME DeveloperNewcomer
asked in eSignature API
Sms & Whatsapp Delivery not working

Hello,I'm having trouble creating the envelope when I set the delivery method to SMS or WhatsApp. In my tests, I send the following JSON to the Docusign API:{  "emailSubject": "Test AppBuilder - 1_1",  "documents": []  "recipients": {    "signers": [      {        "roleName": "CONTRACTOR",        "name": "Carlos Oliveira",        "email": "",        "recipientId": "",        "routingOrder": "1",        "clientUserId": "",        "deliveryMethod": "SMS",        "phoneNumber": {          "countryCode": "55",          "number": ""        },        "tabs": {},        }    ],  },  "status": "sent",  "sentDate": 1736456976955,  "completeDate": null}The country code is the country code of Brazil.I get an error while requesting server, received a non successful HTTP code [400] with response Body: "errorCode": "INVALID_PHONE_NUMBER_FOR_RECIPIENT","message": "The Phone number is invalid. Envelope definition is missing a phoneNumber for recipientId: "

632
M
Newcomer
z3nkarun
Newcomer
z3nkarunNewcomer
asked in eSignature API
SenderView - Do I create a SenderView Preview URL everytime ? or retain url

Hi Team, Working on an integration utilizing template and sending an envelope. Before sending I want to generate a preview url. This preview url is different everytime I hit the api. How long does this preview url lasts? whats the best practice on generating sender views? Should I retain the generated url until the envelope is sent ? Sender API Regards, Karun

392
z3nkarun
Newcomer
D
Newcomer
djrtjfhdfdtyn45645ytdfgNewcomer
asked in eSignature API
Embedded Sign with JS library at Angular (typescript)

We noticed that DocuSign provides a JavaScript library that seems to enhance the embedding process. However, our project is built with Angular and TypeScript, and we couldn't find documentation specific to TypeScript integration. Could you please share any documentation, resources, or tutorials that could guide us in integrating the library effectively in our environment? Your assistance would be immensely helpful.

1272
D
Newcomer
C
New Voice
cweeksNew Voice
asked in eSignature API
How to send as an Agent

I am using an C# example for sending documents to recipients and that works, but I want to send to an agent since I will not know the recipients, but when I add the Agent, the email never prompts for the signer emails to forward to?    Agent agent1 = new Agent   {       Email = signerEmail,       Name = signerName,       RecipientId = "1",       RoutingOrder = "1",   };     // Add the recipients to the envelope object   Recipients recipients = new Recipients   {       Agents = new List<Agent> { agent1 },             };   env.Recipients = recipients;

282
A
Docusign Employee
K
Newcomer
KhoaNewcomer
asked in eSignature API
Integrating e-signature for React

I want to integrate DocuSign e-signature into my React app, but I can't find any documentation. Could you please share the documentation or guide me on how to do it?

1211
B
Docusign Employee
G
New Voice
G GadowNew Voice
asked in eSignature API
Call to RequestJWTUserToken hangs

Package: DocuSign.eSign.dll (8.0.0.0)Environment: Asp.Net CoreLanguage: C#Demo code:DocuSignClient dsClient = new DocuSignClient(DocuSignClient.Demo_REST_BasePath);DSAuth.OAuth.OAuthToken oaTok = default!;List<string> scopes = new List<string>() { "signature", "impersonation" };byte[] privateKey = File.ReadAllBytes("c:\\Test\\Private.key");DSAuth.OAuth.OAuthToken tok = dsc.RequestJWTUserToken( Properties["IntegrationKey"],    Properties["UserId"],    Properties["AuthServer"],    privateKey,    1,    scopes); I have verified that the values for IntegrationKey, UserId, and the private key are set up in DocuSign correctly and turned on, and that I am using the correct values. I have verified that the authentication server is the correct one (demo.) But when I run this, it just hangs. No response. I have set this up to run asynchronously, and the same thing: it never resolves. This used to work, but it broke some time in late October I think it was. All of the example code I

644
G
New Voice
N
Newcomer
NGWestmeathNewcomer
asked in eSignature API
Embedded Url - User might not have an account

We are currently implementing a DocuSign Esignature integration. Our application is multi-tenanted.  What is the best way to handle users who need to sign a document via an embedded URL without logging in. My understanding is that the user would need to log into DocuSign to generate the URL or have a embed url sent via API by a sender account. Is there a way to avoid this requirement?Some of our user will not have a DocuSign account and would not be willing to sign up. Is there another way to get the URL with minimum user interaction?Our ideal scenario would be that the user logs into our application, selects from a list of envelopes, and signs the document via a embed URL. The user should not have to login to docuSign. 

491
JohnSantos
Valued Contributor
U
Newcomer
umar8092Newcomer
asked in eSignature API
API Endpoint for Creating Contacts Returning ACCOUNT_SPECIFIED_INVALID

Hi DocuSign Support Team,I am reaching out regarding an issue with the API endpoint for creating contacts.When making the following POST request to create a contact:curl --location 'https://api.docusign.net/restapi/v2.1/accounts/{accountId}/contacts' \--header 'Content-Type: application/json' \--header 'Authorization: Bearer {access_token}' \--data '{  "contacts": [    {      "name": "John Doe",      "emails": [        "john.doe@example.com"      ],      "organization": "Example Corp",      "shared": "true"    }  ]}'We receive the following error response:{    "errorCode": "ACCOUNT_SPECIFIED_INVALID",    "message": "The account id provided does not exist, or is improperly formatted."}However, when the request method is changed to GET and the body is removed, the call works as expected, confirming that the account ID is valid.Could you please assist in identifying the root cause of this issue? It appears the endpoint is not processing POST requests correctly for contact creation.Thank y

638
JohnSantos
Valued Contributor
J
Newcomer
JerseySTEMNewcomer
asked in eSignature API
Bypassing User Authorization for access token

We are currently working on integrating DocuSign with our MySQL database using the low-code ETL tool Integrate.io. During the integration process, we've encountered an issue related to the redirect URI.Our primary question is whether it is possible to integrate the DocuSign API without requiring the user-authorization step to generate an access token. Specifically, we want to confirm if the integration can be achieved using only the client secret and integration key, bypassing the need for individual user authentication.Additionally, we're wondering if there are any other authorization grants, other than JWT, that might be more suitable for this situation.

1402
A
Conversation Starter
C
Newcomer
cjDevNewcomer
asked in eSignature API
API Usage Center showing zero API calls

Why is API Usage Center showing zero API calls against my integration key? I have been testing using this key since last 1 week.

505
JohnSantos
Valued Contributor
J
New Voice
JijingNew Voice
asked in eSignature API
How to sign two documents simultaneously

I hope to achieve this function. I write my signature in the signature panel, then click sumit. The signature positions of the two documents I preset above can be signed. Can this function be achieved?

614
A
Community Moderator
N
Newcomer
NoelleWNewcomer
asked in eSignature API
Is there any way to convert a remote signer to an embedded signer after they've already been created?

Is there currently a way to update a remote signer to be an embedded signer instead, after the signer has already been created? I tried using the envelopesAPI’s updateRecipients() method from the PHP SDK with a mapped version of my recipients with clientUserIds assigned to them (since this is my understanding of what makes a signer “embedded”). But, when doing so, I still wasn’t seeing an embedded signer’s view for the signer whose clientUserId I had updated.  

431
JohnSantos
Valued Contributor
K
Newcomer
kiranbaby14Newcomer
asked in eSignature API
Help Needed: Building Standalone Web App with DocuSign

Hi DocuSign community!Project Goal: I'm building a standalone web application for the Docusign hackathon where I want users to:Log in to my web app using their DocuSign account Once logged in to my application, they should see all their DocuSign contracts/envelopes The application is completely separate from DocuSign, just using DocuSign for authentication and fetching contracts I am planning to have a python application in the backendI'm new to DocuSign and would greatly appreciate if someone could guide me through the proper process of implementing this. What would be the right approach and what are the key steps I need to follow?Thank you in advance for any help!

545
Kelly.Shalk
Docusign Employee
Z
Newcomer
zhangNewcomer
asked in eSignature API
400 with response Body: '{"errorCode":"USER_AUTHENTICATION_FAILED","message":"One or both of Username and Password are invalid."}'

After I moved the program to production, when I called envelopesApi.createEnvelope(accountId, envelopeDefinition), I got this error.Error while requesting server, received a non successful HTTP code 400 with response Body: '{"errorCode":"USER_AUTHENTICATION_FAILED","message":"One or both of Username and Password are invalid."}' what should i do  

781
L
Docusign Employee
N
Newcomer
NoelleWNewcomer
asked in eSignature API
Envelope fields not showing in recipient view

Hi everyone! I’m running into an issue with DocuSign's envelope API recently and I’d love some more insight as to why.I start by creating a two-signer envelope. One signer is embedded from my external integration, and the other is added within the sender view in DocuSign. After adding signer fields, I use the "Preview" button to check that the fields show up for both signers. Both signers have clear signing fields. However, when I create a recipient view through my integration, no signer fields appear for the remote signer. Here is the envelope prior to pressing “Preview”.Blue = added externallyYellow = added during the “Sender view” Here’s how the fields for the signer I added within DocuSign's “sender” view appeared when I was using the “Preview” button. But, here’s how it looks when creating a recipient view for that same signer. Any ideas as to why this is? 

571
JohnSantos
Valued Contributor
R
Newcomer
Rithish_KumarNewcomer
asked in eSignature API
Docusign Integration with SAP for Contract Approval Workflow

Dears,The requirement is to have the signatures of all the approvers of Purchase Contract in the contract document generated in SAP.There is already a workflow setup in SAP for the Approval process, now once a user approves the contract in SAP inbox, I need to get the signature of the approver on the document and send the workflow to further approvals.Is there any API to directly open the document for signing and sending the response back to SAP System!?Or any feasible approach or insights would be helpfulThanks

591
I
Docusign Employee
A
Newcomer
alaxosNewcomer
asked in eSignature API
¿How to sign multiple pages (SignHere tab) without using AnchorString to place the tabs?

Hi guys, I want the signers to be able to sign all pages of all documents, i.e. page by page they can click on the (SignHere) tab.I can also consider the option of them signing only the first page and the signatures being replicated on the others.Is this possible using Java SDK?

894
A
Conversation Starter
V
Newcomer
vladNewcomer
asked in eSignature API
fix error AUTHORIZATION_INVALID_TOKEN

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 

1032
B
Docusign Employee
Hengfeng Ge
Frequent Contributor
Hengfeng GeFrequent Contributor
asked in eSignature API
please update the Docusign endpoint IP addresses in https://www.docusign.com/trust/security/esignature

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

691
M
Docusign Employee
M
Newcomer
meilinglamNewcomer
asked in eSignature API
SOAP API RequestStatus does not return RecipientId

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&

222
I
Docusign Employee
B
Newcomer
BridgetLyonsNewcomer
asked in eSignature API
Dayforce DocuSign Integration going Live

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?

1281
Alexandre.Augusto
Docusign Employee
R
Newcomer
RabGhNewcomer
asked in eSignature API
Next.js App Router, TypeScript, building DocuSign Api

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

8879
K
Newcomer
M
Newcomer
mfrieswykNewcomer
asked in eSignature API
simple field mapping using api to create an envelope and auto-populate std text fields in a template to create a document for signing

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

823
T
Docusign Employee

Badge winners

Show All Badges
Code of Conduct

Docusign Community

Code of Conduct