eSignature API

What scope parameter value should we use for the Authorization Code endpoint to ensure that the refresh token never expires? Currently, we have set the scope to "signature extended," but the refresh token still expires after 30 days. 

Hello, This endpoint is listed on Docusign’s postman workspace, however I see no documentation for it. Is this a supported endpoint? Thank you!

Hello, We have an application using eSignature API for signing our collaborators’ annual assessments. The authentication flow is JWT Grant, and the impersonated user id I’m passing in the configuration file belongs to my user account.I was wondering since we purchased Branding option, is there any way to overwrite the account details of the Envelope Originator / Record tracking holder by the Company name in the Certificate of Completion.Or should I create a general Admin account and pass this user id in the configuration file?Thanks for your help.

We built a C# SDK API that is connected to our customer’s website, and is supposed to call DocuSign’s API. From time to time, the DocuSign API sends back an 500 error without any error message attached (it can happen at any part of the API, from the creation of the enveloppe to the sending of the mails). The API can then be recalled with the exact same infos given the first time and will work properly.The weird part is that when we used our API for tests purposes through swagger (we tested it for a very long time) that kind of 500 error never occured. After searching any kind of possible problem, I’m still completely clueless about where the error might be coming, any kind of idea is appreciated.If any information is needed i’ll do my best to answer asap, thank you in advance. 

We are integrating DocuSign into our application and using the Correction View feature to allow users to edit document fields before sending envelopes. However, we need to prevent users from modifying recipients and documents while still allowing them to edit signature fields and other form fields.We have tested using the CreateLock API with LockType = "edit" and the useScratchPad parameter.When useScratchPad = false, users are unable to modify anything, including document fields. When useScratchPad = true, users can modify document fields, but they can also change recipients and documents, which we need to prevent.Our goal: We want users to have the ability to edit document fields (such as signature and text fields) but prevent them from changing recipients or documents when the Correction View is opened.Is there a way to achieve this through DocuSign’s API or configuration settings? Are there any best practices or recommended workflows to handle this scenario?Thank you for your assis

We are generating contracts for our customers and sending them via DocuSign. However, for one of our customers, the contract wasn’t sent and we are receiving the following error:{'errorCode': 'ENVELOPE_IS_INCOMPLETE', 'message': 'The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying recipients for Envelope ID = 1db6cbd9-cd95-4a42-8c43-41ad321bfe77'}This is the first time we have seen this issue. It has worked fine for all our customers till date. Please let us know what’s the exact issue and how can this be fixed.

 When calling RequestJWTUserToken, an exception is returned:Exception: "We call the token API, but the token creation sometimes results in a non-successful HTTP response code," not always.What could be the issue? We are implementing it as shown below.var _apiClient = new ApiClient(_baseurl);token = _apiClient.RequestJWTUserToken(_integratorKey, _userID, _baseurl, Encoding.UTF8.GetBytes(PrivateKey), 1, Scopes);TokenGeneratedAt = DateTime.Now;

SCENARIOWhen calling: PUT {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/docGenFormFields With the following payload:  "docGenFormFields": [    {      "docGenFormFieldList": [        {          "value": "2024 Carbon",          "name": "Z1TKH6C",          "required": "true"        }      ],      "documentId": "1"    }  ]}Returns the following error response body:{    "errorCode": "INVALID_REQUEST_PARAMETER",    "message": "The request contained at least one invalid parameter. Value for 'documentId' is invalid."}The endpoint is NOT honoring the standard value of 1, which has been the normal approach for other DocuSign REST endpoints.RESEARCH A DocuSign Blog and documentation states to call the GET endpoint first and map the documentId and other properties to the request payload.  Our application currently uses Redis cache to store all Tab information and JSON PATCH value mappers, therefore this GET operation is overly 'expensive'.  Going into DocuSign/ Envelopes/ Drafts

Hi,Currently to get JWT access token we are following these two steps. Step -1: manual action:Currently to get JWT access token we need to manually prepare JWT JSON and here we need to add start time, expire time and need to generate JWT token.Step-2: Rest APIFrom the above generated JWT token we are execute DocuSign API to get the access token “https://account-d.docusign.com/oauth/token?grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<JWT token>. Is there any way so that with the user credentials/data we need to fire only one API to get the access token no need of again manual generation of JWT token. Is there any way to avoid manual action.  

The docusign folder is not stable when I marked the folder complete and moving to the complete status.   The word “COMPLETED” disapears. 

But everytime, when I type : https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id={my_real_client_id}&redirect_uri=https://localhost:8080/callbackDocusign ask the developer account to sign in, otherwise I cannot get the auth code, so I cannot get the access token by the auth code. So it is not a one time thing, everytime, If I want to call some eSign API, I need to login the developer account everytime, why? 

I am attempting to delete/close an account user using the Python SDK. The access token was obtained using the Oauth Authorization Code Grant Flow. I have the user_read and user_write scopes as well. The schemas were imported from the docusign_admin.models and used to craft the response bodyI am declaring my api client and making the request in the following manner. api_client = ApiClient(host="https://api-d.docusign.net/management")api_client.set_default_header( header_name="Authorization", header_value=f"Bearer {access_token}")users_api = UsersApi(api_client=api_client)request_body = DeleteUserIdentityRequest( identities=[ UserIdentityRequest( id=account_id ) ])response = users_api.delete_identities( organization_id, user_id, request_body)I am getting the following response. The reference id has been redactedHTTP response body: b'{"error":"internal_server_error","error_description":"An internal server error occured. If this error continues

Good morning.   As Administrators of our DocuSign account we create templates for users to send for signatures.   Since yesterday we are encountering the below error on all our DEMO templateswhen clicking on USE.  Can anyone help with this? 

I am reaching out to clarify whether it is possible to download signed documents via the DocuSign API without encryption or without copy restrictions, as we need to automate the process of redacting (blacking out) confidential information** in these documents.  Our current workflow involves receiving signed documents from clients, but they appear to be encrypted or restricted, preventing us from copying or modifying the content. Great!We need to automate the redaction of specific sensitive information before distributing the documents internally.  Could you confirm:  1. Is there an option to download the document without encryption or restrictions via the API?2. If encryption is enforced, is there an official way to process and automatically redact specific content while maintaining compliance?3. Are there any recommended best practices, tools, or integrations within DocuSign that support automated redaction of signed PDFs?We are looking for a scalable and compliant solution to integra

Is there anyway or any call we can use to retrieve the envelope ID from signing URL.  An example of signing in urL is: https://demo.docusign.net/Signing/MTRedeem/v1/1946017d-21a5-428e-8912-4028c033b68f?slt=eyJ0eXAiOiJNVCIsImFsZyI6IlJTMjU2Iiwia2lkIjoiNjgxODVmZjEtNGU1MS00Y2U5LWFmMWMtNjg5ODEyMjAzMzE3In0.AQYAAAABAAMABwAA6jrrO0bdSAgAAIpMcl1G3UgYAAEAAAAAAAAAIQDrAgAAeyJUb2tlbklkIjoiYzMyZjkwZDAtOGYyMy00MzZhLWFlNTctN2Q1MDgxZGRkZjAxIiwiRXhwaXJhdGlvbiI6IjIwMjUtMDItMDVUMjM6Mjc6MTIrMDA6MDAiLCJJc3N1ZWRBdCI6IjIwMjUtMDItMDVUMjM6MjI6MTIuMTMwNTM2KzAwOjAwIiwiUmVzb3VyY2VJZCI6IjQzNDU2ZTVhLTNiZjUtNDhlNi1iNGMxLTlhZDNmMjZmNGUxMyIsIlJlc291cmNlcyI6IntcIkVudmVsb3BlSWRcIjpcIjQzNDU2ZTVhLTNiZjUtNDhlNi1iNGMxLTlhZDNmMjZmNGUxM1wiLFwiQWN0b3JVc2VySWRcIjpcIjI5MDE3ZTBmLTkzZWEtNDg2My1hYTg2LTk1ODNhNzA5MmYyNVwiLFwiUmVjaXBpZW50SWRcIjpcIjYxZjg1OGYwLTg3MzgtNDY0OS1iOTkwLWU2MTAzYmU5MjI1ZVwiLFwiRmFrZVF1ZXJ5U3RyaW5nXCI6XCJ0PWQ5ZWEzMWRkLTUxZDYtNDA0MC1hZTExLWUyZmE2MWQyOGY5MFwiLFwiSW50ZWdyYXRvcktleVwiOlwiMTJjMjY3N2QtMjUxMS00OWFjLWE2M2

Hi everyone,I’m reaching out for your help regarding an issue we're experiencing with our DocuSign integration with HighQ. The integration is authorized and generally works, but we encounter problems when sending certain documents for signature.Issue:Some documents trigger the error message:“The server has encountered an issue while processing this request.”This happens regardless of the method we use to send the document.Key Details:There’s no clear pattern linking the problematic documents. Interestingly, if I upload two identical copies of the same document, one may trigger the error while the other sends successfully.Has anyone encountered a similar issue? Are there any specific troubleshooting steps we can take on the DocuSign side to identify the root cause?Thanks in advance for your support!  

I'm participating in a hackathon and building a project using Docusign's ID verification functionality. However, the API only seems to offer phone authentication as an option. Does anyone know why this might be happening and how I can enable other ID verification methods? Any guidance would be greatly appreciated!

Hi DocuSign Community,I'm having trouble sending an envelope via the DocuSign API using a template. I have verified that my template is set up correctly (it works as expected when I create and send an envelope manually from the console). However, when I create an envelope using the API, the envelope is created with a status of "created" (i.e., a draft) rather than "sent".Here’s my setup: Template Details: Template ID: templateId The template contains two recipient roles: one with the role name "provider" and one with "site". The template has required fields and signature tabs already configured. Envelope Definition (API Payload): const envelopeDefinition = { templateId: 'templateId', templateRoles: [ { email: 'provider@ajay.com', name: 'Ajay Parashar', recipientId: '1', routingOrder: '1', roleName: 'provider' // matches template role (case-sensitive) }, { email: 'site1@ajay.com',

I have a Zap setup to pull info/file from Monday.com and then send it via DocuSign. It was working for a while and then all of a sudden over the last 5 days, its stopped and is throwing errors. The latest one I cannot figure out because the sending account is a full admin thus security shouldn't be an issue. I cannot find anywhere in the DocuSign settings for “display” or 'signermustacknowledge'.  Error: Could not create signature request: ACCOUNT_LACKS_PERMISSIONS: This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document Offer of Employment. (Offer of Employment = the Template we use in DocuSign) The error you're encountering indicates that your DocuSign account lacks the necessary permissions to set certain properties, specifically 'display' or 'signermustacknowledge', on the document "Offer of Employment". This typically happens when the account used in the Zap does not have the required permission

Our elastic template has the following settings: However, when we look at the certificate of completion, we see that “Must view” and “Must read” are marked as FALSE:How can we make sure the certificate shows accurate information?

Does DocuSign API support TLS1.3?

Hi There, We are trying to implement a read-only field in a DocuSign webform that is preset when the form URL is sent from our CRM system. However, when the read-only field is preset from a CRM system, it seems that it can’t be configured as a read-only field. The system throws an error at the beginning of the webform and also after you submit it. When you configure a read-only field that is not getting preset, it is working and the value is getting mapped over to the document as expected upon submitting. I have attached some screenshots below of the errors that are getting triggered when the “CaseID” read-only field is getting preset in the first screen as well as the one at the end.    

Hello! The legal entity of my company asked me if we can enable the possibility for the end-user to download the Electronic and signature disclosure (what we see in the screenshot).I did not find something like this in the settings.Does someone know if it is possible?Thanks! 

Hi everyone,We’ve encountered an issue with our DocuSign integration and are hoping someone can share their experience.Here’s the situation:We send documents to a DocuSign envelope and specify the documentId for each document in our API request. The API responds with the same documentId values we set. However, when we view the envelope in the DocuSign UI, the documentId appears to have been reset or renumbered (e.g., starting at 1).Has anyone else faced this issue or something similar? If so, how did you handle it?Thanks in advance for any insights!

Hi everyone,I have a question about integration keys in the developer account.If you create an integration key in a free developer account, you need to promote it to production using your production account to move it to production.What about a paid developer account? Do integration keys created in a paid developer account still require promotion to production, or are they promoted to production by default?