Skip to main content
arrow-left Back to Docusign.com

Developer

Ask questions, share knowledge, and get help from other developers as well as our support team.

  • 1,161 Topics
  • 12 Replies
1161 Topics
A
Newcomer
AdamQNewcomer
asked in eSignature API
Document Generation SAP with Docusign

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

150
A
Newcomer
paige.rossi
Docusign Employee
paige.rossiDocusign Employee
posted in General
Developers, help us improve our email testing-management experience

📢 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. 

190
paige.rossi
Docusign Employee
paige.rossi
Docusign Employee
paige.rossiDocusign Employee
posted in General
Trending Topics: Latest from our forums (August 2025)

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

250
paige.rossi
Docusign Employee
T
Newcomer
thisiskarthikrajNewcomer
asked in Docusign Connect
Unable to Receive Webhooks on Development Server – TLS/SSL Issue

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.

251
T
Newcomer
R
Newcomer
renderNewcomer
asked in eSignature API
I received the envelopeSenderView and templateEditView URLs, but I cannot access them.

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?  

180
R
Newcomer
O
Newcomer
OliverbackNewcomer
asked in Docusign Connect
x-docusign-signature headers not included in the eventnotification webhook request

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?

1481
R
Newcomer
C
Newcomer
Carlos SilvaNewcomer
posted in eSignature API
Integrating RD Station CRM with DocuSign for automated contract sending

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!

140
C
Newcomer
B
Newcomer
bryankoulmanNewcomer
asked in eSignature API
Is it necessary to update BaseUri for Rest EndPoints because of the move to Azure

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.

291
G
Docusign Employee
G
Newcomer
ganesh.sthaNewcomer
asked in Maestro API
How to Preselect Radio Buttons, Checkboxes, Dropdowns, and Phone Fields via API trigger_inputs in Maestro Webforms?

Hello everyone,We’re currently working on passing values from our website into a DocuSign Maestro webform via API trigger_inputs, and while we’ve had success with text fields and date fields, we’re running into challenges with other field types.Specifically, we want to pre-select a radio button option so that when the webform loads, the correct option is already chosen. For example: Gender field (radio buttons): Options are Male, Female, Others. We’d like to pre-select Male. We suspect this challenge may apply similarly to dropdowns, checkboxes, and phone number fields as well.Has anyone implemented this successfully? Could you please share examples of the correct variable types or payload structure required to map these field types (radio buttons, checkboxes, dropdowns, phone)?I’ve attached screenshots for reference. Any guidance or working examples would be greatly appreciated!Thanks in advance.

231
Leandro.Reis
Docusign Employee
K
Newcomer
kristipatisNewcomer
asked in eSignature API
How can we set the status to 'Completed' using the REST API?

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?

231
J
Docusign Employee
P
Newcomer
Pepco demoNewcomer
asked in eSignature API
When trying to sent a file for signing form Coupa getting the error

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.  

151
I
Docusign Employee
E
Newcomer
EponaNewcomer
asked in eSignature API
Request-Id not allowed on options of endpoint accounts/${accountId}/envelopes/

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.

232
T
Docusign Employee
A
Newcomer
aminagallNewcomer
asked in eSignature API
Create an Envelope - Email Body API Character Limit

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

301
T
Docusign Employee
E
Newcomer
eakiraNewcomer
asked in eSignature API
How do I send an ICP Brazil certificate via the API?

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

211
I
Docusign Employee
B
Newcomer
Bertrand CHENINNewcomer
asked in eSignature API
Link to DS signed document doesn't appear in my app

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  

201
karan.kaushik
Docusign Employee
T
Newcomer
TatianaNewcomer
asked in eSignature API
DocuSign Sandbox: Envelopes Created Successfully, but Emails Not Delivered to Recipients

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.

886
T
Newcomer
T
Newcomer
tharunmullapudiNewcomer
asked in Docusign Connect
DocuSign Dropbox Integration Error: AuthenticateFailed when accessing documents

 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.

100
T
Newcomer
C
New Voice
cweeksNew Voice
asked in eSignature API
Webhook Expired Events

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?

421
JohnSantos
Valued Contributor
C
Docusign Employee
Community UserLegacy User
asked in General
How do I access my sandbox?

How do I access my sandbox?

55972
P
Newcomer
N
Newcomer
nasNewcomer
posted in eSignature API
JWT Error: "DocuSign rejects JWT signature - public/private key mismatch or missing consent"

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 🙏 

200
N
Newcomer
K
New Voice
Kat0120
posted in eSignature API
I'm learning how to use SOAP UI. Does Docusign provide a WSDL (Web Service Description Language) file(s)?

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

242
K
New Voice
leah.breen
Community Admin
leah.breenLeah Breen
published in General
Help pick the topic for the September Developer Async AMA

Our next Developer Async Ask Me Anything (AMA) is coming up in September—and we want you to decide what we cover. Cast your vote in the poll below to let us know which topic you’d find most valuable.If you’ve got another idea for a future AMA topic, share it in the comments. Your input helps us make these AMAs as useful and relevant as possible.If you missed the last AMA on embedded signing & sending, you can check it out here. 

12080
leah.breen
Community Admin
paige.rossi
Docusign Employee
paige.rossiDocusign Employee
posted in General
Building Integrations With AI Assistance That Go Beyond Vibes

💻 While vibe coding is possible with our Docusign Developer AI Assistant, it’s important to be smart about incorporating vibe coding into production projects. Over at The New Stack, I wrote about how the Developer AI Assistant for VS Code can be used to build integrations with trusted AI assistance that goes beyond just vibes.  💡 Check out the post and let me know what you think! Have you tried vibe coding with Docusign yet? Any tips and tricks for others who want to give vibe coding a try responsibly?

160
paige.rossi
Docusign Employee
leah.breen
Community Admin
leah.breenLeah Breen
published in General
Here’s what’s changing behind the scenes in eSign
Here’s what’s changing behind the scenes in eSign

To better support your needs and stay ahead of what’s next, Docusign eSignature is moving to the cloud—bringing more agility, security, and speed to every transaction.Over the next several months, all Docusign eSignature transactions will move to Microsoft Azure. This shift is aimed at giving you stronger security, better performance, and faster innovation.This update applies to all production accounts, except those hosted on AU, CA, and JP1 servers, which already operate on Azure. This also applies to all demo accounts. The transition will begin in September 2025 for demo accounts and roll out to production accounts from November 2025 to May 2026.Migrating to Microsoft Azure is a key infrastructure update that allows us to better serve you and your customers.✨ Key takeaways: Robust security: Our move to Azure ensures your current security standards remain strong — and unlocks the path to deliver additional security enhancements in the future. More agility and resilience: A cloud-nat

1110
leah.breen
Community Admin
J
Newcomer
JanSNewcomer
asked in eSignature API
EnvelopeTemplates:list returns only first document of the template for envelopes created using composite templates

Hi,I'm encountering an issue when using the compositeTemplates feature to create an envelope from a template that contains multiple documents.When retrieving this template via the EnvelopeTemplates:list endpoint, only the first document is returned in the response - the remaining documents are omitted.This behavior is different from what I observe in the DocuSign web UI. If I simulate the same process (e.g., by creating an empty envelope and applying the templates), all documents are present as expected.Is this a known limitation of the EnvelopeTemplates:list API? Or am I missing something in the way the template is structured or retrieved? Thanks in advance for any help or clarification.

643
J
Newcomer

Badge winners

  • 1st Question Posted
    RWebsterhas earned the badge 1st Question Posted
  • 1st Question Posted
    smartalec1494has earned the badge 1st Question Posted
  • 1st Question Posted
    ValDShas earned the badge 1st Question Posted
  • 1st Question Posted
    TrevorGreenhas earned the badge 1st Question Posted
  • 1st Reply Posted
    niani.byrdhas earned the badge 1st Reply Posted
Show All Badges
Code of Conduct

Docusign Community

Code of Conduct