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.

  • 906 Topics
  • 5 Replies
885 Topics
C
Newcomer
cloudopsenableNewcomer
asked in eSignature API
Getting wrong embedded event after signing is complete in the callback url

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

732
C
Newcomer
R
Newcomer
roger320Newcomer
asked in eSignature API
Error message: Account lacks sufficient permissions. In-session permission required when specifying a captive recipient.

Our B2B software has an embedded e-Signature integration with DocuSign where we allow our software users to create envelopes and tag recipient fields for other software users. Our integration utilizes a “system user” who authenticates to the customer’s DocuSign account and all subsequent envelopes are created and signed on behalf of that system user. For the error message: Account lacks sufficient permissions. In-session permission required when specifying a captive recipient. the customer’s system user has the “DS Admin” permissions profile. I welcome any ideas where the client’s DocuSign Admin can go to enable a “in-session permission”?

722
R
Newcomer
R
Newcomer
RutujaNewcomer
asked in eSignature API
DocuSign production account "consent_required\" error

I have created a application in developer account and verified it after making 20 API calls. I am using JWT authentication. After that I logged in to my production account and granted access again using https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=<YOUR_CLIENT_ID>&redirect_uri= <MY_REDIRECT_URL>.I also updated the UserId and API Account ID. Now when I am trying to send document to sign using my application, I get error {"Error while requesting server, received a non successful HTTP code with response Body: {\"error\":\"consent_required\"}"} How can I resolve this issue? Will I get this error of I don’t have plan with API Access?

591
E
Docusign Employee
H
Newcomer
hopegNewcomer
asked in eSignature API
Getting started ussing DocuSign with Lone Wolf

Hi Community, Does anyone use DocuSign with Lone Wolf here? I need help with my first e-signing and sending docs out for e-signing. According to Lone Wolf, my DocuSign account is already integrated with Lone Wolf. Lone Wolf reps are not trained for DocuSign support. I’ve put in a support request to DocuSign. If you’re so inclined, Help!

151
Hengfeng Ge
Frequent Contributor
C
Newcomer
carlos.torres140Newcomer
asked in Docusign Connect
Testing Webhook connect using localHost URL (URL to publish)

Is there any way to set the localhost in the “URL to Publish” section? I need to test my localhost url and looks like its not possible. Do you recommend any tool to create a fix url temporary while I’m running my test ? I read about ngrok for example but I’m not sure if its secure.

453
C
Newcomer
D
Newcomer
Dave WDXNewcomer
asked in Docusign Connect
How do I link one of my Apps and Keys to only one of my connects

I am currently trying to set up my DocuSign account so I have on App & key for each of our pre prod environments (Dev,test,staging) I would like to have three different keys, one for each environment. In turn these three different environments will have a connect for each one, how do I specify that a certain app should only use a certain connect, I can add them all into each one, but it gives me tonnes of failed messages

252
M
Community Moderator
R
Newcomer
ribeiroanamrbNewcomer
asked in eSignature API
error when downloading the envelope

When downloading the envelope via the application, the completed fields are not shown in the document and the signatures are not shown eithernote: I am using the development environment, my account is not yet in production app . get('/envelopes/:envelopeId/documents', async (req, res) => { await checkToken(req); const envelopesApi = getEnvelopesApi(req); const envelopeId = req . params . envelopeId; my code: try { const docs = await envelopesApi . listDocuments(process . env . ACCOUNT_ID, envelopeId); res . json(docs); } catch (error) { console . error('Erro ao listar documentos:', error); res . status(500). send('Erro ao listar documentos'); } }); app . get('/envelopes/:envelopeId/documents/:documentId', async (req, res) => { await checkToken(req); const envelopesApi = getEnvelopesApi(req); const { envelopeId, documentId } = req . params; try { const envelope = await envelopesApi . getEnvelope(process . env . ACCOUNT_ID, envelopeId); if (envelope .status !== 'completed') { throw new E

471
T
Docusign Employee
U
Newcomer
umar_clickfunnelsNewcomer
asked in eSignature API
Go Live Review declined without any reason

Hi everyone, I need some help with the DocuSign Go-Live process. I’ve been trying to get my Integration Key (5adb2409-a79c-4616-8a0c-79de07f2d449) approved for production for over a month, but I keep getting declined without any reason provided. Here’s what I’ve done so far:✅ Read and implemented all troubleshooting documentation ✅ Tried with multiple Integration Keys✅ Passed automatic review (20 successful API calls, no polling)❌ Go-Live manually declined multiple times (first two attempts took 3-5 days, latest one was rejected within hours)❌ No emails or notifications explaining the rejection I’m stuck and don’t know what else to fix. Has anyone faced this before? How can I get feedback on why the integration is being declined? Any insights would be greatly appreciated!

311
M
Docusign Employee
D
Newcomer
developerXHWNewcomer
asked in Go-live
promote to production got review declined

I want to switch to production, submit the review and it shows review passed . Then I promote to production and selected a production account, which has the same email address as the development account,After a period of time， I receive a [review declined], but there are no error messages，I don't know how to improve it

402
D
Docusign Employee
sofian_solusign
Troubleshooter
sofian_solusignTroubleshooter
posted in General
How to Prefill Documents in Docusign

Hi! I just published a new YouTube video on how to prefill Docusign documents before sending them, ensuring accuracy and saving time. You’ll learn how to: Prefill documents manually without sending them to yourself first. Use recipient fields vs. pre-filled fields for different scenarios. Automate pre-filling using CRM or spreadsheets. Track document status and auto-store completed files. Eliminate repetitive data entry and streamline your document workflows! You can find it here: Sofian Saoudi | Founder @Solusign Consulting - Docusign Partner Need help with Docusign? Book a call with me 🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

180
sofian_solusign
Troubleshooter
F
Newcomer
ForeveruniqueNewcomer
asked in eSignature API
Revolutionizing Data Ownership with SecureConsent

In today’s digital world, protecting personal and business data is more critical than ever. SecureConsent is a solution designed to safeguard data through encryption, access controls, tracking mechanisms, and blockchain ownership proof. I’m exploring ways to integrate real-time monitoring and user-controlled access to ensure transparency and security. How do you think blockchain can enhance data ownership rights? What challenges have you faced in securing your digital assets? Let’s discuss how we can create a more secure and user-empowered data ecosystem! © 2024 Desiree A. Robledo, Diversity Connected, Connected Communities LLC.

180
F
Newcomer
U
Newcomer
UniqueUser1Newcomer
asked in General
Reassignment from One Contact to Another

My Salesforce org has DocuSign Package integrated in it and I have a contact who is the recipient of email that is sent. That recipient changes the signer from himself to another contact that is available in the org as another contact. My question is, which object, field shows these changes? Tried with dfsle__Recipient__c object and no changes in fields value were shown before and after the reassignment. Further no new dfsle__Recipient__c record were created other than the one initially created.

322
M
Community Moderator
S
Newcomer
surfjabroniNewcomer
asked in eSignature API
Dayforce Popups for Docusign

Hi everyone, Docusign newbie here. Not sure which category to post this in so apologies in advance on that one. I work for a MSP. Our client uses Dayforce HR platform. In order for docusign signature box to pop up in browser we want to assign an Azure policy. The HR website is https://us242.dayforcehcm.com:443Should I allow this URL https://na2.docusign.net/Signing/?insession=1&ti=f53d6cb0d3f64a96a295c0be724e7e9eor what should it be shorttened to? Thanks in advance!

382
M
Community Moderator
C
Newcomer
csannicNewcomer
asked in Salesforce/Apex Toolkit
DocuSign in Salesforce - combine certificate of completion and document in returned file

We’re using DocuSign in Salesforce. After a document is signed, we get the signed document and certificate of completion as two separate files in the Salesforce record. We’d like this to return as one file--the signed document with the certificate of completion appended to the end. Is that possible? I have the setting Attach certificate of completion to envelope checked, but that isn’t helping.

625
M
Community Moderator
S
Newcomer
SravyabmNewcomer
asked in eSignature API
Updating the Envelope with new documents and sending the Envelope does not reflect the updated documents in Docusign

I have installed Docusign App Launcher in my Salesforce developer org. I am using the generate_and_convert REST API to generate the documents and then I am sending these documents using sendEnvelope method of EnvelopeService ApexToolkit. I have the requirement of getting a list of documents as and when it comes and then updating them onto an Envelope and finally send the Envelope. For this I have created an empty envelope with a recipient and sent the Envelope with Boolean false. Contact myContact = [SELECT Id,FirstName,LastName,Email,Phone FROM Contact WHERE Name = 'Test Contact']; dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity('mysourceId')) .withRecipients(new List<dfsle.Recipient> { dfsle.Recipient.fromSource( myContact.FirstName + ' ' + myContact.LastName, myContact.Email, myContact.Phone, 'Signer 1', new dfsle.Entity(myContact.Id)) });myEnvelope = dfsle.EnvelopeService.sendEnvelope(myEnvelope, false); Once this Envelope is saved in Docusign...

251
Ivan.Dinkov
Docusign Employee
M
Newcomer
matheusmouraNewcomer
asked in eSignature API
Document Generation TextField Line Break

Hello! I’m currently automating our contract generation process using DocuGen (DocuSign eSignature) but have recently encountered an issue. Specifically, when I populate a text field (e.g., {{test_field}}), the field no longer accepts line breaks. This functionality was working correctly about a week ago. Could you please advise me on how to resolve this issue? Thank you!

831
karan.kaushik
Docusign Employee
M
Newcomer
michael.tomNewcomer
asked in eSignature API
eSignature API using PFX?

Hi everyone, I’m trying to integrate with the eSignature API with a product that has Docusign integration, but it might be old because it requires a PFX file. Is anyone able to help confirm whether integration with eSignature using a PFX file is still available? If so, does anyone know how to obtain the PFX file? We have the public and private key files, as well as the certificate, but the generated PFX (using open SSL) does not work. Thanks Mike

442
B
Docusign Employee
R
Newcomer
ribeiroanamrbNewcomer
asked in eSignature API
download envelope documents

The files are downloading but the document does not show the signatures, the filled fields are blank. I want the complete document, with the filled fields and the signatures, can someone help me? my code: app . get('/envelope/:envelopeId/documents', async (req, res) => { await checkToken(req); let envelopesApi = getEnvelopesApi(req); const { envelopeId } = req . params; try { let results = await envelopesApi . listDocuments(process . env . ACCOUNT_ID, envelopeId, null); res . json({ envelopeId: results .envelopeId, documents: results . envelopeDocuments . map(doc => ({ documentId: doc .documentId, name: doc .name, type: doc .type, uri: doc .uri })) }); } catch (error) { console . error('Erro ao listar documentos do envelope:', error); res . status(500). json({ error: 'Erro ao listar documentos do envelope' }); } }); app . get('/envelope/:envelopeId/document/:documentId', async (req, res) => { await checkToken(req); let envelopesApi = getEnvelopesApi(req); const { envelopeId, documentId

90
R
Newcomer
S
Newcomer
sadiomanhneNewcomer
asked in eSignature API
Overriding SignerAttachmentTabs optional property is not working as expected

I created a template with a SignerAttachmentTab (optional) inside it on Docusign. Before creating an envelope, I get the SignerAttachmentTabs of a signer and override the value of the property Optional to make it become required. But when I sent an envelope, the UI was confusing me. There were 2 overlapping tabs. Do you guys know a better way to control the property Optional before creating an envelope?

212
S
Newcomer
V
Newcomer
vaas070Newcomer
asked in eSignature API
Auto signing implementation

I have been trying to place signature image directly without having the user to sign it. I have used sign here tabs and added stamp tabs in it. But in the received document, it is still expecting the user to manually sign it. I have researched enough,I am not finding any resource which solves my problem. here is the code took some help from AI. This does seem to work. Is it even possible to achieve this? If yes, how? ```args = { "account_id": jwt_values["api_account_id"], "base_path": jwt_values["base_path"], "access_token": jwt_values["access_token"],} api_client = create_api_client( base_path=args["base_path"], access_token=args["access_token"],) env = EnvelopeDefinition( email_subject="Please sign this document set", )env.documents = []document2 = Document( # create the DocuSign document object document_base64=base64.b64encode(file_bytes).decode('utf-8'), name='Sample Document', file_extension='pdf', document_id='1')env.documents.append(document2) signer1 = Signer( email='srinivasst

251
S
Docusign Employee
T
Newcomer
t.bas.ppsNewcomer
asked in eSignature API
How are DocGenFormFields supposed to be set up when creating a template and envelope?

I’m trying to generate a document with parameterized where i’m creating a template when it doesn’t already exist, generate the envelope, and update the fields.The fields in the document are being set as {{FieldName}} as suggested by documentation, but the GetEnvelopeDocGenFormFields() for the envelope is returning no fields and any attempt to use the update throws an error. i’ve added a simple version of my code bellow.How is the sender field parameterization supposed work? public async Task TestCode() { var fileName = "test_document"; string docBase64; using (FileStream fs = new FileStream($"E:\\{fileName}.docx", FileMode.Open, FileAccess.Read)) { using (var ms = new MemoryStream()) { fs.CopyTo(ms); var bytes = ms.ToArray(); docBase64 = Convert.ToBase64String(bytes); } } // Add Template var template = await templatesApi.CreateTemplateAsync(accountId, new EnvelopeTemplate() { Name = "Test Template", Description = "Test Template Description", Shared = "false", Recipients = new() { Signe

410
T
Newcomer
T
Newcomer
TechniqueNewcomer
asked in eSignature API
Bad request - Docusign JS embeded - The form is signed but "sessionEnd" is not triggered

How to reproduce my bug : Generate a enveloppeView Sign the enveloppe The signing.on(‘sessionEnd’) isn’t triggered I was a valid docusign integration and it works on dev environnment

502
B
Newcomer
D
Newcomer
dgh11Newcomer
asked in eSignature API
I managed to connect to dev API but i cannot do same on Production

Are these url s correct? $baseUrl = "na3.docusign.net/restapi"; $consentUrl = "https://account.docusign.com/oauth/auth?response_type=code&scope=$scope&client_id=$clientId&redirect_uri=$redirectUri"; the JWT headers $payload = [ 'iss' => $clientId, 'sub' => $apiUserId, 'aud' => 'account.docusign.com', 'scope' => 'signature impersonation', 'iat' => $now, 'exp' => $now + 3600 // 1 hour expiration ]; $tokenUrl = "https://account.docusign.com/oauth/token"; $config=$apiClient->getConfig(); $config->setHost('https://na3.docusign.net/restapi');

201
Ivan.Dinkov
Docusign Employee
M
Newcomer
MacitNewcomer
asked in Go-live
How to upgrade Basic API plan

Hi, I would like to upgrade my Basic API plan so I can make an integration to Go-Live on production and remove the watermark on the envelopes. Can someone tell me how to do this because when I go on ecom.docusign.com (logged in or not) I can’t choose a higher plan. And if I go to my admin account at “Billing and plan” I can’t upgrade there aswel

402
M
Newcomer
S
New Voice
sammy_rabieiNew Voice
asked in eSignature API
EnvelopesApi's create_envelope responds USER_AUTHENTICATION_FAILED: One or both of Username and Password are invalid. Invalid access token

I’m getting “USER_AUTHENTICATION_FAILED: One or both of Username and Password are invalid. Invalid access token” when I call create_envelope. I know the access token is correct after it’s generated because “get_user_info” is returning the correct account id and username, but by the time I try to create the envelope, it says the access token is invalid. in the code below, after “request_jwt_user_token”, the print commands are displaying the correct account id and username. I have been stuck on this issue for a few days now and any help would be GREATLY appreciated! Code: import base64from cryptography.hazmat.primitives import serializationfrom docusign_esign import ( ApiClient, EnvelopesApi, EnvelopeDefinition, Signer, Tabs, SignHere, InitialHere, Recipients, Document,)from docusign_esign.client.api_exception import ApiExceptionfrom django.conf import settings scopes = ["signature", "impersonation"]base_url = settings.DOCUSIGN_BASE_URLintegration_key = settings.DOCUSIGN_INTEGRATION_KEY

4883
S
New Voice

Most helpful members this week

Badge winners

Show All Badges

Popular tags

Code of Conduct

Docusign Community

Code of Conduct