Back to Docusign.com

Get Started
- - Get Inspiration
Groups
Events
Ideas

Docusign 2024 Release 3 Is Live! Discover the New Capabilities

27 days ago

Home
Community Overview
Help Forums
Developer
eSignature API

eSignature API

Find answers to your Docusign eSignature API questions.

344 Topics
756 Replies

When you subscribe we will email you when there is a new topic in this category

344 Topics

Most Replies

Most views

Newest First

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

346

8 hours ago

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.

412

2 days ago

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.

375

5 days ago

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?

424

6 days ago

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.

161

8 days ago

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!

345

10 days ago

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

191

11 days ago

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?

181

12 days ago

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

211

12 days ago

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.

241

13 days ago

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?

424

13 days ago

Nicholas H.New Voice

asked in eSignature API

User Management API - User List Failed Call

Hello, We were getting ready to “Go-Live” with our first DocuSign integration but when we went to start the process, it is showing that we don’t have 20 consecutive Api calls. Upon closer review, it looks like the “GetUsers” endpoint (list | REST API | Docusign) is registering as Failed when it cannot find a user. This doesn’t make sense because it is still a successful call is it not? We are using this to check and see if the user exists before creating the signature request. If they do not exist then we call the user Add API. Any insights into this? Is there a better approach that I am missing? Or do we just need to get past this initial fail and run multiple more tests to get to 20 consecutive successful calls?

203

14 days ago

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

182

14 days ago

Hengfeng GeRising Star

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

281

16 days ago

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&

132

16 days ago

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?

121

18 days ago

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

6279

18 days ago

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

353

18 days ago

trungduc74f1Newcomer

asked in eSignature API

Document does not load full page and shows loading so I cannot sign the document

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

30016

20 days ago

meyercdllNewcomer

asked in eSignature API

Need inventory of PowerForm fields within an account

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?

202

20 days ago

Nicholas H.New Voice

asked in eSignature API

Using API Embeded Signing with User Auto-Provisioning

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.

6810

20 days ago

evanLiNewcomer

asked in eSignature API

Focus View in Angular doesn't work

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

433

21 days ago

Scott.NiemanNew Voice

asked in eSignature API

Expand GET /{{baseUrl}}v2.1/accounts/{{accountId}}/envelopes to have query parameters that search documents by documentFields[?(name=='text')].value and contains() filter like OData

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.

577

21 days ago

CyrineNewcomer

asked in eSignature API

Issue During Go Live - OAuth Consent Error

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

353

22 days ago

JohnSantosValued Contributor

asked in eSignature API

Purging documents

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?

564

22 days ago

Page 1 / 14

Badge winners

JJackhas earned the badge 1st Reply Posted
AllieOlsonhas earned the badge 1st Question Posted
hnd01has earned the badge 1st Question Posted
lennysohas earned the badge 1st Question Posted
Rscraig11has earned the badge 1st Question Posted

Show All Badges

Code of Conduct

Sign up

Already have an account? Login

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Customer Login/Registration Developer Login/Registration

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Customer Login/Registration Developer Login/Registration

Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

Enter your e-mail address

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

Docusign Community

Code of Conduct