Developer

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

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.

Hi,I was talking to our sys admin about some cloud flare blocking that has since been resolved, but he asked me to ask you about this image I am attaching. Can you give us some information about this screen shot ? Thank you,maggie  

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 am working with a developer account and am receiving this error message:502: Error, {"error":"DocuSign send failed","detail":{"errorCode":"RECIPIENT_LIMIT_EXCEEDED","message":"The cumulative recipient limit has been exceeded."}}I tried deleting some envelopes but that did not resolve the issue. Our level of testing seems to be below the published threshold for a developer account.Can DocuSign reset or clarify the cumulative recipient limit on a free developer/demo account? I have also seen reference to some kind of account hold that would result in the same error message. Any insights would be appreciated.

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

 send 3 documents in a DS envelope - Offer Letter (signatures) Non Disclosure Agreement (Signatures) Benefits Overview no signatures or field completion required.Candidates are saying they cannot see the last document which is a one page benefit summary.  I have no idea why, unless it is because that doc requires no signatures it is just informational?  Has anyone else had this?

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

Hello DocuSign Support,We have completed the Go Live process successfully and are now in production, but every OAuth token exchange request is failing with the following error:  "error": "invalid_grant"  "error_description": "unauthorized_client"This has been confirmed via direct Postman testing with a correct request structure. Our technical team has ruled out all client-side configuration issues. We believe the root cause is that API access entitlement is not active on our production account. On our current IAM Starter plan, API access is listed as "Contact sales."We need the following resolved as quickly as possible:1. Confirm whether API access can be activated on our current IAM Starter plan or whether an upgrade is required.2. Provide pricing for the appropriate plan that includes full production OAuth token issuance.3. Activate API entitlement on production account ID 2********* immediately.This is blocking a live

I’d like to come back to the topic of getting shared access to DocuSign. Previously, we were granted shared access without the information that the access was for the entire profile and no old files could be hidden or deleted, due to that to protect some of the data, we revoked the access. However, upon checking possible solutions, Google says for DocuSign folders can be created with specific permissions, so it seems we could create a new folder for future documents only and grant access to others to that folder solely. The other option would be to move the old documents to a folder that would be restricted from view. Can you please explore these options and let me know if this solution would be possible? 

Hi everyone,I'm trying to connect to the DocuSign hosted MCP server (mcp-d.docusign.com/mcp) from an MCP client that follows the standard OAuth discovery flow, and I'm seeing what looks like an RFC 8414 deviation that I'd like to confirm before assuming it's an issue.The flow my client is doing is: Fetch https://mcp-d.docusign.com/.well-known/oauth-protected-resource. Returns 200 JSON, lists https://account-d.docusign.com as the authorization server. Per RFC 8414, fetch https://account-d.docusign.com/.well-known/oauth-authorization-server for the AS metadata. This is where I'd expect a JSON metad

I have had several people who were not able to access a DS agreement that I sent at all. She tried 3 different browsers, cleared cookies/cache etc.  Does anyone have any idea why this happens and what I might be able to do to fix this?  The first 2 signers in my organization were able to sign and when it gets to the third one - not in my organization she could not get to the document.  I double checked the email it was correct and she was using a computer and not on a phone.  I don’t want to make my first 2 signers sign again as they are executives and it is a bad look.  Is there another way around this?