eSignature API

planning to integrate DocuSign eSignature with a SharePoint Framework (SPFx) web part.RequirementsUsers submit requests through a SharePoint Online site. Upon submission, a DocuSign envelope should be created automatically and sent to designated recipients for e-signature. The organization has a single dedicated DocuSign service account. SharePoint users are not DocuSign users and should not be required to log in to DocuSign separately. Recipients should receive DocuSign emails directly and complete the signing process through DocuSign. The signed document and envelope status should be stored and tracked within SharePoint. Due to project constraints, the current approach being considered is calling DocuSign APIs directly from the SPFx web part.QuestionsWhat is the recommended enterprise architecture for this scenario? Can a single DocuSign service account be used to create and send envelopes for all SharePoint users? How should authentication be handled between SharePoint Online, Micro

We are using Signer Attachment tabs in a multi-recipient envelope. After completion, we can retrieve documents using Envelopes API, but there is no clear way to determine which signer uploaded which attachment. What is the recommended approach?

Hello,  I would really appreciate your help. Using the API, our envelopes are created and sent with the correct prefilled values. However, when our customers open the document for signing, one of the fields (“Title”) is covered by an editable textbox with some unrelated value.This is the document before signing (created with the correct prefilled valued, Name and Title):  And this is how customers see it when signing: The correct value (“1st Degree”) is underneath a textbox with “Staff”. We have no clue where it gets this default value from or how to edit out the textbox. I’ve recreated this field several times in the template and the issue still persists. This is what the template looks like: The backend is a simple POST request to DocuSign Base URL with this information: request_data = { "templateId": config["Processes"][process]["Template"], "templateRoles": [ { "email": signer_email, "name": signer_name, "roleNam

Hi,    Message: You have reached the maximum number of recipients permitted  for a single transaction in your account. Please ask your administrator  to increase your limit.  What we've tried:  1. Voided and deleted all envelopes on the account — error persists  2. Created a brand new developer account — same error occurs after ~20 envelopes  3. Verified only 4 unique recipient email addresses are used across all envelopes  4. Each envelope has exactly 2 signers, 0 CC — well within the documented 5-recipient per-envelope  limit  5. Billing & Usage page shows "Envelopes: Unlimited"  Account details:  - Environment: Demo (account-d.docusign.com)  - Account ID: *information removed due to PII*  - Integration Key: *information removed due to PII*  - HTTP User Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_452) (server-side integration)  Questions:  1. What is the cumulative recipient limit for developer accounts, and what is the timeframe  (daily/monthly)?  2. Is there a way to reset this

Hello Everyone,I am currently exploring the integration of DocuSign with SAP SuccessFactors and would appreciate guidance from anyone who has implemented this solution.I would like to know:Is there a pre-delivered or standard extension/connector available for integrating DocuSign with SAP SuccessFactors? If yes, could you please share where I can find the documentation, installation guide, or configuration steps? If no standard integration is available for my use case, would the recommended approach be to develop a custom integration using the DocuSign APIs? For those who have implemented this before, what architecture did you use (standard connector, SAP Integration Suite/CPI, custom APIs, etc.)?Any best practices, lessons learned, or reference materials would be greatly appreciated.Thank you in advance for your assistance.

We are unable to use checkbox in the payload as it not recognizable inside the Oracle Integration Cloud iPaaS "checkboxTabs":[     {       "tabLabel": "Terms_And_Conditions",      "selected": "true"     },     {       "tabLabel": "Newsletter_OptIn",      "selected": "false"     }]

I am using the createEnvelope endpoint using the structure envelopedefinition > compositetemplates > inlinetemplates > recipients > signers. For each of my signers, I want to customize the email body/message e.g. “Hi [Recipient1_Name], ...” but I don’t want this message to appear on the ERSD modal (see screenshot below) that pops up once they have completed two-factor authentication. I tried using the note string, but it has the same effect. Any thoughts that don’t mean updating this globally?   

Hi Team,I have created data labels for check box in DocuSign template and tried to populate check box data label through OIC. But we are not able to set the check box through value populated in check  data label.Attached documents for references.

We are experiencing an intermittent connectivity issue with the SAP SuccessFactors (SF) – DocuSign integration. Occasionally, when recruiters send offer letters from SuccessFactors to candidates through DocuSign, the system displays a connection/disconnection error.Observed Behavior:The issue is not occurring consistently and is difficult to reproduce. When the affected user refreshes the URL/page, the process resumes and works normally. No permanent failure is observed after the refresh. The issue has been occurring intermittently since October 2025.Request for Guidance:We would like to understand:What could cause these intermittent connection failures between SuccessFactors and DocuSign? Are there any known issues related to session timeouts, API connectivity, authentication tokens, or integration endpoints that could result in this behavior? What logs (Connect logs, API logs, envelope logs, or integration logs) should we review to identify the root cause? Has anyone in the community

 We are facing an issue with the SuccessFactors (SF) to DocuSign connector integration for offer letters.Current Process:The recruiter sends the offer letter from SuccessFactors. The candidate successfully receives the offer letter from DocuSign. The candidate reviews, signs, and submits the offer letter.Issue Observed:After the candidate completes the signing process and submits the document, the candidate is expected to receive a copy of the fully executed/signed offer letter. However, the candidate is not receiving the signed offer letter copy via email.Request:Could you please investigate the integration/workflow and confirm why the completed signed document is not being delivered to the candidate after successful submission? Additionally, please advise if any DocuSign notification or distribution settings need to be configured or updated.Note: Configuration was changed as per DocuSign docment

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 Checking API logs → no errors or warnings Verifying envelope status → shows as “sent”Despite all of this, no email is ever received by any recipient.At this point,

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 ? 

My developer account has not sent the envelope yet this month, but it prompts that the envelope limit has been exceeded.Account ID: 3******* 

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_Z2bXgzv   Fully Qualified Path: com.docusign.platform@1/AgreementParty/displayName   Type: TextBox2. Field Label: demo_field   Internal Name: C_demo_field_value_1Xkjiv   Fully Qualified Path: account._771d

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

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",        "routingOrder": "1"      },      {        "email": {{user2_email}},        "name": {{user2_name}},        "recipientId": "2",        "routingOrder": "2"      }    ]  },  "status": "sent"} The first order signer gets mail, after signing it shows that invitation was sent to 2nd signer but the 2nd signer did not get any mail in the inbox. After i forced “Resend” in the developer console, It sent the mail. What could be the issue?There is

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. The signer email/name matches the recipient definition. We are using a different authenticated DocuSign user (different access token) when calling CreateRecipientView.Questions:Does CreateRecipientView need to be called using the same DocuSign us

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? Under what conditions would the envelope recipient userId match the DocuSign account userId? Could this difference affect operations such as embedded signing (CreateRecipientView) or envelope access permissions? Is there a recommended way to map an envelope recip

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 get the same behavior when setting th

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 versus spaces and no underscores for the formula to work in my mind is counter intuitive.  Underscores should be used in all cases and consistent across the platform.Thank you for reading my venting on this issue. I’ve had to reformulate so

One of the recipient email addresses is no longer valid (inactive/incorrect email). The envelope status in Salesforce changes to "Sent", but DocuSign later fails for that recipient because the email address is invalid.Because Salesforce already marks the process as sent, we are unable to stop or handle  business process correctly.We want to know:How can we capture recipient email bounce/invalid recipient errors from DocuSign? Is there a webhook or DocuSign Connect event available for invalid recipient/email delivery failure? How can we send this failure information back to Salesforce automatically? What is the best practice to update Salesforce records when a recipient email becomes invalid after envelope sending? Has anyone implemented Apex REST + DocuSign Connect webhook for recipient delivery failures?