eSignature API

Hey Community - hope you’re having a good day...long weekend (In UK) nearly here ! When a Completed Document gets ingested into Workday (via API) for downstream storage and processing, is that document a copy of the ‘original’ ? In other words, would a version / copy of the completed document be stored in both DocuSign AND Workday or only a ‘master’ copy stored within Workday ? Also - does the Certificate of Completion ‘route’ with the completed document into Workday (for audit) ? Hope that makes sense ! Thanks in advance. 

Hello DocuSign Support Team,I am experiencing an issue with pre-filling document generation (DocGen) form fields when creating and sending an envelope via the REST API. Despite trying multiple approaches, the fields are rendering as unresolved placeholders (e.g., {{Agreement Party}}, {{demo_field}}) in the document instead of showing the values passed through the API.---ENVIRONMENT- API Base URL: https://demo.docusign.net/restapi/v2.1/- Template ID: 3cfaca9c-ffd5-4c16-a416-992ca05317b0- Template Name: Final Contract AI- Document Type: .docx (ACE/DocGen format — isAceGenDocument: true)---FIELD DETAILS (from template response)The template contains two DocGen form fields confirmed via GET /templates/{templateId}:1. Field Label: Agreement Party   Internal Name: AgreementParty_displayName_Z2bXg

Hi, I am consuming Doc gen api to automatically generate a document in which I have an image tab. <# <Image Select="//Internal_Signature" Height="1" Width="2" Optional="true"/> #> My original image is very small and need not exceed height and width of 1 inches, but I am unable to add less than 1 inches in the above parameter.Template is in a word doc which I am passing to api The one highlighted is from the image tag, original image is below. Can someone share inputs on how to adjust the image size

Hello,I’m currently integrating DocuSign into my ERP system using the API, and I’m working with a developer (demo) account.For several weeks, everything was working perfectly:Envelopes were successfully created via the API They were sent without any issues Recipients were receiving the email notifications and could sign documents normallyHowever, starting about a week ago, the behavior changed unexpectedly.Now:The API still works correctly (no errors returned) Envelopes are created and sent successfully Recipients are correctly assigned But no recipient receives any email notification at allTo troubleshoot, I have tried:Sending to multiple types of email addresses (personal, professional, temporary emails) Recreating a completely new developer account → it worked once for a single envelope, then the same issue occurred again

Hi, i am currently in the developer phase, I was testing if multiple routing order can be done. Made a request with the following api{{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesand with body{  "documents": [    {      "documentBase64": {{document}},      "documentId": {{documentId}},      "fileExtension": "pdf",      "name": "document"    }  ],  "emailSubject": "Multiple Signing Example from api testing",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "1",

Hello,I am experiencing an issue with the embedded signing flow and would appreciate any guidance.Scenario:We create envelopes using a system administrator account via the eSignature REST API, then attempt to generate an embedded signing URL (CreateRecipientView) while authenticated as a different DocuSign user.Error received when calling CreateRecipientView:{ "errorCode": "ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE", "message": "This account is not authorized to access the requested envelope."}What we have confirmed so far:The envelope is successfully created by the admin account. The accountId used in the CreateRecipientView endpoint matches the one used during envelope creation. recipientId and clientUserId are set in the CreateEnvelope request.

Hello,I have a question regarding the userId assigned to recipients in an envelope versus the userId of an actual DocuSign account.Scenario:When we create an envelope via the eSignature REST API and then retrieve recipient information using the listRecipients API, the userId returned for the signer is different from the userId of the corresponding DocuSign account (retrieved via the Users API).For example:DocuSign account userId (Users API): AAAAA... Envelope recipient userId (listRecipients): BBBBB...The signer email address is the same in both cases, but the IDs do not match.Questions:Is the userId returned by listRecipients intended to represent a recipient-specific identifier rather than the actual DocuSign account userId?

I got a requirement as mentioned below:I will be triggering the journey from the oracle HCM, once the employee completed signing the document it need to be moved to oracle HCM document of records, Is that feasible to move the pdf file from Docusign to oracle HCM document of records ? 

Hi,I’m on a developer sandbox still. My connect setup is set with ‘acknowledgement required’ enabled.I’ve implemented the webhook callback endpoint. It is working fine. I’m trying to test what happens on retries if the initial callback fails. I’m returning http code 500 from the webhook endpoint. It is going through `ngrok` and I see that it is being propagated. The connect dashboard shows the event error code as ‘Success’. The API call to fetch failures returns empty. No retries are sent.The only way I managed to cause it to log an error and retry is if I stopped the process enough for the 100 second limit to engage.I thought maybe something was ‘stuck’ in the settings so I wanted to disable and re-enable the ‘acknowledgement required’ setting, so I tried to disable ‘acknowledgement required’ but upon saving and refreshing, the setting comes back as enabled. I tried to update it through an API call with the same results.I also tried to do see if I

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My Azure web App Service to supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

Hello Every One,I’m refactoring an Apex class to follow Apex Toolkit best practices for DFSLE. Is there a way to set a system user as the envelope sender instead of the executing user, while still allowing other users to send envelopes?thank you in advance, Best Regards,

Web Form In our travel form we use a formula to pull information from the form to act as the email subject.  I find the inconsistent use of underscores.The information being pulled from the form is from the Web Form Field API reference name and that information does not allow spaces:Travel Start DateAPI reference Travel_Start_Datethere are underscores in place of the spaces for the API referenceWhen you use the information in the formula, the underscores need to be removed:[[ECF:Travel Start Date]]When the email comes from Docusign there are underscores where the spaces used to be. Email subject 2026/05/14_Initiator_Firstname_Lastname_Travel_Destination_NameI’m not sure where this development evolved but the inconsistencies of underscore for spaces v

Hi Team,We are facing an intermittent issue while integrating with DocuSign using the Node.js SDK.Issue DescriptionWe are calling the createEnvelope API from our Node.js application. In some cases: The API call times out (60 seconds) on our side However, the envelope is successfully created in DocuSign within ~7–10 seconds A webhook (Connect event) is also received successfully The problem is that the API response is not received by our applicationExpected BehaviorThe createEnvelope API should return a response with envelopeId once the envelope is created.Actual Behavior Envelope gets created successfully Webhook is triggered But the API call results in:

[Posted originally on Partner Innovation Community, but this is probably a better place to post]Hi all — Rafa from Simple Proof here 👋 Quick intro: we're a DocuSign ISV partner. We've built an Extension App that generates cryptographic proofs of completed envelopes and anchors them to the Bitcoin blockchain. In plain terms — when an envelope completes, we hash the final signed PDF and create a tamper-proof timestamp that anyone in the world can independently verify, forever, without trusting us or DocuSign. Our customers include government agencies and election authorit

Hi all,First post here so be patient with me :)I created a template a few pages long with signature and date of signing lines.The workflow is:Fill out form on web app Web app uses form data to replace text in a word file (agreement) and in turn, sends form data (recipient) and document to DocuSign to create envelope. The template is also set in code for use.Intended outcome:Client opens document, clicks to sign and date - job done.Actual outcome:Client opens document, nothing to click - no signature or date fields present.Envelope Inspection:Looking at the document in the created envelope, the signature and date fields are not there (although the template is applied). The document does not show page breaks in this view either.Manual Test:I clicked “Use” on the template, entered recipients and clicked next - signature fields are there

https://support.docusign.c> Document file limit:om/s/articles/DocuSign-Document-and-Envelope-File-Size-Limitations?language=en_US)Hello, I have a question similar to In my envelop, we send the following files which I converted to base64 : ```Size Name299k 69e772f5b28637.57190393.pdf.b64521k 69e772f5cf6a18.49898668-1.pdf.b64521k 69e772f5cf6a18.49898668.pdf.b641.5M 69e772f5f03d22.08961500.pdf.b644.1M 69e772f6b8acf3.84730872.pdf.b641.0M 69e772f7bc72c.pdf.b644.0M

Hi DocuSign Community,I am currently in the planning phase of integrating DocuSign eSignature into our real estate agency platform, which consists of a Laravel-based web portal and a Flutter mobile application (iOS & Android). I have a few questions regarding licensing and API integration that I hope the community or DocuSign team can help clarify seeing the email support only for trial/paid account. Even the chat doesn't work for me no matter how i tried to initialise it.---LICENSING & PLAN QUESTIONS1. We are planning to use a single DocuSign account/license across our platform, where multiple agents will be sending documents to clients for e-signature on a daily basis (after each case submission). Is this allowed under a single license, or does each agent require their own?2. What is the envelope (document) sending limit per month or per year under the Standard or Business Pro plan? If agents are sending documents daily, is there a risk o

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

It is quite important to allow closing vulnerabilities, could one please review and accept this pull request https://github.com/docusign/docusign-esign-php-client/pull/253 to allow make our system safer and also make your system safer since it’s related to the communication between the two.

Hi DocuSign team,I'm stuck in a loop trying to enable SMS and WhatsApp delivery on my developer sandbox account. I've been advised to open a support case, but support.docusign.com won't authenticate me. What I need:  Enable SMS and WhatsApp delivery on account 7ba44489-edcb-4415-9dd9-3632e018480c.What I've tried:  1. Viewed a post on this community with the same request. The reply     redirected me to open a support case.  2. https://support.docusign.com → Log in     - Tried "eSignature and IAM Applications" category → password       rejected every attempt (same credentials that work on       apps-d.docusign.com and developers.docusign.com).     - Tried "Docusign Partner" category → same rejection.  3. Attempted to sign in at developers.docusign.com and navigate     to a support form from there — no developer-specific case     portal is exposed afte

I have a template that has a single signer that is a signing group. I need to create an envelope from this template using API calls.  The API requires an email and ends up creating a new signer in addition to the signing group that’s in the template. Is there a way to create the envelope so it only has the signing group as the single recipient?

We would like to integrate an Aadhaar-based e-Signature API into our application, where as developers we can send a PDF document and allow the end user to complete Aadhaar e-sign on it.Could you please provide guidance on the following: How to use the Aadhaar e-Sign API for uploading and sending a PDF for signature The complete integration steps and workflow involved How the end-user authentication (Aadhaar OTP/biometric) is handled in the process Steps to configure and enable this feature in a demo/sandbox account for testing Any required API credentials, documentation, or prerequisites to get started We are currently in the initial integration phase and would like to test the functionality in a demo environment before moving to production.Kindly share the relevant documentation, API references, and onboarding steps.Thank you.

Hello.i’m working with a microservice API to connect my applications with Docusign APIs.I have an issue that my client web application are not alowed send document to my API for business rules reasons.There is any option to upload the document within a empty envelope over a presigned URL, that my API generates in Docusign APIs and then my web client just upload the document directaly?I have searched over API documentation but didnt found anything

Is it possible to set reminders and different reminder frequencies for each user? In other words, so that all the envelopes sent by a user have different reminders and frequencies. ¿Es posible establecer recordatorios y frecuencias de recordatorios diferenciadas por usuario? Es decir, para que todos los sobres que envíe un usuario tengan unos recordatorios y frecuencia diferenciados. Would it be possible to include in the API the option to choose the reminder frequency for each envelope? ¿sería posible incluir en la API la posibilidad de elegir la frecuencia de recordatorios por sobre? Is it possible to include in the API the ability to send copies without requiring a signature? In other words, in Docusign we can decide whether the person receives only a copy or, conversely, must sign—would this be possible in the