Docusign 2024 Release 3 Is Live! Discover the New Capabilities
Find answers to your Docusign eSignature API questions.
Recently Active
Hello,I am a developer of a software package that integrates with docusign. Our customers purchase the license and use our admin tool to update the integration information. Our code then uses that authentication to make the calls. We have a certain customer who is asking us to allow them to configure an integration key per user. Meaning they’d like us to enhance our user setup admin to give them a place to save the oauth information per user.I’ve read the documentation and understand that it’s recommended there be a single integration key per integration between docusign and the third party software (our suite). Their reasoning to the best of my understanding is to allow different integrations for users in different regions or countries (I’m not certain the actual differentiation). We proposed enhancing our current admin (where they now enter a single integration key and authentication to docusign) to allow multiple entries, and then they would be able to select an integration from
Hi,I'm working on an Docusign integration using the embedded flow and one of the requirements is after the user signs the document we capture the timestamp of the signature. After reading some of the docs and going through the code samples, there's still something not really making sense to me. How can I fetch the signing metadata after the user is redirected back to my application? I ran the code sample but the only parameter I get is a `signing_complete` event in the query string. I was expecting to get an "envelopeId" as one of the query string parameters so that I could use this parameter to issue a request to the EnvelopeRecipients:list endpoint.
I am using developer account, Below is my configuration and yet on opening the e-sign URL, the recipients are not asked to login. Basically any user with access to the URL is able to put their signature. How to configure this correctly ?
We are using the Embedded View for signing but for some reason the loading spinner is eternalI don't see issues in the console Any idea of what is happening? I'll appreciate any help
Hello community,I have a Bulk Action stuck “in progress” for way longer than it should be. This is done through automation utilizing the Admin API, however, we cannot seem to terminate or make any other request until this user export request completes. Is there any way I can resolve this? Any help is much appreciated.
Yesterday I corrected an Envelope. After I re-sent, it disappeared. I’ve logged a case and explained 4 times that I've searched in every folder I can and used every search filter available. I keep on getting a response to search in a different folder, even though I keep on explaining that I already did the search. No one is helping, they just tell me to do what I already did.
Hello,So I got the API integration almost working perfectly, just one hangup which I hope I’m just missing a setting somewhere.I’d like to setup an In-Person Signer but without their name pre-filled. We are delivering goods to a company, so we know the company name and general email inbox to send the documents. We just don’t know who is going to be there to receive the goods, could be John Smith, Jack or Jane Doe. The In Person Signer is able to change to their name when signing, but would be nicer to have it already blank.How can we accomplish this? Thanks,Brian
const jwtLifeSec = 24 * 60 * 60; // 1 day in seconds (3600 * 24) const dsApiClient = new ApiClient();dsApiClient.setBasePath(this.configService.get<string>('docusign.base_path'),); const results = await dsApiClient.requestJWTUserToken(this.configService.get<string>('docusign.integration_key'),this.configService.get<string>('docusign.user_id'),[this.configService.get<string>('docusign.scope')],this.privateKey,jwtLifeSec,);I added like that ti’s not working. it’s always return expire_in : 3600I wana more than. How can I do that Please someone help me.
{ "emailSubject": "Please DocuSign This NDA for ABC Company", "emailBlurb": "Please let us know if you have any questions.", "status": "sent", "templateId": "{{NDA Template}}", "customFields": { "textCustomFields": [{ "name": "entityID", "value": "1234" }] }, "templateRoles": [ { "roleName": "Customer", "email": "{{Signer Email}}", "name": "{{Signer Name}}", "tabs": { "textTabs": [ { "tabLabel": "company", "value": "ABC Company" } ] } } ]}
Hi,One of my documents failed to deliver because of an incorrect e-mail addressBut all the API response lists is that the envelope has status “sent”:{ "resultSetSize": "3", "startPosition": "0", "endPosition": "2", "totalSetSize": "3", "nextUri": "", "previousUri": "", "envelopes": [ { "status": "sent", "...": "..." }, {...} ]} I would like to recognize an issue like this so I can report it in the module we’ve been building, but have been unable to do so with “listStatusChanges” or “Envelopes:Get”. Is it not the status?Am I missing some other field?Do I need a different request?
Hello,I’d like to send a draft envelope via DocuSign API. The application uses ASP.NET Core.What I’ve done so far, I retrieved the envelope with GetEnvelope and set Status as “sent”, then I called Update method to change the envelope status.The envelope contains one Document, and 2 Recipients. And I received an error as follows : Error calling Update: {"errorCode":"INVALID_REQUEST_PARAMETER","message":"The request contained at least one invalid parameter. Value for 'purgeState' must be 'documents_queued' or 'documents_and_metadata_queued' or 'documents_dequeued' or 'documents_and_metadata_and_redact_queued'."}I tried to set PurgeState as “documents_dequeued” (1) or “documents_queued” (2) but I received different error messages : (1) documents not in the purge queue, and (2) the envelope must be completed first, which is not the case.I just want to send the draft envelope with documents to sign after storing the envelope id in our database, so I can keep track of the envelope status in
Hello DocuSign Community,I am using the DocuSign Monitor API in my developer account and have noticed an unusual behavior in the API responses. Specifically, records with the data field having attributes such as IDs, IPs, or user agents are returned as a list of individual characters rather than as a single string.For example, instead of:"userId": "abab12"the API response gives: "userId": ["a", "b", "a", "b", "1", "2"]This behavior is not consistent across all records and only occurs in certain records. Is this the intended behavior of the API, or could it be a potential bug?Note: I have observed this behavior at least for ‘Alert’ records related to ‘Envelope’ activities.I have attached a screenshot for reference.Docusign Monitr API response
Once i submit the docusign application for “Review”, review gets passed and status c, when i hit “Go live” then the docusign team would manually review my application or how does the go live process works, please explain & how many days it takes!!
Back to Docusign.com
