eSignature API

After experiencing a significant outage for my largest user group for DocuSign at my organization, I have been asked by management to confirm DocuSign’s role in third party integrations like SAP Ariba falling out of compliance resulting in a complete rejection of signature tasks.Are these third parties reviewed or tested on a regular schedule? DocuSign was very quick to respond and helpful working with the integration team at SAP and it is working.But the question I was asked by our management team is why this wasn’t identified sooner? If anyone has information or experience in overseeing integrations with DocuSign and some best practices you have adopted in your team, I would be grateful to know it.Thanks!

I’m currently integrating with the DocuSign eSignature REST API (v2.1) and facing an issue when creating envelopes using composite templates.What I’m Trying to Do Create an envelope using a server template The server template already contains one or more documents At runtime, upload multiple additional attachment documents (PDFs) Use compositeTemplates (serverTemplates + inlineTemplates) for this purpose IssueWhen the server template contains documents, I’m unable to upload multiple additional attachment files via composite templates. Additional documents are ignored / not added to the envelope If the server template has no documents, multiple attachments work as expected

Description:I'm unable to authenticate using JWT Grant with my promoted integration key in production. I receive an issuer_not_found error despite having the integration key properly configured.Configuration:Integration key was created in developer account and promoted to production using DocuSign's go-live process Generated new RSA key pair in production User Application setting: Yes Authentication Method: Authorization Code Grant Redirect URI: http://localhost:8080/callbackError:When attempting JWT authentication, I receive:{"error":"invalid_grant","error_description":"issuer_not_found"}Steps Attempted:Tried granting individual consent via multiple authorization URLs (both account.docusign.com and account-d.docusign.com) A

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?

Hi, I work as an Integration Engineer for Unit4 and we’ve developed an integration between our ERPx platform and Docusign for document e-signing. We are now introducing some changes in the integration and we noticed an apparent difference on the signer consent process. We used to have a ‘consent_required’ error (HTTP response status 400) when requesting an OAuth token for the signer and we used it to identify that a given signer hadn’t yet given their consent. Currently it seems that all the signer consent process is dealt exclusively on Docusign UI. Can you please confirm if Docusign introduced any changes at the signer consent processing level? Thanks in advance

Hello, I have an issue concerning the simplified view, it would seem that it doesn’t support HTML, or just partly ?When sending an envelope via docusign API, i am sending HTML through the “emailBlurb”, that html is well rendered on the email side. But it is not on the docusign simplified preview pageOn the email side: On the simplified welcome view, many spaces generated, images doesnt work. 

  Hello DocuSign Community,  We are hitting the ENVELOPE_ALLOWANCE_EXCEEDED error on our Developer Demo account, and the error occurs both via the REST API AND the web interface. This rules out the "API has separate limits from web" explanation mentioned in previous threads.  Environment:  - Account type: Developer Demo (sandbox)  - Authorization server: account-d.docusign.com  - API base path: demo.docusign.net/restapi  - Integration method: REST API via official PHP SDK (docusign/esign-client v8.6)  - Error code: ENVELOPE_ALLOWANCE_EXCEEDED  - Error message: "The envelope allowance for the account has been exceeded"  Critical detail:  The same error appears when trying to send envelopes through:  - ✗ REST API calls  - ✗ Web interface (appdemo.docusign.com)  This suggests either a system-wide bug or an account-level issue, not an API-specific quota.  Su

I am working on converting a bunch of hand written forms to DocuSign.  Our system uses the DocuSign API and connects to it using the C# .NET SDK.This works well for most fields and anchor tags but, recently, we have started adding fields like checkboxes and radio buttons.  However, it appears that radio buttons do not have any sort of measurement associated with them in their class (no scale, no width/height, etc.).  The only size related field I can find is fontsize, but changing that does not appear to change the size of the radio button.Is there any way to change the size of a radio button for a form submitted through the DocuSign API?

Hi, I’ve created a Connect configuration with the following settings:Trigger Events > Envelope Events > Envelope Signed/Completed!-->Include Data:Documents Attachments Document Fields!-->But when the contract signing process is complete, I receive a payload into my webkook with the following structure:!-->​​​​​​​{ event: 'envelope-completed', envelopeId: '68ce2953-4fa5-8d2f-8094-cde7fc130d3b', status: 'completed', documents: [ { documentId: '1', name: 'InvestmentContract_50b40cd2-f529-4584-892d-926b40447143' }, { documentId: 'certificate', name: 'Summary' } ], completedDateTime: '2026-01-13T16:15:14.87Z', createdDateTime: '2026-01-13T16:13:53.8Z'}The PDFBytes is not included in the payload. I need to get the signed PDF and save it in a safe storag

I’m trying to use the simple send.sig.request script to send signature requests, but it is not at all clear how to get the access token. The JWT seems like overkill as I don’t need to impersonate everyone, just access as a single user, but I don’t want to deal with popping up web pages and whatnot for consent - it just needs to send the request. The instructions say to setup a redirect uri, but it’s not at all clear what the uri is supposed to do when whatever redirects to it…Thanks for any help...

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"

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?

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?

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