General

We’ve just published a brand new developer use case focused on Compliance and Identity Verification, and it’s packed with ways to help you build secure, compliant verification flows right into your applications.Whether you work in financial services, insurance, or any industry that requires strong identity checks, this guide walks you through Docusign tools and APIs you can use to:Verify signer identity with multiple authentication options   Meet industry regulations while keeping the user experience smooth   Integrate verification directly into your signing workflows  Check it out here: Compliance & Identity Verification Use Case What kinds of solutions are you building for this use case? We would love to hear your thoughts. Share your feedback in the comments so we can continue making these resources even better for you! 

So I have seen a few people that have the same issue. I have tried the best answer to open support. Now I get this reply But I still can’t access developer account. Clicking on the button just redirect me to maestro page. i have tried to login with my email, but I can’t. I tried to change my password but it said that I don’t have any account.What should I do from this? 

Curious about creating a smooth, in-app signing experience with Docusign? We recently hosted an async Ask Me Anything (AMA) with ​@paige.rossi, Lead Developer Advocate at Docusign, where developers submitted their questions on embedding eSignature using the Docusign API.Below is a recap of the top questions and their answers.What’s the difference between embedded signing and embedded sending?Answer: These two terms sound similar but serve different purposes in your Docusign integration. Embedded signing lets signers complete documents within your app or website, instead of navigating away to check their email. It’s all about making the signing experience faster and smoother for your users. Embedded sending, on the other hand, is for the senders. It allows you to embed the Docusign sending experience into your own app or portal, so users can create and send envelopes without going to Docusign.com. Why does this matter?By embedding either (or both), you streamline the agreement workflo

What’s the difference between embedded signing and embedded sending?

Hi DocuSign Team,I'm trying to create a developer account, but the sign-up process doesn’t complete and no error message is shown.Steps I’ve already tried: Used different devices and browsers Switched to different networks Cleared browser cache and cookies Despite these attempts, I’m still unable to proceed. Could you please assist me with this issue? Thank you, 

Hello,I’m trying to create a DocuSign developer sandbox account, but I'm unable to complete the process. The browser seems to hang during the registration, and nothing progresses beyond a certain point.When I inspect the browser console, I see the following errors:_app-573f798ac9f1a077.js:1 Logger failed attempting to post telemetry data to server Error: Error sending data to Kazmon. Status = 0 at W.n.onerror (_app-573f798ac9f1a077.js:1:221602)   telemetry-s.docusign.net/api/v1/TelemetryWrapper:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT Could you please assist me in resolving this issue? 

Here are some of the latest popular questions that developers asked on Docusign Community in the month of July 2025. Thread: Is there a way to realign transformed PDF fields based on original PDF alignment?https://community.docusign.com/esignature-api-63/is-there-a-way-to-re-align-transformed-pdf-fields-based-on-original-pdf-alignment-24757Summary: The developer is using PDF form field transformation to convert PDF AcroForm fields into Docusign tabs. They’ve noticed that the text in these new tabs is always left-aligned, while some of the tabs on the original PDF were center-aligned. They want to know if it’s possible to realign these new tabs to match the alignment in the original document.Answer: Docusign eSignature always left-aligns all tabs and fields. Currently, there's no option to change their alignment to right or center, whether they were added manually or transformed. If you want to change where the text in a tab appears, you would need to reposition the tab itself. Thread:

We have been unable to sign up for a developer account the past 2 days. When we click on the “Get Started” button after filling out all required fields, the button flashes for a moment, but then no other response from the page.We have tried:Using a different email addressUsing a different browser (chrome, Edge)Clearing cache and cookiesUsing Incognito modeTrying to sign up on a mobile phone on both wifi and cellular networkI notice a request outgoing in the network tab:POST https://protect-d.docusign.net/api/2.0/approvals?ik=89220935-c225-4fcf-9eb7-547598b97a7bPayload{"state":"<JWT_HERE>","action":"ActionNewAccountSignup","challenge":"ActionRuleEngine","features":{"firstname":"Evan","lastname":"Payne","email":"evan@<my_email_address>.com","fingerprintHash":"4a7c65ea490b114675f8ee664634ebb3","sessionId":"9249bd95-7fc3-44c7-88e2-8b6a83a7cc8c"}}Response:{    "id": "42e25fda-3e40-4cc8-972b-45c20c641be2",    "done": false,    "state": "<JWT>",    "challenges": [        "Ac

I can’t create a Docusign developer account - when filling out the form and submitting, the subsequent “clock” just spins and spins forever.  Have tried two computers and two different browsers.    I’ve seen some other mentions of this issue but no resolution. help?The api response like thie  {"id": "abc","done": false,"state": "abc","challenges": ["ActionRuleEngine"],"version": 1}

🎉 Big news from the Docusign developer team—we’re honored to be named a 2025 Postman Champion Award winner! This recognition means a lot to us. Over the past year, we’ve focused on making our APIs easier to work with, more reliable at scale, and better supported with tooling and documentation. Whether you're embedding Docusign into your workflows or building complex integrations, we aim to make that experience as smooth and developer-friendly as possible. I had a fantastic time participating in this year’s POST/CON. The event was filled with in-depth technical sessions, and two topics particularly stood out: scaling APIs for performance and reliability, and fostering strong, authentic developer relations by providing developers with interactive content and tools built from developer feedback. These are areas the Developer Advocacy team deeply cares about, and observing how other teams tackle them has sparked many ideas that we're eager to explore further. A huge thank you to the Postm

  Ever wondered whether vibe coding has a place in building Docusign integrations? I experimented with the Docusign Developer AI Assistant for VS Code to find out whether I could vibe code my way to an embedded signing session and I was pretty surprised with the results.Want to try it out yourself? Learn more about the Docusign Developer AI Assistant and let us know your thoughts! https://developers.docusign.com/tools/visual-studio-code-extension/

The July 2025 Developer Newsletter is out! In this month’s issue, we highlight the Connected Fields API. This API lets your Docusign integration poll your Docusign account for installed extensions that can verify data so you can connect those extensions to fields in your Docusign envelopes, thereby enabling on-the-fly data verification for those fields. The Connected Fields API works with prebuilt Docusign data verification types as well as custom types defined using Connected Fields extension apps, so you can build an extension to verify any data you like against any system of record you choose, then use that data verification directly in your integration!More July Newsletter highlights:Paige Rossi shows you how to integrate Stripe payments processing into your Maestro workflows with the Stripe extension app. See how to auto-read data into your workflows with data IO extension apps. Hold the date for Docusign Discover! Our premier developer conference is coming to San Francisco this O

Here are some of the latest popular questions that developers asked on Docusign Community in the month of June 2025.Thread: Hide finish later option popup when it appears on clicking of "Finish Later"https://community.docusign.com/esignature-api-63/hide-finish-later-option-popup-when-it-appear-on-clicking-of-finish-later-24382Summary: This developer wants to hide the popup that appears (as seen in the screenshot below) when a user clicks Finish Later while signing a document with Docusign.Answer: This confirmation popup is a standard part of the Docusign signing process and can’t be disabled. However, it is possible to disable the Finish Later button entirely if you don’t want to give users that option. To do that, follow the steps below:Access Branding Settings: Navigate to the Brands section within Docusign eSignature Admin. Edit the Resource File: For the specific brand being used in the signing session, download the "Signing Resource File." This is an XML file that controls various

I’m trying to request a phone call and it’s not working. I need to talk to support! I will not be renewing if it’s this hard to get support.

For the past few days me and my team have been trying to create a free Docusign developer account but every time we click the “Get Started” button, nothing happens. We have tried on multiple devices (laptop, desktop, phone) and in different browsers but we are all getting the same result. There are no errors displayed, the “Get Started” button just greys out for a second then nothing happens. Can someone please help in resolving this?

Here are some of the latest popular questions that developers asked on Docusign Community in the month of May 2025.Thread: Unable to Restrict Editing in Sender View Despite Setting All Configuration Flags (disableDocumentEdit, etc.)https://community.docusign.com/esignature-api-63/unable-to-restrict-editing-in-sender-view-despite-setting-all-configuration-flags-disabledocumentedit-etc-23880Summary: The developer is embedding the Sender view of an envelope into their application. They want the sender to be able to add tabs to the document, but they don’t want to give them permission to edit the document, edit recipients on the envelope, or change the envelope routing. They have tried passing various parameters to the EnvelopeViews: createSender endpoint, but they aren’t able to restrict the sender’s permissions in the way that they want to.Answer: The sender is seeing these options to edit the document and recipients because they are seeing the Prepare page. If you want to bypass the Pre

Hi! I just published a new YouTube tutorial showing how Docusign AI helps accelerate contract reviews, identify risky terms, and even suggest clause edits—all directly inside Word. You’ll learn how to:Run AI-powered playbook checks on contracts using Docusign AI assisted review for Docusign CLM Search contracts for clauses using AI in Docusign eSignature How to use Docusign Navigator to resurface agreement information using AI in Docusign eSignatureWatch the full video here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Maestro is featured in The New Stack! 🗞 Check out the step-by-step guide to learn how developers and business users can leverage Docusign Maestro to build scalable, custom agreement workflows. 💡 We want to hear from you! Have you built any cool or unique workflows recently?https://thenewstack.io/build-api-driven-custom-agreement-workflows-with-docusign-maestro/

Hi everyone!I am evaluating if we want to use docusign for our non profit org. We are using slack and want to utilize the workflow builder of slack for which DocuSign steps are available.I have created a envelope template in docusign and want to send it via Slack workflow. In the custom workflow step in slack I am able to select my DocuSign account and the template created. However the step is not able to load the roles that need to sign into the workflow step:Roles can’t be loaded from docusignMaybe thats a temporary bug or I have done something wrong?Is this working for anyone or is this bug known?If this is not working we will probably not go with docusign even thougth everything else is working just fine. Thanks in advance!

Hi! I just published a new YouTube tutorial explaining how Docusign CLM streamlines your entire contract lifecycle—from creation and approval to negotiation and signature. You’ll learn how to:Automate contract generation using templates and data Collaborate and redline documents in one platform Track contract status and obligations with built-in reportingWatch the full video here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

I can't create a developer account now. I clicked the button to create a developer account, but nothing happened.I tried various methods based on existing posts, but I couldn't create a developer account.Is there any solution?

Hi everyone. Im setting up a Zap in Zapier that creates a draft envelope on docusign from a template.The template was created with pre-fill fields (signer fields) assigned to the Customer Role, for example:The displayed label has “customerName” as ToolTip and Data Label When i configure the step in Zapier i see the fields and load them with information as part of the data sent to docusign. When setting “Recipient Role” to Customer i find the created fieldThis is what i see as part of “Data in” in the testing step (another field created the same way) Unfortunately, when i execute this step, i’m able to view on Docusign the created DRAFT envelope using the template, but i don’t see on the documents the information i sent to prefill the fields (there’s a blank space). I tried changing the Zaps action from “Create draft request signature” to “Send envelope using a template”, and also sending the Draft envelope after its creation. If i change the action to “Send envelope usign a template”,

Earlier this year, 1,400+ developers participated in our Docusign Hackathon: Unlocked! Hear directly from the hackathon winners as they showcase their solutions built with Docusign for Developers, our suite of APIs and tools.  Thanks to all who participated! We can’t wait to see what other innovative solutions you all come up with.