Skip to main content
arrow-left Back to Docusign.com

Developer

Ask questions, share knowledge, and get help from other developers as well as our support team.

  • 1,148 Topics
  • 12 Replies
1148 Topics
S
Newcomer
SeanJuegosDevNewcomer
asked in eSignature API
Multiple unknown signers

Hello, I’m trying to use the docusign rest api to create a signing url from a pdf. The problem i’m encountering is no matter whether i sent up a placeholder recipient or use a template to have a user create their own envelope they can sign i get auth blocked. the reason why i’m doing it this way is that A. users in my app may not have a pre-existing docusign account and i don’t want to add a cascade update for all event documents when they make one B. i don’t want our app to keep having to use the hosts docusign account to add people as recipients. all i need is a solution that opens a signing event in a url and the host can get those signed documents

230
S
Newcomer
sofian_solusign
Troubleshooter
sofian_solusignTroubleshooter
posted in General
Automate Your Applications with Docusign

Hi! I just published a new YouTube video on how to automate complex application forms using Docusign Web Forms.You’ll learn how to:Build a mobile-friendly credit application form with multiple layers of conditional logic. Capture incomplete submissions in case your signers don’t go through the entire process. Auto-export application form data into your CRM, eliminating manual entry. Implement ID verification to prevent fraud.Transform your credit application process with automation! You can find it 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

190
sofian_solusign
Troubleshooter
D
Newcomer
danielsamaliaNewcomer
asked in eSignature API
multiple sending

I'm trying the trial version. Can I send an envelope to multiple people at the same time but have each person sign the document without other users seeing the signature? as if it were a single shipment.Has anyone done this in power automate(Microsoft365)?

341
Michael.Rave
Docusign Employee
K
Newcomer
KamillaNewcomer
asked in eSignature API
DS Electronic Signature does not register documents at a notary's office.

Quando assinamos o contrato com a Docusign, deixamos bem claro que os documentos que enviaríamos aos clientes para assinar seriam enviados a um cartório para registro. No entanto, enviamos um documento e ele não foi aceito porque foi assinado pela DS Electronic. Eles aceitam o ICP BRASIL, mas nem todos os clientes possuem certificado digital. Quando entramos em contato com a Docusign, eles agora querem cobrar outro valor por uma assinatura qualificada, o que não foi o que nos foi dito quando assinamos o contrato. Precisamos urgentemente de uma solução para este caso. Estamos aguardando uma resposta. .

271
A
Active Voice
A
Newcomer
amitms123Newcomer
asked in eSignature API
DocuSign Admin API Unauthorize error

I am trying to call DocuSign Export API's and getting error "Unauthorized" below see below details for more : Code : (Azure Function C#) string url = $"https://api.docusign.net/Management/v2/organizations/ORGID/exports/user_list"; _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); var requestBody = new StringContent("{\"type\": \"organization_user_list_export\"}", Encoding.UTF8, "application/json"); var response = await _httpClient.PostAsync(url, requestBody); if (response.IsSuccessStatusCode) I'm trying to export all users list using DocuSign admin API, however I have provide the required consent but still getting "Unauthorized error"Below is the code (Azure Function C#) that i am using:string url = $"https://api.docusign.net/Management/v2/organizations/ORGID/exports/user_list"; _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); var requestBody = new StringContent("{\"

350
A
Newcomer
L
Newcomer
LucasBCastroNewcomer
asked in eSignature API
Request application consent generating JWT payload encrypted

Hello, i’m following the steps in this doc https://developers.docusign.com/platform/auth/jwt/jwt-get-token/.and when i paste the jwt on jwt.io the payload come in this format:  "\u0001\u000b\u0000\u0000\u0000\u0001\u0000\u0006\u0000\u0007\u0000\u0000my�SL�H\b\u0000\u0000���SL�H\u0002\u0000M�%��O�B�'\u0015[�0É\u0015\u0000\u0001\u0000\u0000\u0000\u0018\u0000\u0003\u0000\u0000\u0000\u0005\u0000\u0000\u0000\u001d\u0000\u0000\u00002\u0000\u0000\u0000\r\u0000$\u0000\u0000\u00001dff3d9d-d24b-48b0-bd7b-96d282b4d7af\"\u0000$\u0000\u0000\u00001dff3d9d-d24b-48b0-bd7b-96d282b4d7af0\u0000\u0000my�SL�H\u0012\u0000\u0001\u0000\u0000\u0000\u000b\u0000\u0000\u0000interactive7\u0000}\u0012����5N����3t\u0016�" Even after verifying the signature with public and private key..  and if I try to use the JWT on https://account-d.docusign.com/oauth/token I still get:{"error": "invalid_grant","error_description": "user_not_found"}

471
R
Docusign Employee
A
Newcomer
anupk11Newcomer
asked in eSignature API
Need help with creating Access token

I have a Node.js application where I create a DocuSign envelope. Currently, I use the Authorization Code Grant flow to manually obtain the access token and refresh token. However, the refresh token expires every 30 days if not used. Is there an alternative method that would allow me to avoid manually generating a new access token and logging in each time the refresh token expires?

904
A
Newcomer
S
Newcomer
seven-avalonNewcomer
asked in Embedded Signing
Bundle.js How can I cleanup the listeners added to the signing events?

Hey there, currently I’m integrating the bundle.js to my application to sign an agreement. I’m using a dialog to present this document, this dialog can be closed or opened, I was looking for a way to clean the event listeners of the signing but I can’t find any information about it.  I’m using React, there’s any way to remove the listeners associated when unmount the docusign embed document?

1152
T
Newcomer
neethujkp
Troubleshooter
neethujkpTroubleshooter
asked in eSignature API
Refresh Token Expiry

What scope parameter value should we use for the Authorization Code endpoint to ensure that the refresh token never expires? Currently, we have set the scope to "signature extended," but the refresh token still expires after 30 days. 

6823
A
Newcomer
S
Newcomer
SaaSNewcomer
asked in eSignature API
Is /accounts/{{accountId}}/reports/report_results_csv a supported endpoint?

Hello, This endpoint is listed on Docusign’s postman workspace, however I see no documentation for it. Is this a supported endpoint? Thank you!

433
JohnSantos
Valued Contributor
Y
Newcomer
YefanNewcomer
asked in eSignature API
Is there a way to display Company name as Envelope Originator instead of my user account info?

Hello, We have an application using eSignature API for signing our collaborators’ annual assessments. The authentication flow is JWT Grant, and the impersonated user id I’m passing in the configuration file belongs to my user account.I was wondering since we purchased Branding option, is there any way to overwrite the account details of the Envelope Originator / Record tracking holder by the Company name in the Certificate of Completion.Or should I create a general Admin account and pass this user id in the configuration file?Thanks for your help.

440
Y
Newcomer
S
Newcomer
Sweenal FurtadoNewcomer
asked in Embedded Signing
Embedded Docusign signing_complete event

I have used embedded docusign in my implementation. Everything works fine but once user is done signing the envelope and clicks on “Finish”, it takes about 7-8 seconds for docusign to respond back with the sessionend event signing_completeSo user might get confused or think something went wrong as the screen looks like this.and after 7-8 seconds, we get the eventIs it possible for docusign to send the response within 2-3 seconds?Or else is there any event where we can show processing loader so that user is not confused?Thanks,Sweenal​​​​​​​

33010
V
Newcomer
A
Newcomer
Anthony.CNewcomer
asked in eSignature API
Random 500 error

We built a C# SDK API that is connected to our customer’s website, and is supposed to call DocuSign’s API. From time to time, the DocuSign API sends back an 500 error without any error message attached (it can happen at any part of the API, from the creation of the enveloppe to the sending of the mails). The API can then be recalled with the exact same infos given the first time and will work properly.The weird part is that when we used our API for tests purposes through swagger (we tested it for a very long time) that kind of 500 error never occured. After searching any kind of possible problem, I’m still completely clueless about where the error might be coming, any kind of idea is appreciated.If any information is needed i’ll do my best to answer asap, thank you in advance. 

814
E
Docusign Employee
M
Newcomer
MilutinKLycNewcomer
asked in eSignature API
Prevent users to modify recipients and documents when in coorection view

We are integrating DocuSign into our application and using the Correction View feature to allow users to edit document fields before sending envelopes. However, we need to prevent users from modifying recipients and documents while still allowing them to edit signature fields and other form fields.We have tested using the CreateLock API with LockType = "edit" and the useScratchPad parameter.When useScratchPad = false, users are unable to modify anything, including document fields. When useScratchPad = true, users can modify document fields, but they can also change recipients and documents, which we need to prevent.Our goal: We want users to have the ability to edit document fields (such as signature and text fields) but prevent them from changing recipients or documents when the Correction View is opened.Is there a way to achieve this through DocuSign’s API or configuration settings? Are there any best practices or recommended workflows to handle this scenario?Thank you for your assis

620
M
Newcomer
S
Newcomer
sokinlegalNewcomer
asked in eSignature API
Receiving Envelope is Incomplete error

We are generating contracts for our customers and sending them via DocuSign. However, for one of our customers, the contract wasn’t sent and we are receiving the following error:{'errorCode': 'ENVELOPE_IS_INCOMPLETE', 'message': 'The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line. Error querying recipients for Envelope ID = 1db6cbd9-cd95-4a42-8c43-41ad321bfe77'}This is the first time we have seen this issue. It has worked fine for all our customers till date. Please let us know what’s the exact issue and how can this be fixed.

3905
Michael.Rave
Docusign Employee
R
Newcomer
RukkuNewcomer
asked in eSignature API
DocuSign : We call the token API, but the token creation sometimes results in a non-successful HTTP response code

 When calling RequestJWTUserToken, an exception is returned:Exception: "We call the token API, but the token creation sometimes results in a non-successful HTTP response code," not always.What could be the issue? We are implementing it as shown below.var _apiClient = new ApiClient(_baseurl);token = _apiClient.RequestJWTUserToken(_integratorKey, _userID, _baseurl, Encoding.UTF8.GetBytes(PrivateKey), 1, Scopes);TokenGeneratedAt = DateTime.Now;

300
R
Newcomer
M
New Voice
mehul.shahNew Voice
asked in Salesforce/Apex Toolkit
Salesforce Connect | Connect Object Limit

Hello,  I’m using Salesforce Connect to update records in Salesforce once the envelope is completed. I want to select records where there are multiple conditions in OR. I can’t see any option for OR / NOT. All conditions under SELECT WHERE section are applied as AND.Can we create new connect objects for the same Salesforce object with different conditions ?Is there any limit to how many can we create ?Regards,Mehul Shah

542
M
Community Moderator
Scott.Nieman
Conversation Starter
Scott.NiemanConversation Starter
posted in eSignature API
Consistent resource reference on endpoints - who else is concerned about this?

SCENARIOWhen calling: PUT {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/docGenFormFields With the following payload:  "docGenFormFields": [    {      "docGenFormFieldList": [        {          "value": "2024 Carbon",          "name": "Z1TKH6C",          "required": "true"        }      ],      "documentId": "1"    }  ]}Returns the following error response body:{    "errorCode": "INVALID_REQUEST_PARAMETER",    "message": "The request contained at least one invalid parameter. Value for 'documentId' is invalid."}The endpoint is NOT honoring the standard value of 1, which has been the normal approach for other DocuSign REST endpoints.RESEARCH A DocuSign Blog and documentation states to call the GET endpoint first and map the documentId and other properties to the request payload.  Our application currently uses Redis cache to store all Tab information and JSON PATCH value mappers, therefore this GET operation is overly 'expensive'.  Going into DocuSign/ Envelopes/ Drafts

190
Scott.Nieman
Conversation Starter
H
Newcomer
Harish reddyNewcomer
asked in eSignature API
Is it possible to get JWT access token using single rest API call.

Hi,Currently to get JWT access token we are following these two steps. Step -1: manual action:Currently to get JWT access token we need to manually prepare JWT JSON and here we need to add start time, expire time and need to generate JWT token.Step-2: Rest APIFrom the above generated JWT token we are execute DocuSign API to get the access token “https://account-d.docusign.com/oauth/token?grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<JWT token>. Is there any way so that with the user credentials/data we need to fire only one API to get the access token no need of again manual generation of JWT token. Is there any way to avoid manual action.  

2629
A
Newcomer
A
Newcomer
adarshNewcomer
asked in Docusign Connect
Can't be able to access the webhook feature properly

Hi Team,I have configured the webhook feature in my demo account and include OAuth for integration and security, the webhook attempts to call the API when an event is triggered. However, I got  an error message in the log. Here is the error message: Error: https://dev.api.genpt.com/catalog/debi-service/debi/documentSign/status :: Error - HTTP call to OAuth authorization server failed: HTTP status code = 401, OAuth response = {"fault":{"faultstring":"Invalid access token","detail":{"errorcode":"oauth.v2.InvalidAccessToken"}}}; My question is: What details can I expect in the webhook API call? What should I configure in my service to handle this properly? Can anyone help us with this? Regards,Adarsh

732
M
Community Moderator
V
Newcomer
VettieNewcomer
asked in eSignature API
Docusign Folder is not stable with the word "Completed" when moving to the moved folder

The docusign folder is not stable when I marked the folder complete and moving to the complete status.   The word “COMPLETED” disapears. 

130
V
Newcomer
P
Newcomer
pkrbkrNewcomer
asked in General
Docusign just keeps spinning.

When trying to get a signature or sign a document from a SharePoint library, Docusign just spins forever.  I have tried using Chrome and Edge browsers.  I have tried on different devices and different login accounts and still are having the same results.

1631
N
Community Moderator
N
Newcomer
nomanmujahidNewcomer
asked in Embedded Signing
Want to integrate docusign with Next.js application

Hey everyone,I’m working on Next.js application and I want to create contract there and also i want edit them on my website also want to know about there status so can you guys please tell me step by step guide how can I do this?

1401
karan.kaushik
Docusign Employee
L
Newcomer
LegalOpsNewcomer
asked in Docusign Connect
Error when running PowerAutomate flow that triggers when Docusign envelope changes

Hello,I am trying to generate a flow in Power Automate that is triggered off when a Docusign envelope changes, however, am running into the following error code: The request failed. Response content: '{"errorCode":"USER_NOT_ACCOUNT_ADMIN","message":" User is not an account administrator."}'.After researching this, it’s my understanding that a DocuSign administrator must enable Docusign Connect before a non-administrator can use the Docusign for Power Automate connector to run a flow when an envelope status changes. I have met with the Docusign administrator for my account and we have tried to follow the instructions linked below but do not have a button for “Enable Connect” in the top righthand corner. We do have the ability to click on the “Add Configuration” button, however, upon trying to add a configuration we receive receive another error message stating that Docusign “needs permission to access resource in your organization that only an admin can grant” (see below). Would greatly

2412
L
Newcomer
H
Newcomer
Hejun DengNewcomer
asked in eSignature API
How can I call eSign API without login developer account everytime?

But everytime, when I type : https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id={my_real_client_id}&redirect_uri=https://localhost:8080/callbackDocusign ask the developer account to sign in, otherwise I cannot get the auth code, so I cannot get the access token by the auth code. So it is not a one time thing, everytime, If I want to call some eSign API, I need to login the developer account everytime, why? 

431
E
Docusign Employee

Badge winners

  • 1st Reply Posted
    PCGhas earned the badge 1st Reply Posted
  • 1st Reply Posted
    acranehas earned the badge 1st Reply Posted
  • 1st Reply Posted
    kailamcalisterhas earned the badge 1st Reply Posted
  • 1st Reply Posted
    barbi130has earned the badge 1st Reply Posted
  • 1st Reply Posted
    TB25has earned the badge 1st Reply Posted
Show All Badges
Code of Conduct

Docusign Community

Code of Conduct