Developer

Not sure if my last question was posted…As I said before, this is not much information on the JavaScript $.ajax call on the DocuSign REST API.  If there was, not much information on it (or even examples).I’m am trying to use JavaScript (JQuery) $.ajax call using a DocuSign REST API.  Even though I tested out on Postman successfully, it does not work using $.ajax (i.e. https://account-d.docusign.com/oauth/token) including the header information and the requested body (note the ${???} represent a placement of the actual values - just to be safe):                    let tkHeader = {                        'Content-Type': 'application/x-www-for-urlencoded',                        'Accep

Hey developers! Have questions about which OAuth grant to use? Trying to get an access token to test our APIs?This month’s AMA is all about OAuth 2.0 authentication at Docusign.The thread is open now through November 25—comment with  your question and I’ll get right back to you (I’m a Senior Programmer Writer at Docusign).To make this more fun, when you add a question, you’ll be automatically entered to win a$100 non-branded gift of your choice from Loop & Tie 🎁Topic for this AMA: Authentication and access tokensOAuth authentication is the foundati

I added to a document template a checkbox, and when i edit a data label, it don’t save the new label. There’s anything i might need to edit additionally?After edit the Data Label and save it, it return to the original value “Checkbox 1a31da89-4ae0-49…...”. I validated and i’m not using the Data Label anywhere. Any Data Label that i entered is reverted to the original value. 

There seems to be vert little information about using $.ajax call to a DocuSign REST API on the web.   Is it possible to use $.ajax? If there is, how can use setup $.ajax to perform an OAuth/Auth  Using https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id=${integrationKey}&redirect_uri=https://localhost Able to do this directly on a web page on the address line but not using $.ajax Get a token from the OAuth/Auth (https://account-d.docusign.com/oauth/token) If a access token is return, use it to GET/POST a DocuSign REST API through

Hii have a problem while sending a documents via binary transfer in multipart requests to the endpoint: POST /restapi/v2.1/accounts/{accountId}/envelopes Im receiving the following error:{"errorCode":"NO_DOCUMENT_RECEIVED","message":"The document element did not contain the encoded document, or there is a problem with the encoding. Bytes for document corresponding to documentId 1 not found in request. 'documentId=<x>' possibly missing from Content-Disposition header."} For some context, im sending the request from an SAP-System, and im limited to the http_interface that the system provides. I dont have full control over how the request is generated in the end and that is the problem i think:See → The content-disposition header of the added pdf-file is in lower case, while the tuturial (

Here are some of the latest popular questions that developers asked in the Docusign Community for the month of November 2025. Thread: Inquiry: Polling Violationhttps://community.docusign.com/esignature-api-63/inquiry-polling-violation-25891Summary: The developer is looking for

My team has submitted my go live request for about 4 days now and i still haven’t gotten an approval , does anybody know what the issue might be or how to speed this up ? i have a deadline to meet, it will be nice to get this working as fast as possible. 

After authorizing through the authorization url, how should the code passed in when docusign initiates a callback be used? I haven't found a clear definition of "code" 

We are attempting to Go Live and moving our developer integration key to production, however we have been systematically declined every time for… not having a production key. How are we supposed to provide a key which we are applying for? 

I’m working with DocuSign Maestro Designer and need to get the value of a webform field/description that was filled in during a workflow run. Specifically, I want to retrieve the field values via the WorkflowInstanceManagement: getWorkflowInstance API.Currently, I have access to: accountId workflowId instanceId But when I call getWorkflowInstance, I only see general instance metadata and status details. I don’t see how to extract the actual webform responses that were submitted.

I used the Application integration key as the userId and called the ApiClient#requestJWTUserToken method. The returned tokenType was Application. What is the function of this token? Is there any documentation to explain? 

We have been successfully using the API end-point since around March 2024 with a custom built plugin in WordPress Gravity Forms on our USA server. The custom plugin uses the composer package docusign/esign-client ^6.10 behind the scenes. In mid august we migrated our setup to new server in the EU. Since migrating to a fully patched ubuntu 24.04 server (no java or log4j), using a LAMP stack, all of our API calls get HTTP 444 with the vague error message “The custom error module does not recognize this error.”If we run “curl -v  https://na4.docusign.net/restapi”  on the cli from the new server we receive this response: < HTTP/1.1 444 < Content-Type: text/html< Vary: Origin< X-Content-Type-Options: nosniff< X-DocuSign-TraceToken: c247ca85-1505-4838-9d76-693daec3245d

I am sending emails via DocuSign API to recipient with type carbon_copy. How can I track if the email got bounced back due to reason like invalid email address? It seems DocuSign automatically mark the status to completed if the recipient type is carbon_copy.

I need to send an envelope that is made from multiple server templates (compositeTemplates). There is a fixed set of signers (4) across the business process — each signer should only sign the templates that are assigned to them (not every signer signing every template).My goals are: Avoid repeating signer details (name/email/custom emailNotification) inside every composite template so the request JSON stays small and non-redundant. Reuse “global” signer definitions (by recipientId / recipientIdGuid) and reference those signer IDs wherever a template role needs that person. Achieve faster envelope creation / better API performance by reducing payload size and duplication. When I try to use global signers and reference their recipientId (or recipientIdGuid) from inlineTemplates, DocuSign rejects

I am calling Docusign EnvelopeService to send emails with documents. How can I track if the email is bounced back due to non-existed email address? 

Hi.In the documentation, I was able to find a complete list of statuses with which a user’s work with the Recipient View can end (and which is subsequently passed as a query parameter to the specified RedirectUrl):https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createrecipient/At the same time, I can’t find similar information anywhere for the Sender View:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createse

Hi, I am developing an interface from SAP C4C (Sales Cloud) which brings in Sales quote data for e-signature. There is a standard connector available in Integration suite for authenticating and perform function calls to Docusign. Can someone help me with what function/API to call and if there is a sequence of APIs I need to call for this requirement

I'm trying to set up JWT Grant authentication in the DocuSign sandbox, but I'm constantly running into an invalid_grant / issuer_not_found error, even though I have successfully completed the consent process.My Configuration Environment: Development (account-d.docusign.com) Integration Key: 1b490ae4-97d1-4b5b-a4d4-cee9998fdf03 API Account ID: 73228f49-0509-4526-ac11-20a1025960e3 User ID (the user who granted consent): 80a3a400-b695-4fbf-9809-7cf4538d9419 Problem DescriptionMy server-side application (a Firebase Cloud Function on Node.js) is using the official docusign-esign library to call requestJWTUserToken. In response, I receive a 400 Bad Request error with the following body:{ "error":

Hi all,I’m trying to add a new recipient to an existing envelope after it has already been created.I’m using the following endpoint:/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}?advanced_update=true&resend_envelope=true(from the Docusign Documentation)It works fine for all recipients, except for the one I’m trying to add after the envelope was created.When I try with this new recipient, I get this error response:"UNSPECIFIED_ERROR"Object reference is not set to an instance of an object I’ve tried multiple approaches and endpoints, but none of them worked.Here’s one of the request bodies I’ve used:{ "recipients": { "signers": [], "agents": [],

Hello everyone,We’re currently working on passing values from our website into a DocuSign Maestro webform via API trigger_inputs, and while we’ve had success with text fields and date fields, we’re running into challenges with other field types.Specifically, we want to pre-select a radio button option so that when the webform loads, the correct option is already chosen. For example: Gender field (radio buttons): Options are Male, Female, Others. We’d like to pre-select Male. We suspect this challenge may apply similarly to dropdowns, checkboxes, and phone number fields as well.Has anyone implemented this successfully? Could you please share examples of the correct variable types or payload structure required to map these field types (radio buttons, checkboxes, dropdowns, phone)?I’ve attached screenshots for reference. Any guidance or working

Hi, I have issue with attachments, they just don’t return to Salesforce, my expectation is that after user signed doc, it should attaches to Salesforce record, I also adjusted Salesforce connection in Admin panel at DocuSign Demo and installed and connected package in Salesforce sandbox. I attached Apex file, could someone help me?

 Hello,I want to configure the settings for my organisation. I am an Admin and can edit all settings except the recipient Roles. Why?I need it for a third party Application to work. Am I missing something here? Why cant I set the checkmark on “Enable allow to edit recipient”?  

I am trying to automatically send docx documents for signature to Docusign using only google apps scripts. I went through all the steps to convert the docusign RSA private key from pkcs1 to pkcs8 and then paste the pkcs8 key into the apps script project properties, but i am still running into this error on the code line const signature = Utilities.computeRsaSha256Signature(signatureInput, keyBytes); I also tried an alternative with uploading the pkcs8 .pem file to drive and using the file ID as one of the project properties, but that didn’t work either, the cleaned key in the debugger is showing up like this (screenshot). I used the texteditor on macbook (with make plain text formatting utf-8 option) to create the .pem  files, the openssl terminal command to convert from pkcs1 to pkcs8 and the cat command to get the pkcs8 key after conversion.

So I have to make an envelop using a combination of documents:First is a lets say 10 page flattened pdf from our document management system that need to be in the envelop (in this document no signature or client input is required), then,it is followed by another document that is from the same system and this I am overlaying with a server template.Issue: When the envelop is created, the server template fields are overlaying on the first document and not the second where it is supposed to.I am using the following Json: {    "allowMarkup": "false",    "brandId": "86aee07f-0f86-4c26-xxxxx",    "compositeTemplates": [        {            "compositeTemplateId": "1",            "document": {                "documentId": "1",                "fileExtension": "pdf",                "name": "forms.bound_pages",                "transformPdfFields": "false"            },

When I try to use Google Drive to add documents, nothing happens. I wen thru a step by step of API access, ensuring it was trusted, and then in google admin workspace, ensuring Drive SDK thing is on, still nothing. restarted the comp. nothing.  I am not sure what else to do.