Developer

Hi Team,I have configured the webhook feature in my demo account and include OAuth for integration and security, the webhook attempts to call the API when an event is triggered. However, I got  an error message in the log. Here is the error message: Error: https://dev.api.genpt.com/catalog/debi-service/debi/documentSign/status :: Error - HTTP call to OAuth authorization server failed: HTTP status code = 401, OAuth response = {"fault":{"faultstring":"Invalid access token","detail":{"errorcode":"oauth.v2.InvalidAccessToken"}}}; My question is: What details can I expect in the webhook API call? What should I configure in my service to handle this properly? Can anyone help us with this? Regards,Adarsh

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

When trying to get a signature or sign a document from a SharePoint library, Docusign just spins forever.  I have tried using Chrome and Edge browsers.  I have tried on different devices and different login accounts and still are having the same results.

Hey everyone,I’m working on Next.js application and I want to create contract there and also i want edit them on my website also want to know about there status so can you guys please tell me step by step guide how can I do this?

Hello,I am trying to generate a flow in Power Automate that is triggered off when a Docusign envelope changes, however, am running into the following error code: The request failed. Response content: '{"errorCode":"USER_NOT_ACCOUNT_ADMIN","message":" User is not an account administrator."}'.After researching this, it’s my understanding that a DocuSign administrator must enable Docusign Connect before a non-administrator can use the Docusign for Power Automate connector to run a flow when an envelope status changes. I have met with the Docusign administrator for my account and we have tried to follow the instructions linked below but do not have a button for “Enable Connect” in the top righthand corner. We do have the ability to click on the “Add Configuration” button, however, upon trying to add a configuration we receive receive another error message stating that Docusign “needs permission to access resource in your organization that only an admin can grant” (s

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? 

Hi Team,Whether it is possible to change the payload format of our webhook from XML to JSON. Our account is an enterprise demo account, and we are currently unable to locate the configuration option within our webhook settings to make this change.Could you please confirm if this feature is available for enterprise accounts and provide guidance on how to update the payload format if it is?Regards,Adarsh

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_se

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? 

Hi! I just published a new YouTube video breaking down the key differences between Docusign Web Forms and PowerForms so you can choose the best option for your workflow.You’ll learn:When to use Web Forms vs Powerforms depending on your use case. A demo of how the same document looks and feels in Web Forms vs Powerforms. Key limitations and advantages of each form type.Find out which solution fits your needs best! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?

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

Is there anyway or any call we can use to retrieve the envelope ID from signing URL.  An example of signing in urL is: 

When paging for a response on an instance ID well a user is working on the form, there is only INITATED and SUBMITTED, Why isn’t there a way to see if they are filling in the form under INPROGRESS. So we can see if the user left mid form.data: {    id: '',    clientUserId: 'guest_user',    formId: '',    accountId: '',    tags: [],    status: 'INITIATED',    instanceMetadata: {      expirationDateTime: '2026-03-29T08:24:26.078Z',      createdDateTime: '2025-02-05T16:24:26.078Z',      createdBy: [Object],      lastModifiedDateTime: '2025-02-05T16:24:26.078Z',      lastModifiedBy: [Object]    },    envelopes: [],    formValues: {      Language_Difficulty: [],      Legal_Guardian_Emergency_Contact: [],      Primary_Insurance_Coverage: [],      Secondary_Insurance_Coverage: [],      Contact_Preference: []    }  }}

Here are some useful links for JavaScript resources when developing with Docusign:SDKs:The following SDKs are open sources and each of their npm packages can be found on npm.orghttps://github.com/docusign/docusign-esign-node-client https://github.com/docusign/docusign-click-node-client https://github.com/docusign/docusign-webforms-node-client https://github.com/docusign/docusign-rooms-node-client

Hello,I’m encountering an issue while trying to create a developer account for the email xxx@ABC.com (not the actual email). When I visit the DocuSign Developer Sandbox page and click the “Get Started” button, nothing happens — the page doesn't load or display anything.I’ve already successfully created an account for yyy@ABC.com, and it worked fine. Could you clarify if there are any specific requirements for the email address in order to proceed?Additionally, upon inspecting the page (F12), I can see a request being sent, and here is the

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! 

Learn how you can help shape the future of Docusign for Developers with our new public roadmap, see how LaborEdge is revolutionizing healthcare staffing compliance with Docusign, explore upcoming events, expert dev tips and more!Check it out. https://developers.docusign.com/newsletter/2025/february/  

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! I just published a new YouTube video explaining how to use Docusign approve and decline buttons to create efficient approval workflows.You’ll learn how to:Add approve/decline buttons to templates to create approval processes. Configure signing orders so documents are routed correctly. Workarounds if you don’t want to waste your envelopes with these buttons!Transform your approval processes with these techniques! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusig

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@a

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 'signermustac

Hello,I tried to delete personal data at the development environment. Given account has been closed for few days, using following request:curl --request POST 'https://api-d.docusign.net/management/v2/data_redaction/accounts/8d2d3601-24f5-xxx-xxx-d9acac3d26d2/user' --header 'Authorization:AzMzE3In0....' --header 'Content-Type: application/json' --data-raw '{ "user_id": "91585e2f-xxxx-4a44-bf16-xxxxxxxxxxxxx"}'but i get internal error response:{"error":"internal_server_error","reference_id":"dbb84fb9-3bed-40fd-b708-63112cc15e2b"}Is this functionality temporarily unavailable? Do I need to fulfill any other prerequisites besides closing account?

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?

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of January 2025. To make sure we see your questions on Stack Overflow, use the tag docusignapi.Thread: Send one carbon copy (CC) in bulk requesthttps://community.docusign.com/esignature-api-63/send-one-carbon-copy-cc-in-bulk-request-22345Summary:  The developer is bulk sending envelopes through the eSignature REST API. Each of the envelopes has a different signer recipient, but they want to add a

Does DocuSign API support TLS1.3?