Developer

I successfully configured a custom connector for DocuSign yesterday. It ran a couple of times, but today it had an error. Failed to refresh access token for service: oauth2. Correlation Id=39ea2047-xxxx-xxxx-xxxx-ef8ad5cb80a7, UTC TimeStamp=12/24/2025 1:00:44 PM, Error: OAuth 2 access token refresh failed. Client ID and secret sent in form body.. Response status code=NotFound. Response body: { "statusCode": 404, "message": "Resource not found" }   What would cause this? I tried creating a new secret and  added it to the custom connector but the test doesn’t work either (It did yesterday). 

We have build an app to allow our Customers to sign Up and use their docussign account. I am extremly consfussed - on stepsWhen we go to Promote the App into Production - Which email id do I need to give? As part of partner prohram do we get an account provisioned? Any clear documenation will helpful - atleast I coundt find any? 

I’m using the list envelopes action to get the status. This envelope has a bad email address.  but the API only shows it as ‘Sent’ I have also tried the Get_audit_event_list action. This does not show delivery failure either. This seems like a very basic requirement so it must be possible?

I'm using embedded signing in my app. It redirects from my web page to the DocuSign signing page, and after the user finishes signing, it redirects back to my web page. I want users to receive a completion email once they've signed, just like when they sign via email. Is that possible?  Do I need to modify the code, or can I do it through platform settings?  

Hi all,I’m stuck with a DocuSign JWT Grant issue and would appreciate help from anyone who has seen this before.ProblemCalling the token endpoint consistently returns:{ "error": "invalid_grant", "error_description": "user_not_found"}Token RequestPOST https://account-d.docusign.com/oauth/tokenContent-Type: application/x-www-form-urlencodedgrant_type=urn:ietf:params:oauth:grant-type:jwt-bearerassertion=<signed_jwt>JWT Details alg: RS256 iss (Integration Key):0a09f94b-xxxx-xxxx-xxxx-722da7e2846a sub (User ID):3af994a5-xxxx-xxxx-xxxx-adf23dce0cd3 aud: account-d.docusign.com scope

Does anyone know why we need “Express Signature” with the “IDV Premier” type of signature? 

I have a number tab called Employee Number.  How do I update this tab using esign API in C# before I send the email?This is my existing MakeEnvelope where I am attempting to do it:         public static EnvelopeDefinition MakeEnvelope(            string signerEmail,            string signerName,            string ccEmail,            string ccName,            string templateId)        {            // Data for this method            // signerEmail            // signerName            // ccEmail            // ccName            // templateId            EnvelopeDefinition env = new EnvelopeDefinition();            env.TemplateId = templateId;                        //env.AllowMarkup = "false";            //env.EnforceSignerVisibility = "true";            //env.RecipientViewRequest            Number employeeNumber = new Number            {

Hi, I have a weird behaviour I do not understand. I’m using the envlope-API to create an envelope based on a template (/restapi/v2.1/accounts/{{accountId}}/envelopes). My destination is the development tenant. For this API Call I use the following request body { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email": "Some.Name@test.com", "name": "Some Name", "roleName": "signer", "tabs": { "companyTabs": [ { "value": "test Company 1", "tabLabel": "atb.docusignFields.label-company <id>",

Hi,I’m trying to use Embedded Web Forms in my React App. I’m using the following Docusign NPM Packages: docusign-esign @ ^8.4.0 docusign-webforms @ ^2.1.0 I have created an Application at https://apps-d.docusign.com/admin/apps-and-keys, and I have requested the following OAuth Scopes, and approved these within the Browser:const scopes = [ docusign.ApiClient.OAuth.Scope.IMPERSONATION, docusign.ApiClient.OAuth.Scope.SIGNATURE, docusign.ApiClient.OAuth.Scope.EXTENDED, 'webforms_instance_read', 'webforms_instance_write', 'webforms_read', ];I use the `requestJWTUserToken()` method from the SDK to successfully authenticate using my Private Key and this returns an Access Token.I then use the `F

Hi, I’m implementing the SenderView in an iframe using the docusign-esign node package. I’ve set a returnUrl, however upon clicking Send in the iframe, it just redirects the user to the Sent list page instead of the returnUrl. As a result, we are unable to get any trigger or indication that the sending is complete and we don’t know when to close the iframe. Is this a known limitation? Are there any fixes or workarounds?

I recently used docusign connect in my application and i had this doubt, Are the events for an envelope queued before sending them in the order of occurring. lets say i had 3 levels and the final recipient just receives a copy, no signing action. Now two events will occur right, recipient delivered, recipient completed which will happen so quick, now will this 2 events triggered in parallel, or will it happen one after another. that is only after recipient delivered event gets a 100 response will recipient completed event sent?

Hi, I am generating a document in Google Docs where I add variables like {{NAME}}, {{EMAIL}}, etc. Then I export that file (PDF) and send it using the DocuSign API.The envelope sends successfully, but the variables are not getting replaced by the values I pass in the API. The final document still shows {{NAME}} instead of the actual name.I am confused: Is Google Docs the correct place to create documents with variables for DocuSign? Does DocuSign support the {{NAME}} syntax, or does it require special tags? What is the correct way to insert fields (merge fields / tabs) so that the values I send in the API appear inside the document? Below is what I want: Create document with placeholders Send envelope through API Fill placeholders with values programmatically  

 After changing my development account to a production account, the last step was to get this authorization code. I allowed access (granted permission) and tested it in Postman. I keep receiving this 400 error “Invalid Grant” “ Unauthorized Client”.  Has anyone encountered this error before? 

Hello, I’m using the DocuSign eSignature API to create an envelope draft from a template that uses DocGen and contains a dynamic table. After creating the draft and adding rows to the table programmatically, I attempt to add signature tabs anchored to text placeholders inside the table.The sequence of operations is:Create a draft envelope from a DocuSign template using the Envelopes API (POST /v2.1/accounts/{accountId}/envelopes). Add dynamic table rows via DocGen Form Fields API (PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId}/docGenFormFields). Wait for DocGen rendering to complete. Add signature tabs via Create Recipient Tabs (POST /v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/tabs) using SignHere tabs with AnchorString values matching the placeholders inside the table.The envelope and recipients are created correctly, and the table rows appear as expected. However, the sig

Hello, I’m currently trying to understand the eSignature API (I’m new to docusign). Our UseCase is to create a template for a document we want to send out to customers for signature This template should contain “variables” that needs to be pre-filled before sending out to the signee (e. g. a Customer ID or Name) Sending should work via API.I created a template with several variables (I just put random variables for testing inside, they do not make sense) Within my API Call I am able to send out an envelope with the help of a template by { "templateId": "{{templateId}}", "emailSubject": "Subject set by API", "emailBlurb": "Mailbody set by API", "templateRoles": [ { "email":

Hello - I have a custom integration that scans the Sent folder of a processor’s account for a completed document and moves it to another custom folder.If I click the custom folder, it shows the folder ID in the URL: https://apps.docusign.com/send/documents?folder={folderID}.  However for the Sent folder, it only shows https://apps.docusign.com/send/documents?view=sentYears ago the URL showed as it does with the custom folder with the folder ID, but now it now longer does.  How do I find the folder ID of the Sent folder?  I am switching accounts to a new processor

Hi there, I am setting up a docusign sending to some recipients through the developer API. Everything works fine but the emails recipients received show a document that can be edited by the recipients. Why is that? none of the fields I have added are editable. (the same thing happens when I test the signing in the docusign UI, meaning issue is not in my code). Thanks for your help 

Not sure if my last question was posted…As I said before, this is not much information on the JavaScript $.ajax call on the DocuSign REST API.  If there was, not much information on it (or even examples).I’m am trying to use JavaScript (JQuery) $.ajax call using a DocuSign REST API.  Even though I tested out on Postman successfully, it does not work using $.ajax (i.e. https://account-d.docusign.com/oauth/token) including the header information and the requested body (note the ${???} represent a placement of the actual values - just to be safe):                    let tkHeader = {                        'Content-Type': 'application/x-www-for-urlencoded',                        'Accep

Hey developers! Have questions about which OAuth grant to use? Trying to get an access token to test our APIs?This month’s AMA is all about OAuth 2.0 authentication at Docusign.The thread is open now through November 25—comment with  your question and I’ll get right back to you (I’m a Senior Programmer Writer at Docusign).To make this more fun, when you add a question, you’ll be automatically entered to win a$100 non-branded gift of your choice from Loop & Tie 🎁Topic for this AMA: Authentication and access tokensOAuth authentication is the foundati

I added to a document template a checkbox, and when i edit a data label, it don’t save the new label. There’s anything i might need to edit additionally?After edit the Data Label and save it, it return to the original value “Checkbox 1a31da89-4ae0-49…...”. I validated and i’m not using the Data Label anywhere. Any Data Label that i entered is reverted to the original value. 

There seems to be vert little information about using $.ajax call to a DocuSign REST API on the web.   Is it possible to use $.ajax? If there is, how can use setup $.ajax to perform an OAuth/Auth  Using https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id=${integrationKey}&redirect_uri=https://localhost Able to do this directly on a web page on the address line but not using $.ajax Get a token from the OAuth/Auth (https://account-d.docusign.com/oauth/token) If a access token is return, use it to GET/POST a DocuSign REST API through

Hii have a problem while sending a documents via binary transfer in multipart requests to the endpoint: POST /restapi/v2.1/accounts/{accountId}/envelopes Im receiving the following error:{"errorCode":"NO_DOCUMENT_RECEIVED","message":"The document element did not contain the encoded document, or there is a problem with the encoding. Bytes for document corresponding to documentId 1 not found in request. 'documentId=<x>' possibly missing from Content-Disposition header."} For some context, im sending the request from an SAP-System, and im limited to the http_interface that the system provides. I dont have full control over how the request is generated in the end and that is the problem i think:See → The content-disposition header of the added pdf-file is in lower case, while the tuturial (