Developer

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

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 tes

 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

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?

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.   

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

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? 

Docusign account URL is account-specificAccording to https://developers.docusign.com/platform/api-endpoint-base-paths/, the {server} value (which determines the base URL for several Docusign APIs) is specific to a Docusign account:The Account Base URI section of the Apps and Keys page. This is confirmed by the structure of the /oauth/userinfo response, where the base URL can vary per account. For example:{ "sub": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "name": "First Last", "given_name": "First", "family_name": "Last", "created": "2015-08-

Received dependency version mismatch error while trying to import “DocuSign.eSign.dll” version 8.1.0.While downloaded “DocuSign.eSign.dll” (version 8.1.0) using .NET NuGet Package Manager, the version of “System.Numerics.Vectors.dll” downloaded was “4.1.4.0”. But when tried to import that “DocuSign.eSign.dll” (version 8.1.0) to our product, got an error as “System.Numerics.Vectors.dll” version “4.1.3.0” is missing.Unable to get any reference of the version 4.1.3.0 for “System.Numerics.Vectors.dll”.Please help to this dependency version mismatch error for “DocuSign.eSign.dll”. Error Message: “Could not load file or assembly ‘System.Numerics.Vectors, Version=4.1.3.0’ or one of its dependencies. The system cannot find the file specified.”

I am trying to create an application with DocuSign Connect. In DocuSign Connect I have enabled Include Basic Authentication Header, but still I am not able to make a call on the URL provided. I checked the logs on the server and the request reached the server but was rejected because of invalid credentials.I am able to make a call to the URL from postman with the same username and password. Am I missing some settings here? Is DocuSign not sending the authentication in the header as “Basic <Credentials>” or is it doing something else? Thanks in advance.

My integration key is currently in development and we’re getting ready to submit for review to move into production. However, we need to continue testing with they key until go live. Once the key is moved into production, will I still be able to use it in the test environment? How long does the approval generally take to promote the key to prod?

Hi everyone,I'm running into an issue when making API calls to DocuSign using our SOAP client. Specifically:Not all the tab values we're setting are being sent in the request. Even when we explicitly define certain tab types (e.g., RadioButton), they appear to default to simple text fields in the envelope.I've attached an example of a radio tab configured prior to the payload, along with a Fiddler capture showing the request being sent.Has anyone run into similar behavior or have suggestions on what to check? Any help is appreciated! Fiddler outputRadio Tab configuration 

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of April 2025.Thread: Multiple documents with Auto-Place not using DocumentIdhttps://community.docusign.com/esignature-api-63/multiple-documents-with-auto-place-not-using-documentid-23643Summary: The developer has created an envelope through the C# SDK and is trying to add tabs to the documents in that envelope using

Hello, In my Django app, we can create and edit a docuisgn template internally. I am using the embedded url. It works great, but there are a few tweaks. Safari does not like iframes for example. And the return url in dev mode can be a challenge. But in production it works. I am looking to harden the approach. I have added a few things like a side bar menu to help with guiding people through the process. Stuff like that. Does anyone have an experiences with this approach that they would like to share? thank you. Paul.

I am developing a React Native application where I need to implement document signing functionality for PDF files. The requirement is to allow users to upload a PDF from their device and sign it using DocuSign. However, I want to achieve this without creating or managing an envelope in DocuSign.Is there a way to directly sign a PDF document within my React Native app without involving the envelope process?

Hello,I'm currently using the DocuSign Java SDK (docusign-esign-java) version 6.0.0 to call the createEditView method from the TemplatesApi class, as shown below:templateViewRequest.setReturnUrl(returnUrl);templateViewRequest.setViewAccess("template");ViewUrl view = templatesApi.createEditView(accountId, templateId, templateViewRequest);I would like to hide the “Back” button on the Template Edit View screen.According to the API documentation, it's possible to customize the embedded view using the settings object (e.g., showBackButton, startingScreen, etc.), but the TemplateViewRequest class in the SDK doesn't seem to support setting this settings field.I would like to ask: Is there a way to set the settings parameter when using createEditView with the Java SDK?

We are using JavaAfter calling:net.docusign.api_3_0.AuthoritativeCopyExportDocuments authcopy = api.exportAuthoritativeCopy(eid)How do get I a checksum for api.acknowledgeAuthoritativeCopyExport?I’ve tried to use the Javscript example I found and covert to Java, but I am clearly missing something! var CryptoJS = require("crypto-js");var document1 = "<documentpdfbytes>";var coc = "<certificatepdfbytes>";// CryptoJSvar parseB64 = CryptoJS.enc.Base64.parse(document1);parseB64.concat(CryptoJS.enc.Base64.parse(coc));var shaB64 = CryptoJS.SHA1(parseB64);console.log("->", shaB64.toString(CryptoJS.enc.Base64));</certificatepdfbytes></documentpdfbytes>

Our company has two Docusign accounts, one of which is linked to Ironclad. Periodically, at random periods, the integration goes off and any signature process is stopped. We are obliged to log on to Docusign and relink the two apps. This behaviour is not normal, since a link validly affirmed should be permanent. If there is a periodic reset for whatever reason (e.g. security) this should be clearly stated so that the relinking of accoints can be made object of a procedure to ensure uninterrupted functionality. The issue is critical as it interruprs workflows and prevents the signature of contracts. Thank you in advance for your feedback.