Developer

In the Developer account, templates created through the Template Builder include a tab field called Data Label.However, in the Production environment, the Data Label field is not available in the Template Builder.I developed a program that populates template tabs fields using the DocuSign eSignature API. Data Label used as a key to map values from the API. Production Account Developer Account 

I’m currently working on a project that uses the DocuSign API to automate envelope creation and integrate with other systems through webhooks. At the moment, I’m building and testing everything in a developer sandbox account. From what I understand, once we are ready to deploy, the developer account will go through the Go Live process and be promoted to a production account. My question is:Does the production account created from Go Live also have access to the 30-day free trial plan, or would it require moving directly onto a paid plan? I want to confirm this before we finalize our deployment plan. Thanks in advance for any clarification!

I have a user attempting to create envelopes via power automate. When they do so, the power automate flow returns the following error when using the CreateEnvelope action: { "errorCode": "USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT", "message": "The specified User is not a member of the specified Account."}They can run the flow, which requires a successful sign in to DocuSign.They can create and send envelopes via the DocuSign web app.  The user is a user in our DocuSign tenant, and DocuSign SSO group, and seemingly identical users are not encountering the error. Things I’ve tried to troubleshoot:re-created the user’s docusign account with highest privs deleted all previously created power automate connections associated with this user in power automate  re-created the connection used when signing into the flowAny assistance would be appreciated.

I am currently integrating DocuSign with Oracle Integration (OIC). At present, I am using the following REST API to generate a bearer token:<BASE_URL>/oauth/token?grant_type=refresh_token&client_id=[client_id]&client_secret=[client_secret]&refresh_token=[refresh_token] This works fine as long as my refresh token is valid. However, when the refresh token itself expires, I currently use Postman to manually log in to my DocuSign account, provide consent, and generate a new refresh token.This approach is not ideal since it introduces manual intervention and breaks the automation.My Questions: What is the best way to avoid this manual Postman step? Is there a way to fully automate the token generation process in Oracle Integration so that I don’t have to worry about refresh token expiry? Should I switch to the JWT Grant flow for this type of server-to-server integration? Any guidance on the recommended approach would be greatly appreciated.Thanks in advance! 

Hi all, I have a question related to SAP Document Generation.When we generate a document via sap and select -Allow Digital Signature. The document will be signed via DocuSign. Do you know if it is possible to generate a document via SAP Document Generation and sign the document using DocuSign (QES) Qualified electronic signature addon? Some of our markets require QES. Any help would be appreciated. ThanksAdam

📢 Hello Developers! Our team is working on improving the email testing-management experience. To make sure we're solving the right problems, we'd love to get your input. Let us know in the comments, what type of email do you use for testing? Your work email, a personal email, or a dedicated fake email created for testing?Between the two options in the poll, let us know which you prefer and leave additional thoughts in the comments. 

Here are some of the latest popular questions that developers asked on StackOverflow and Docusign Community in the month of August 2025.Thread: Is it necessary to update BaseUri for Rest EndPoints because of the move to Azurehttps://community.docusign.com/esignature-api-63/it-it-necessary-to-update-baseuri-for-rest-endpoints-because-of-the-move-to-azure-25268Summary: In light of the announcement that Docusign eSignature transactions are moving to Microsoft Azure, this developer is wondering if they need to make any changes to the base URI of the endpoints that they’re using.Answer: With the move to Azure, the base URI is not changing. The only change that developers may need to make is that, if your organization restricts inbound network connections and allow-lists specific Docusign IP addresses, you’ll need to update your allow-list to include all current Docusign IP ranges. IP allow-listing: Make sure your allow-list includes all current Docusign IP ranges from our Trust Center by De

I am unable to receive webhooks on my development server from DocuSign.When DocuSign tries to send the webhook, I see the following error:Error - The request was aborted: Could not create SSL/TLS secure channel.

We are integrating with DocuSign using the Python SDK.We implemented retrieving the envelope sender view URL via the API so it can be edited within an iframe.The template editing screen was implemented in the same manner.The view URL functions correctly when accessing the application under development via localhost or 127.0.0.1. However, accessing it via an internal IP like 192.1.x.x or an external IP results in a 401 error.How can I make the view screen appear in an iframe when accessing via an internal IP like 192.1.x.x?  

Im using envelope level connect keys and setting the includeHMAC to true in the eventNotification object of the envelope.This works and the x-docusign-signature headers are being sent as part of the call. We are using this with a client and initially the x-docusign-signature headers were coming through. But the x-docusign-signature headers are no longer present. Ive checked with our client and the connect key still exists for that account.Is there any reason or a configuration setting that would stop the headers coming through?

Hi everyone,I’m trying to create an integration between RD Station CRM and DocuSign to automate the process of sending contracts to my clients. The idea is that when a deal reaches a specific stage in the CRM (e.g., “Proposal”), the system should automatically send the contract for signature via DocuSign and then update the deal in RD with the contract status and signing link.So far, I’ve found that: RD Station CRM provides a REST API to manage deals and contacts. DocuSign also provides an API to create and send envelopes for signature. I haven’t found any native integration between the two. My questions are: Has anyone implemented something similar using direct API integration or via tools like n8n / Zapier / Make? What’s the best approach to automatically update the contract status back in RD Station CRM? Are there any common pitfalls or limitations I should be aware of when building this integration? Thanks in advance for any help!

Hello,       I have written an application that makes RestAPI calls to a base URI (https://na1.docusign.net/restapi)     I do have clients that need to whitelist all URLs from their servers.     For the example above (na1.docusign.net/restapi), I will now need to have the client whitelist na1-b.docusign.net     My question is:               Does the base URI for the RestAPI calls remain na1.docusign.net.      I assume that the base URI remains the same (na1.docusign.net/restapi).      Thanks.

Hi,I have implemented the following using the REST API: Created a templated envelope with two recipients. The first recipient is required to sign, so I used the embedded signing focus view on the frontend and completed the process. Updated some additional tab details for the second recipient in the same envelope using the REST API. The second recipient does not need to sign. Now, how can I update the envelope status to ‘Completed’ using the REST API and send it to both recipients?

I have crated a Sandbox Docusign account for our Client using a Gmail test account. I have successfully connected the Sandbox Docusign account with Coupa test instance. Although, when I try to send the document for e-signing I am always getting the error “Unable to send selected attachment for signing. Please retry by clicking on Send button”. Could you please suggest if this error is due to any incomplete configuration? As I can see the Connect webhook is already active.  

I am implementing a integration with my browser application and Docusign. For this I have to call the endpoint from the browser and for this I am using the default fetch command from node. This command results in a unstoppable options command which includes a unstoppable Request-Id header. I have tried using a client instead of the browser which results in everything working perfectly. I have implemented the authentication but this is the final hurdle.Officially Request-Id is not specified in the HTTP schema but a lot of browsers do send this when cross origin querying endpoints. What do you suggest I change or is there a chance the Docusign api will support this?For completeness the error in the console: Access to fetch at 'https://demo.docusign.net/restapi/v2.1/accounts/${accountId}/envelopes/' from origin 'http://localhost:8080' has been blocked by CORS policy: Request header field request-id is not allowed by Access-Control-Allow-Headers in preflight response.

hello :) I’m using power automate to create envelopes.The API doc states the email body has a 10,000 character limit. When i send an email body over 1,500 characters I get a generic 404 response. The only difference in the call seems to be the email body. Over 1,500 chars, bad, under 1,500 chars, good. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/><title>404 - File or directory not found.</title><style type="text/css"><!--body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;}h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"treb

How do I send an ICP Brazil certificate via the API?I'm using PHP with Laravel.And using your Git repo.https://github.com/docusign/docusign-esign-php-laravel/tree/main

DocuSign integration in my app allows to find the DS link in a specific field of my database. This DS link allows me to get the signed document on my server. 90% of the time it works. 10% of the time the DS link does not appear in the field where it is supposed to be.I can not establish any common properties or specificities in between all names for which the DS link does not appear.Thank you if you can help  

Hi,I’m working with a sandbox to integrate docusign in my web app. My service is able to create the envelopes and, checking on the docusign developer page all appear to work properly. The problem is that the mail never get to the recipients.

 I am  trying to access and send documents through the Dropbox integration with DocuSign, but we keep encountering the following error:https://na4.docusign.net/plugins/api/RedirectExternalDocService.aspx?status=fail&error=AuthenticateFailed  Details: Integration: DocuSign connected with Dropbox SharePoint Site URL:  App Version: 4.0.3 Server Version: 4.0.0.6 Status: Dropbox is connected successfully, but when we try to prepare an envelope with a Dropbox file, the authentication fails. Has anyone experienced this issue before? How can we fix this AuthenticateFailed error?Any guidance will be highly appreciated.

When a document gets voided due to the expiration date, I assume the webhook sends out an event to the listener telling the doc has been voided, but I am not receiving any voided event. I am receiving all the other events just not any voided or expired events. Can someone tell me how to configure the voided\canceled\expired documents?

How do I access my sandbox?

Hello everyone,I’m currently working on an integration with the DocuSign API using JWT authentication. When I try to call the API, I get the following error:❌ [send-docusign-signature] DocuSign rejects JWT signature - public/private key mismatch or missing consentHere’s what I’ve already checked: The private key in my code is the one generated when I created the app. The public key has been uploaded correctly in my DocuSign integration settings. My Integration Key (client_id) is correct. I suspect the issue might either be a key mismatch or the fact that the user consent has not yet been granted. My questions are: How can I confirm whether the issue is due to missing user consent versus a key mismatch? What is the exact procedure to generate the consent URL and have the user approve it in the demo/sandbox environment? Are there best practices for managing the lifecycle of keys (rotation, updates) to avoid this type of error? Thanks a lot for your help 🙏 

I'm learning how to use SOAP UI. Does Docusign provide a WSDL (Web Service Description Language) file or some documentation for REST API?