eSignature API

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_PHO

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

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.

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;

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?

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 asynchron

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. 

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

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.

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

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?

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.  

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!

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  

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. 

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

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?

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

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 no

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>

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?

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(pro

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", "prop

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

We have integrated DocuSign for a multi-signer workflow with 3 signers using our Node.js application. In most, cases, the signing process work as follows:Signer 1 → Signer 2 → Signer 3 (all signers complete the document one after the other)This is working fine for scenarios where all 3 signers are required.However, we have a specific use case where:1. After Signer 1 completes the signing, we need to  update the second signer’s information dynamically and Skip Signer2(in certain conditions).   Continue directly to Signer 3 to collect their signature2. In other cases, we want to proceed as usual, where all 3 signers complete the document in sequence.Questions:1. Is there a way to conditionally skip a signer(Signer 2) after the first signer has completed the signing process?2. Can we update the document or signer information dynamically(ex: update signer name, date of sign)3. What is the recommended