eSignature API

Hello,I’d like to integrate JWT authentication to access the DocuSign API from my server.I understand that, on first use, I need to accept a consent request by visiting a URL like:https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature impersonation&client_id=CLIENT_ID&redirect_uri=https://www.docusign.comMy question is:Once I’ve granted this consent, is it valid indefinitely as long as I don’t change the client_id? Or do I need to repeat this consent step periodically (e.g., when the token expires or per session)?Thanks for your help!

Hello,I am trying to create a developer account. But it didn't let me create in a first step. it just does nothing when clicking on button can you please look into it . the details i am trying to signup is as followsit gives me error in the console Failed to load resource: net::ERR_NETWORK_CHANGEDIs someone facing the same issue?

I'm building a DocuSign integration using the v2.1 REST API. I create an envelope with multiple recipients and documents, and then open the embedded sender view using: POST https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/views/sender{ "returnUrl": "https://myapp/return", "viewAccess": "envelope", "status": "sent" }My goal: let the sender adjust Document Visibility settings before sending the envelope in the preview screen—uncheck/check visibility for a recipient.Go to: Prepare → Advanced Options → enable "Recipients must be signers to view signed documents" → click Next.Under Documents → Document Visibility, uncheck a recipient for a document and hit Done.Error appears: "Document visibility changes could not be saved. Please try again"Then, if I try Send, I get: "The access token provided is expired, revoked or malformed"However, if I remove the "viewAccess": "envelope" field from my sender view request, visibility changes save correctly.I

I am using a free DocuSign developer account and encountering the following error when trying to send an envelope:“The recipient limit on the envelope has been exceeded. The cumulative recipient limit has been exceeded.”I am unsure about the exact recipient limits for free developer accounts. In my case, the number of recipients per envelope is relatively small (2-3), yet this error still occurs. Could you please clarify what the exact recipient limits are for free developer accounts? Also, are there any ways to resolve or work around this issue?

Hi all,I’m integrating DocuSign with my application using the Node.js SDK and template roles. When I first set up my integration, the template autofilled a few fields as expected. However, now when envelopes are sent, the recipients still receive the emails, but none of the fields in the template are being filled out—even though the data I’m passing looks correct.Here’s a summary of my setup and what I’ve tried:I’m using the createEnvelope API with a templateId and templateRoles.The envelope is sent successfully, and recipients get the email, but all fields are blank.The data I’m passing to the tabs property in templateRoles matches the field names in my template.When I first set this up, a few fields were autofilled, but now none are, even though the code and data structure haven’t changed.I’ve double-checked that the role names and field names in my code match those in the template.Example of my envelope definition:const envelopeDefinition = { templateId, status: 'sent', templateR

Hey Docusign community,I have a Docusign account with a few users. I am trying to perform common CRUD operations with users using the Users api through the Python SDK. I was able to remove (or close, as you call it) a user from the account using this: from docusign_esign import UsersApi, UserInformationdef remove_user(users_api: UsersApi, account_id: str, user_ids: list[str]): users_info = [ UserInformation(user_id=user_id) for user_id in user_ids ] user_info_list = UserInfoList(users=users_info) return users_api.delete(account_id=account_id, user_info_list=user_info_list) Now, I want to reactivate this same user using the Python SDK. How can I do that? I have tried these two enable functions below, but with no success: def get_user(users_api: UsersApi, account_id: str, user_id: str): return users_api.get_information(account_id=account_id, user_id=user_id)def enable_user(users_api: UsersApi, account_id: str, user_id: str, permission_profile): user_info = get_us

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 

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”

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

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?

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 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?

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": {     

I have a text tab assigned to a recipient and I’m prefilling its content when creating the envelope via Docusign API. I need to break the line using \n,  but when I add this character in my text, the text tab shows it instead of breaking the line. I also tried \\n, but had no success.How can I accomplish this?

I'm working on a DocuSign integration using the eSignature API (sandbox environment) and I need to configure BCC email settings on envelopes using the email_settings.bccEmailAddresses field.The request works perfectly in the API Explorer:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeemailsettings/create/?explorer=true However, when I try the same request from my Ruby application (using the official SDK), I get this error only when bccEmailAddresses is included: {  "errorCode": "API_REQUEST_IS_FORBIDDEN",  "message": "The API request is forbidden. Request blocked due to excess usage"}HTTP status: 444 Without the email_settings, the envelope is created successfully.I also tried to set email_settings during the create_envelope call, but it did not work — the field is either ignored or causes the same error depending on how it's passed. Even when correctly structured (and working in the API Explorer), it fails in the application context.Details: SDK: docus

Bonjour,Je vous contacte concernant un dysfonctionnement observé lors de l'envoi de documents XML via l'API DocuSign.Jusqu’à récemment, nous pouvions transmettre des fichiers au format .xml dans une enveloppe, et ceux-ci étaient correctement interprétés et affichés de manière lisible dans l'interface DocuSign.Cependant, depuis peu, bien que l’appel à l’API (POST /envelopes) retourne un code 201 (Created), le document XML n’est plus converti ni affiché correctement. Il apparaît désormais sous forme brute (texte XML non rendu) pour les signataires, ce qui nuit à la lisibilité et à l’expérience utilisateur.Je souhaiterais savoir : Si ce changement est volontaire (ex. : mise à jour du moteur de rendu DocuSign) Ou s’il est possible de restaurer le comportement antérieur via une configuration spécifique Dans l’attente de votre retour, 

I am having issues related to RECIPIENT_LIMIT_EXCEEDED on what I believe is a free account.  Most of the responses to this have said the limit is 5 recipients.  I am trying to send 2 signers and 2 CC’d users and getting this error.  I have tried with different emails and everything and am still getting the same error.  Everything works fine if I take my CC’d users off the email.Any help would be appreciated.

Hello Everyone, I am creating a webform for a loan application, and I see that there is an option for currency in the webform, but I cant figure out how to link it to an API in the template I have. I’ve tried to use a text box that has a number validation, but that isnt working. I’ve tried just a text box, and manually changed the API reference in the webform, but that didnt work either. Am I missing something?  

I am trying to void an envelope using the DocuSign REST API. I used the API Explorer provided in the DocuSign Developer Portal.Here is what I did:✅ API endpoint:PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId}✅ Request body I used (in API Explorer):{ "status": "voided", "voidedReason": "No longer needed" } ✅ The response I get back:{ "envelopeId": "e811fcff-e313-4234-a755-09d394729536" } Notice — there is no "status": "voided" returned in the response.✅ When I run GET /envelopes/{envelopeId} afterwards, the envelope still shows status "sent" (not "voided").✅ I can still access the signing link and sign the envelope.What I have tried: Confirmed that I used the correct accountId and envelopeId Using API Explorer, so OAuth and headers are handled Provided valid voidedReason and "status": "voided" in body Tried multiple times — same result Question: Why is my envelope not being voided even though I am calling the correct endpoint? Is this an issue with API Explorer or somethin