eSignature API

Hi everyone,We’ve encountered an issue with our DocuSign integration and are hoping someone can share their experience.Here’s the situation:We send documents to a DocuSign envelope and specify the documentId for each document in our API request. The API responds with the same documentId values we set. However, when we view the envelope in the DocuSign UI, the documentId appears to have been reset or renumbered (e.g., starting at 1).Has anyone else faced this issue or something similar? If so, how did you handle it?Thanks in advance for any insights!

Hi everyone,I have a question about integration keys in the developer account.If you create an integration key in a free developer account, you need to promote it to production using your production account to move it to production.What about a paid developer account? Do integration keys created in a paid developer account still require promotion to production, or are they promoted to production by default?

When using eSign API/SDK, can we somehow enable the option to attach the template PDF of the template/document to be signed via the developer console? If yes, then how?I know that after completing the signing process, the signer receives an email that contains the signed template. But in my case, I want to include the unsigned doc/template as an attachment in the sign request email sent to the signer!!

Is there a Docusign endpoint that could govern me all the agreements in the user account. I am able to authenticate the user and get the info for the user

Our company is in the DocuSign Partner Program and we have a developer/sandbox account in DocuSign, some of our clients are looking for the feature to have the signature recipients to verify their identity with Bank ID. All signature requests are sent from client instances to DocuSign, I am looking to add the verification feature in our DocuSign integration but the “Identity Verification” is not available on our sandbox account under “Signing and Sending”. How can I get this enabled? 

Hi everyone,I'm working on a DocuSign integration where I want to use a template that dynamically updates as it progresses through a multi-signer workflow. Here’s the flow I’m trying to achieve:The initial template is populated with some hardcoded values for the first signer. Once the first signer completes and the envelope is redirected to the next signer, the template should dynamically update certain fields (e.g., names, amounts, or other placeholders) using data retrieved from an Azure Storage Account via API. This process should repeat for each signer, with the template being updated dynamically based on the signer’s role and data pulled from Azure.Steps I’ve Considered:Use the DocuSign API to create an envelope based on a pre-defined template. Populate initial tabs (fields)

The CXO of a company needs to sign over 20 envelopes daily, which are sent from various systems like Salesforce, SAP and with the majority coming from Docusign web app. Currently, the CXO uses a mobile app for signing documents. The company has developed a new internal portal for employees, which includes functionality for managing approval processes. Now, the CXO would like to use the new portal to sign all of their pending Docusign envelopes. Is this feasible using embedded signing?

Hi there,We’ve been using the DocGen API (https://developers.docusign.com/docs/docgensend-api/) to create pre-populated documents using a word template. In our word-template we’ve been using a custom font family Ciutadella.We’ve been having mixed success with some generated documents (pdf output) looking accurate, and some seemingly using a different font or have issues with spacing or alignment.Are custom fonts support by this API / Docusign, and if so what steps do we need to take to ensure it can be successfully used?Thanks!

Hello,How can I increase the size of the signature window via the REST API ? I would like something like that :   Moreover, is it possible to only enable focused window to avoid closing the modal when touching the screen outside it Regards,Arthur

I am following this code sample and kept running into many errors.One of the error was that it could not find body so realized to use const result = await accountApi.createClickwrap(accountId, clickwrapRequest); instead of the following as given in code baseconst result = await accountApi.createClickwrap(accountId, { clickwrapRequest });But now I am stuck at 401 error, unable to understand the error at all. {  statusCode: 401,  header: Object [AxiosHeaders] {    'cache-control': 'no-cache',    'x-docusign-tracetoken': '86….,    'x-docusign-node': 'DA...',    'strict-transport-security': 'max-age=31536000; includeSubDomains; preload',    date: 'Thu, 23 Jan 2025 19:04:23 GMT',    'content-length': '0',

Hey, I try to localize email and sing compent by signing user and I send by API envelop body: {  "documents": [    {      "documentBase64": "{{document}}",      "documentId": "123",      "fileExtension": "doc",      "name": "document"    }  ],  "emailSubject": "Custom subject",  "BrandId": "brand id from portal",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "{{recipientId}}",        "routingOrder": "1",        "localePolicy": {         "cultureName": "es-ES",          "languageCode": "es"        },         "tabs": {                    "signHereTabs": [                        {                            "anchorString": "/sn1/",                            "anchorUnits": "pixels",

When defining an embedded signer, we need to provide a clientUserId along with the recipient's name and email. The clientUserId is a sender-defined identifier for the embedded recipient, enabling the generation of a signing URL for them. How can this be accomplished when envelope is initiated using the DocuSign web app and recipient should sign using embedded signing in a custom built mobile app

Hello,Using REST API , zoom buttons arent visible until a signature has been drawn on the document , how can i fix it please ?regards,Arthur

I am using the DocuSign API to create an envelope with a document that requires signatures from three different signers. My implementation involves the following: Embedded Signing: I need to generate recipient views for all three signers. However, I am currently only able to generate the view for the first signer. When I attempt to generate views for the other two signers, it doesn't work. How can I resolve this issue to allow recipient views for all three signers? Webhook Triggers: I have set up a webhook with specific events configured. I need to be notified when the first signer completes their signing so I can generate the recipient view for the next signer. However, I am not receiving the event that indicates the first signer has completed signing. Which specific event(s) should I configure in the webhook to ensure I get notified when a signer completes their signing? Are there additional s

I have this error when i’m trying to send an envelope:"errorCode":"ACCOUNT_LACKS_PERMISSIONS","message":"This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document ..."this is the production account. Testing in the developer account i never get that error. What is the soultion for this issue ?  

Jumping in late, but trying to change to OAuth for authentication.Created a new app, but not seeing where to consent. (OAuth error no consent) Tried following instructions here:https://www.docusign.com/blog/developers/oauth-jwt-granting-consentfor admin consent.  Points to send support email at go-live if missing admin piece.Tried emailing support, got a not monitored email.  Tried logging into support, but always get error email / password. Can’t figure out how to get a call back, we do have live integrations in place.  

Hello,I am using the createBulkSendRequest() function from docusign.BulkEnvelopesApi to send a bulk signing request to 20-30 signers. However, I would also like to send a carbon copy of the documents to the manager.Currently, adding the manager as a carbon copy (CC) recipient in the bulk list results in the manager receiving 20-30 individual emails—one for each signer. Is there a way to send a bulk request to 20-30 recipients while ensuring the manager receives only one email or a single copy of the documents? Thank you.

1. pass the go-live review,2. then select a go-live account,input the production email3.input passwordthen get error, does anyone have idea?Thanks a lot

Is there a way to customize the email sent from the Agent to customer to not have the originating senders name to be on the email from the API? On the image attached (everything in red) is there a way to put the Agents name in place of the original sender's name so the customer recognizes the document? 

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. 

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

Hi, is there event callback for elastic template, when clickwrap is rendered and user first click on agreed and than another modal show to send document to email, so I’m curious if there is event when user clicked on request document via email?

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.