Developer

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 am working on a project for a contract management system. The data resides on a SQL Server backend. I need to create Docusign Templates for many state-specific and generic contract documents. I am familiar with Salesforce merge fields, but I need the same capability for this project. I understand I may need to build a custom connector in order to connect to SQL Server databases. I need help or guidance on how to go about this.

I include our CFO as a signer/guarantor on all the agreement envelopes I send to new clients. All of a sudden, he no longer receives the envelopes to sign.  Nothing's changed.  I need support 

We are currently using the DateSignedTab for the embedded signing. However, we are located in Kuala Lumpur, Malaysia, but the timestamp is showing SGT (Singapore Time. Is there any way to change the timestamp to reflect our current location? 

Hello @Everyone,I'm encountering an issue with DocuSign Java SDK integration in my Spring Boot application, specifically concerning email notifications for signers and carbon copy (CC) recipients.Here's a breakdown of my setup and the problem:Setup: We have multiple signers, and their routing order is set sequentially. We have two carbon copy (CC) recipients, both assigned a routing order of "1". Observed Issues: Initial Email (Signing Request): When the document is sent for signing, signers receive the email according to their sequential routing order. However, both carbon copy users also receive an email at this initial stage, seemingly along with the signer who has routing order 1. Declined Email: If any signer declines the signing process: Signers with a routing order less than the declining signer's routing order receive a "declined" email. All carbon copy users also receive a "declined" email. Completed Email (Missing): If all signers successfully complete the sign

When I have more than one copy recipient, an error will be reported. it will tips “The specified envelope has duplicate recipients”

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}

My docusign webhook api calls work in developer account but they fail in prod account giving me KeyErrors in prod. Why is it different and when was this change made?Here’s how the dev response looks like: ``` {"status": "completed","documentsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/documents","recipientsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/recipients","attachmentsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/attachments","envelopeUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd","emailSubject": "Please review your solar contract","envelopeId": "8554a84b-c12e-4d66-a3ae-asdasasd","signingLocation": "online","customFieldsUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/custom_fields","notificationUri": "/envelopes/8554a84b-c12e-4d66-a3ae-asdasasd/notification","enableWetSign": "true","allowMarkup": "false","allowReassign": "true","createdDateTime": "2025-07-04T09:03:25.477Z","lastModifiedDateTime": "2025-07-04T09:03:25.493Z","deliveredDateTime": "2025-07-0

Hi everyone,I'm using the eSignature REST API v2.1 and enabling "transformPdfFields": true to automatically convert PDF AcroForm fields into DocuSign tabs.What I’ve noticed is:In the original PDF, some text fields are center-aligned.After transformation, those fields become left-aligned, and there seems to be no way to restore the original alignment.My questions:Is there a current way (via tab properties or metadata) to re-align or preserve the original alignment of transformed fields?Is there a plan to allow alignment options (left, center, right) on transformed tabs in the future?Thanks!  

Hi DocuSign Community,I'm working on an integration where I need to detect when the first recipient (vendor) signs a document so I can trigger a specific workflow (update status, send notifications, etc.).However, despite configuring my DocuSign Connect webhook to include recipient-signed and recipient-completed, I only receive the envelope-completed event, and never any recipient-level ones.🔧 My Setup: I’ve registered a webhook using the POST /accounts/{accountId}/connect API. events configured:  jsonCopyEditevents: [ "recipient-signed", "recipient-completed", "envelope-completed", "envelope-declined", "envelope-voided" ] The webhook URL is a secure public HTTPS endpoint (not localhost/tunnel). Routing order is sequential: Vendor (routingOrder: 1) Company Signatory (routingOrder: 2) The webhook handler correctly receives envelope-completed when all parties sign — but I do not receive recipient-completed or recipient-signed when just the vendor signs. ✅ Goal:Trigger my

Both the prod and developer docusign account have exact identical structure. Can anyone please help? This is blocking a lot of our customers and this is very high priority.this is my prod account envelope request structure → { "emailSubject": "Please review your solar contract", "documents": [ { "documentBase64": "", "name": "Solar Contract", "documentId": "1", "file_extension": "pdf", } ], "recipients": { "signers": [ { "email": "neel@xyz.com", "name": "neel patel", "phone": "(44)", "recipientId": "1", "routingOrder": "1", "clientUserId": "1000", "tabs": {"signHereTabs": [{"xPosition": 199, "yPosition": 176, "pageNumber": 1, "documentId": "1"}]}, } ], "carbonCopies": [{"email": "neel@xyz.com", "name": "neel", "recipientId": "10"}], }, "status": "sent", "eventNot

🎉 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 Go Live Status for my App is "Pending approval" along with an alert at the top that says "After submitting for review and signing the envelope, please allow for 48 hours and DO NOT submit for review again", but it also shows a link that says "Click here to proceed". Should I click on this link or should I wait for 48 hours as the alert says? 

Hello,I was trying to connect to DS using a PowerShell script and received the following error message: 'Error: Consent required.' Does anyone know the reason for this error and how I can fix it?  

We used to be able to send envelope creation requests to the API with FirstName and LastName variables in the JSON payload.  And the responses included FirstName and LastName.  Now we are suddenly getting responses that only include ‘name’.  Did something change recently?

Hello,         I am developing an integration from Workday to DocuSign to pull the completed documents into Workday. I am getting following error when trying to authenticate to the endpoint - https://account-d.docusign.com/oauth/token to get the access tokenError code : badrequestResponse :{"error":"invalid_grant","error_description":"unsupported_grant_type"}I have the following Grant type which works fine in Postman. In addition to grant type, assertion key is generated which is passed along with grant type in Workdayassertion=@{props['jwt.assertion']}&grant_type=urn:ietf:params:oauth:grant-type:jwt-bearerPostman: 

I want to create an envelope with the third party notary service and template via the eSignature REST API v2.1. But the TemplateRoles doesn’t have any attributes about notary recipient to set notaryType=remote, notarySourceType=thirdparty and notaryThirdPartyPartner=onenotary. The third party notary info that only can be set in recipients.notaries, but I can not set recipients and templateRoles at the same time. Since I get the error: The request contained at least one invalid parameter. 'recipients' may not be specifed when 'templateId' is set. Use 'templateRoles'.Any ideas? Thanks!

Hi there, We already set up the DocuSign Webhook, “Docusign Connect” which is running successfully in our PROD environment for another Signature API called from our application to connect to DocuSign. We are able to connect, so there are no issues with our DocuSign Connect configurations. However, we are using Legacy Mode and are also trying to implement new behavior with PowerForms in DocuSign where we created a PowerForm template. The user is able to click on the PowerForm URL from our application and proceed to fill out the PowerForm; however, Docusign is not publishing the signed document and sending it back to us after use signs and submits it. Does anyone have any suggestions on any approaches/solutions we can try? Screenshots have been provided as per our current DocuSign and PowerForm configurations. Any help is appreciated. Thanks,Linda 

Hi,  I have created an app in demo developer account in docusign. I am using docusign api https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes  to send document to my website user on their signup as well to get document status. Now My testing is done, my app is approved but i try to promote app to go-live, it gives me error “these accounts don't support API integrations. Select a different production account to continue'. Now i have two queriesIs it happening due to the fact that my live account does not any plan yet? If i take developer api plan in live account, will i  be able to promote app from developer account and Api integration will keep working with live keys?Kindly help me on this as i am not able to find any relevant information regarding and i am really confused on which plan to take in order for API integration to work. i am aware that developer API plan has a envelope limit/month.Thanks in advance 

hi docusign team i requested before 48 hours for go live after all successfully calling api for 20 times but now status show declined can i know the reason behind this?

Hi, We are unable to go live with our company account and cannot login to the support centre to open a case either, even thou we manage to login to the actual signing and developer account, and it’s not a recently made account. This is the first problem.The second, more important issue is the API go-life. I try to follow the instructions and get this error integration key.What are we supposed to do?Who can help? Where can I find an actual support email or phone number? Reaching support shouldn’t be that difficult for a paid platform!

Hello,I’m looking to set up the scheduled send attribute when creating an envelope using composite templates, but running into some issues. I understand to apply scheduled send it needs to use the following payload:            "workflow": {              "scheduledSending": {                "rules": [                  {                    "resumeDate": "2025-07-01T15:55:00.0000000Z"                  }                ]              }            }When I use this payload in a Create Envelope request that does NOT use composite templates, it is working correctly. I’m seeing it create the envelope with the defined workflow and see that it is set up to be scheduled for send out on the date specified. This is the request that works correctly:{  "emailSubject": "Please sign this document set",  "documents": [    {      "documentBase64": "<base64encodedString",      "name": "Lorem Ipsum",      "fileExtension": "pdf",      "documentId": "1"    }  ],  "workflow": {    "scheduledSending": {     

We have docusign connect setup to receive events and to monitor the recipient authentication status. The authentication method we are currently using is KBA and the RecipientAuthenticationStatus we receive is correct:<RecipientAuthenticationStatus> <IDLookupResult> <Status>Failed</Status> <EventTimestamp>2025-06-30T22:41:25.04Z</EventTimestamp> </IDLookupResult></RecipientAuthenticationStatus>However, when switching to SMS authentication and according to this doc https://www.docusign.net/api/3.0/schema/dsx.xsd, which might be outdatedthere should be PhoneAuthResult under the RecipientAuthenticationStatus. after testing this is not the case and instead i see an empty object with no info:<RecipientAuthenticationStatus />Any ideas how to get the PhoneAuthResult to show up?

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