Developer

Hello,We are using IAL2 compliance identity verification and want to customize email body when sending documents to customers. I am sending my template in emailblurb property within envelope definition. But somehow it is overrriding and sending me some default email. Can you please help me here? Do we have any restrictions on email body if we are using IAL2 IDV ? Thanks!

Hello,I’m using a DocuSign template that is sent via the API and pre-filled with dynamic values (for example: full_name, date_from, date_to, price, etc.).The values are populated correctly using Text tabs (via tabLabel), however I’m running into a layout issue:The text fields have large visible gaps, because the text tab has a fixed width. Since the data is dynamic (names, dates, values can be longer or shorter), I can’t reliably determine how wide the field should be ahead of time.My questions are: Is there any way for a DocuSign text field to automatically resize (shrink/grow horizontally) based on the value that is injected? If not, is there a recommended best practice for handling dynamic inline values in legal documents without creating large spacing gaps? Are

Hi everyone,I’m running into an issue where I cannot retrieve the actual comment data from an envelope using the primary Get Envelope endpoint, even when including all relevant parameters.The Goal: I want to retrieve the contents of commentThreadTabs (specifically the comments array) in a single request to avoid making multiple calls per envelope.The Problem: When calling GET /v2.1/accounts/{accountId}/envelopes/{envelopeId} with the following query parameters: ?include=workflow,documents,custom_fields,recipients,tabs,prefill_tabsThe response returns the commentThreadTabs object, but the comments array inside it is always empty.Observations: If I use the specific GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}/tabs endpoint, the com

Long story short, I had an embedded E-Signature set up and working without issue last month. Now it only works on my staging server and not on my local. Locally I’m receiving the screenshotted error in my console along with many more. I’ve been trying to work through it with google and other posts be am getting no where and falling behind on my development schedule. Any assistance would be greatly appreciated.Thanks,Andrew

I'm getting USER_AUTHENTICATION_FAILED errors when creating envelopes via the API in production, even though JWT token generation and get_user_info() succeed.Setup:Production account: eSignature Business Pro Authentication: JWT (Service Integration with RSA keypair) Integration Key SDK: docusign-esign PythonWhat Works:JWT token generation succeedsget_user_info() returns account detailsAdmin consent grantedWhat Fails:EnvelopesApi.create_envelope() returns: Error: (400) Bad Request errorCode: USER_AUTHENTICATION_FAILED message: "One or both of Username and Password are invalid." Trace-Token:Code flow:Get JWT token via request_jwt_user_token() Call get_user_info() to get account_id and base_uri Set base_path to account.base_uri + '/restapi' Set Authorization header wi

RecipientViewRequest viewRequest = new RecipientViewRequest();viewRequest.setReturnUrl(redirectUri); My redirectUri is 'http://localhost:8089/callback'and after user do sign and click finish in loaded iframe - below call fails'http://localhost:8089/callback?event=signing_complete'with error 'The connection is blocked because it was initiated by a public page to connect to devices or servers on your local network.' What this error means and how to resolve this issue. Please help

Hoping someone can help,My company has been using eSignature API in our application for a couple of years. As part of our DocuSign implementation we periodically check for envelopes that have been updated using a request with the following format:GET https://na4.docusign.net/restapi/v2.1/accounts/[accountid]/envelopes/status?from_date=2025-09-06T23:25:57Z&from_to_status=changedGenerally this works fine, but we’re getting 408 - Request timed out - responses in some cases and I can’t see any obvious reason why. Any ideas?Some other things to note:This may be related to the fact that this is uses the na4 data centre. Similar requests made to ca or eu work without any issues (in the eu region myself) According to our logs, it’s gen

We are currently using DocuSign API integration, where the recipient security setting is configured as None at the envelope level. However, this configuration is being overridden by the account-level authentication settings.While attempting to disable the account-level recipient authentication, we observed that the Save button is disabled, preventing any changes from being applied. 

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>",

We have a requirement to send a PDF document via the API and have the PDF fields converted to tabs for the signers. There can be multiple signers, and we send to the API the signers and the fields that should be mapped to those signers. Using a modified example from the API documentation (below), we include a second recipient and map the `DocusignInitialHere2` field to that one, where the other fields are mapped to recipient ID 1.{ "status": "sent", "emailSubject": "PDF Transform Example 2", "recipients": { "signers": [ { "email": "sally@email.com", "name": "Sally Dough", "recipientId": "1", "tabs": { "initialHereTabs": [ { "tabLabel": "DocusignInitialHere1" }, { "tabLabel": "DocusignInitialHereOptional1", "optional": "true"

Here are some of the latest popular questions that developers asked in the Docusign Community for the month of December 2025.How to send email to signer after request a signature through your app (embedded signing) Summary: The developer is using

I want my redirect URL to be as below“https://advancers-test4-ms.digital.worldpay.io/dashboard/#/overview/portal/callback”When I add this redirect URL and try to save I get below error message“This integration key could not be updated. Please try again in a moment.”Does docusign allow ‘#’ in redirect URL?

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

Not getting consent page for Authorization Code Grant sample, trying with console sample java application. getting com.docusign.click.client.ApiException: Error while requesting server, received a non successful HTTP code 400 with response Body: '{"error":"consent_required"}'

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

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’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?