Developer

I have a requirement to wrap the Print & Sign flow into my custom app. I need to be able to download the document for an offline Wet Signature and then Upload the signed document upon completion.I have set EnableWetSign to “true” on the EnvelopeDefinition.   I am not finding the Api calls to download and upload the document.  Do they exist and if so, where can I find a reference for these activities?

 anyone know what this means // how to create a new envelope despite this?

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

Hello DocuSign Community,We’re integrating DocuSign with our internal system via the REST API and encountered an issue with controlling permissions in Sender View.What works: We successfully create an envelope via API with attached documents. The envelope remains in created status, as intended. We then create a Sender View (embedded) using the CreateSenderView API call. Our goal:We want the sender to add tabs (fields) for other recipients, but not be able to: Edit or remove the document itself Add/remove recipients Change routing or envelope metadata What we tried:We passed the following parameters into the ReturnUrlRequest (as described in the documentation):{  "returnUrl": "https://ourapp.com/return",  "configuration": {    "disableDocumentEdit": "true",    "allowRecipientRecursion": "false",    "allowComments": "false",    "allowReassign": "false",    "messageLock": "true",    "useDisclosure": "false"  }}Problem:Despite passing all the configuration flags, the resulting Send

Whether anchor tags work in PDF generated from EJS templates? Are there any known limitations in parsing anchors in dynamic PDF files? Any best practices for using anchor tabs in a dynamically generated PDF?

I'm trying to create an envelope using a template and then modify it to add Identity Verification. However, the envelope created earlier doesn't overwrite the existing signer role, even though I'm making the request with the same role name.Does anyone know why this might be happening or how to properly update the role?

I am trying to invoke create envelope endpoint using http request from my application and getting connection reset by peer.Following is the account id account_id: c4de313b-e2ac-4a31-9902-4253b58fb133 Exception :o.apache.http.impl.execchain.RetryExec : I/O exception (java.net.SocketException) caught when processing request to {s}->https://demo.docusign.net:443: Connection reset by peer   

Hi there,Scenario: I have an envelope template 5 recipients, and multiple documents 5-15, the documents contain fields using anchors, multiple fields are repeating inside documents (same Data Label), including fields like SignHere and FullName. Using API a draft envelope is created from template, with fulfilling value for tabs.Problem: Even if the total number of tabs not exceeding 450, while creating envelope we receive error `TAB_LIMIT_EXCEEDED`, when the tabs limit per envelope is 5000.Attempts: When I remove all fields, the creation works. After removing few documents from template (~180 tabs remain) it goes through.Since template creation is responsibility of law department, we can’t limit them in numbers of documents or fields used, (the DocuSign limits are ok)Any ideas how to investigate and what can be the issue of this problem?

Hello DocuSign Team, can you please help us with the pagination parameters( start_position or count) for DocuSign Rest API’s.

Hi everyone, I have been testing GET method for Envelope’s Documents to retrieve an integrated document using documentId = combined as it is guided here:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocuments/getHowever, as said in the title, I cannot exclude the comment history file from the combined document, and it is not like I expected. Are there any ways to acquire this?

I’m using eSignature client api php sdk, how can I set template prefilled tabs while creating an envelop ? Here is my code $invoiceNumberTab = new Text([ 'tab_label' => 'InvoiceNumber', // Must match prefill tab label in template 'value' => 'INV-20240508']);$prefillTabs = new PrefillTabs([ 'text_tabs' => [$invoiceNumberTab]]);$templateRole = new TemplateRole([ 'email' => 'signer@example.com', 'name' => 'John Doe', 'role_name' => 'Signer' // Exact match to template role]);$envelopeDefinition = new EnvelopeDefinition([ 'status' => 'sent', 'template_id' => 'TEMPLATE_ID', 'template_roles' => [$templateRole], 'prefill_tabs' => $prefillTabs]);$envelopeSummary = $envelopeApi->createEnvelope($account_id, $envelopeDefinition);echo "Envelope ID: " . $envelopeSummary->getEnvelopeId();And tried with this way also not working $templateRole = new TemplateRole([ 'email' => 'signer@example.com', 'name' => 'John Doe', 'rol

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”,

 How do I change the sender's email ID and name in an envelope? I want to use a different organizational email ID instead of the one linked to the DocuSign account

Recipients are forced to drag & drop placeholders even though the PDF envelope contains all the docusign api tags. It should not force the recipients to drag and drop.This works as expected in my developer account but fails in my production account. I have checked the code multiple times and there does not seem to be issues with any of the related code. The pdf is being passed with all the tags.  

I want to use a different name and email ID for the envelopes I send using the DocuSign Envelope Sent API. I have tried adding a new user, setting 'Act as User' in the header, and passing the user ID of another DocuSign account. How can I do this?

I am using docusign free account to integrate it with my application , I have tries to create envelope and doing e-sign.I am getting the issue if a single recipient sign multiple times (more than 10) and finish. the signature is not visible on the document. Please help me out here , is there any limitation with free account or something i doing wrong. Please suggest. 

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.

Hello,We are integrating DocuSign via the REST API. In our use case, we use the createSenderView method to allow an initiator to manually place signature tags in the document.However, the sender view also allows the initiator to: Replace or delete the documents, Modify the list of recipients (add/remove/change), Change the signing order, roles, etc. This is not acceptable for our workflow. We only want the initiator to place tags on the pre-uploaded document — and not be able to edit recipients or the document itself.Question: Is there a way (via configuration, permissions, roles, or account settings) to restrict what the user can do in the sender view?If not, could you please suggest an alternative approach where: The document is fixed (read-only), Recipients are fixed, The initiator can only place fields (tabs)? Thank you!

Hi! I just published a new YouTube tutorial showing how to create a subscription-based payment process using Stripe and JotForm—an ideal solution when Docusign's payment options aren't enough.You’ll learn how to:Connect Stripe to JotForm and fetch your subscription plans Apply coupon codes automatically from Stripe Build a mobile-friendly contract and checkout experienceWatch 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

We are using Docusign JS library for embedded signing experience. In chrome browser, when we load the url, it is adding iframe in DOM and then opens modal to accept terms.In edge browser, it just hangs and never open the modal to accept terms with exceptions below.   

Set the ExpireEnabled, ExpireAfter and ExpireDateTime using Docusign SDK 8 for C# and its not taking the values. Key points :Using Docusing SDK 8 with C# Using developer accountI’m creating the envelope from a template.I changed the expiration days in docuSign settingsThese are the lines of code :   // Get the envelope definition after configuration var envelopeDefinition = config.GetEnvelopeDefinition(); // Set the envelope status to "sent". The signer will get an email from DocuSign envelopeDefinition.Status = "sent"; // Set expiration date envelopeDefinition.ExpireEnabled = "true"; // Enable expiration envelopeDefinition.ExpireDateTime = DateTimeOffset.UtcNow.AddDays(14).ToString(); envelopeDefinition.ExpireAfter = "14"; // Set expiration days // Initialize the EnvelopesApi client (reuse existing ApiClient) EnvelopesApi envelopesApi = new(this.ApiClient); // Create the envelope on DocuSign (it will not be sent due to the "created" status) EnvelopeSummary envelopeSummary = envelopesA

Using methods of DocuSign.eSign.dll in a Window Service , developed with C# and targeted to .NET framework 4.7.2 you got a seemingly endless number  of runtime exceptions like ‘Could not load file or assembly 'System.Memory, Version=4.0.1.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.’When you fix the the dependency exception e.g. for Microsoft.IdentityModel.Tokens.dll a new problem with Microsoft.IdentityModel.Logging.dll shows up and then with Microsoft.IdentityModel.JsonWebTokens.dll an so on.Even the latest version of DocuSign.eSign.dll (8.1.0.0) seems to depend on older or deprecated versions of system dlls.Has anyone already had to deal with this problem ? 

We’ve just released our May issue, and it’s packed with good news: our 2025 Docusign for Developers Release 1! This release includes major new features for developers: private extension apps and the new AI-enabled Visual Studio Code extension (both in beta), the Connected Fields API, Maestro embeddability, the Workspaces API, connected fields and data IO extensions, and API-based Notary On-Demand initiation. These new features let you bring agreements into the systems you already use, extend automation where it matters most, and manage with flexibility, speed, and scale. Get all the details in our top story!More good stuff in the May newsletter:See how private extension apps can connect the dots between your Maestro workflows and your internal systems. Dive deep on using data IO extensions to automate your data flows. We’ve just released our new Embedded Sending sample app. Try the app and download the source code for use in your own integrations. Get perspective on how to use extensio

I’m getting this error when obtaining the access token through the /oauth/token endpoint:{"error": "invalid_grant", "error_description": "invalid_user_siteid"}I couldn’t find any info in the Troubleshooting Common Errors. What does this error mean and how do we address this?