Developer

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.

Community poll time…Ask the Expert events are dedicated Q&A sessions that include experts from Docusign. They provide an opportunity for YOU to ask questions, get personalized advice, and dive deeper into industry best practices. What’s something that you would like to learn more about in an upcoming Ask the Expert event?(see your next clue in the reply below this post!)

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

I have never participated in a Docusign API beta. How will this Navigator API beta work and what limitations should I expect?

I need to know whether I will be able to utilize Navigator API with the apps in my production environment during the beta phase.

In order to run some preliminary tests with this new API, I would like to know more about which tools I can expect to be able to currently use it with.

What authentication method is used for the Navigator API? I need to understand if it will be similar to other Docusign APIs I have used before or if it will be different.

I would like to understand more about the functionality of the Navigator API and what I can expect to be able to do with it. Someone please fill me in!

It looks like the Navigator API is currently a closed beta. How do I gain access?

I can not find my signed document in the docusign mailbox. I have two signed document, one I can still access throught security code, another one I totally lost, how can I get the document ? 

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.

 user_data = { "name": user_smartreq.user_id.first_name, "address": "Your Address", } html_content = render_to_string("offer.html", user_data) pdf_file_path = "/tmp/document.pdf" HTML(string=html_content).write_pdf(pdf_file_path) # Step 2: Set up DocuSign API Client api_client = ApiClient() api_client.set_oauth_host_name("account-d.docusign.com") api_client.set_base_path("https://demo.docusign.net") response = api_client.request_jwt_user_token( client_id=env.DOCUSIGN_INTEGRATION_KEY, user_id=env.DOCUSIGN_USER_ID, oauth_host_name="account-d.docusign.com", private_key_bytes=docusign.PRIVATE_KEY, expires_in=100000, scopes=["signature", "impersonation", "extended", "openid", "cors"], ) # api_client.set_access_token(response) print(response.access_token) api_client.set_default_header( header_name="Author

Unlike with EnvelopeViews:createRecipient, which has options to configure clickjacking protections via x-frame-options or csp frame-ancestors, there are no such options for the createSender view.Due to this when displaying the sender view within an iframe element the browser blocks the request.How can we add Clickjacking protection to the embedded sender view to avoid this and add security.Here’s an example of the error on Firefox: 

Hi Team,I am working on a Salesforce integration using the DocuSign Apex Toolkit, and I need to achieve the following:Send multiple documents (a Visualforce page converted to a PDF and a DocuSign template) as part of a single envelope. After all recipients sign the envelope, combine these documents into a single merged PDF.Here's a brief outline of my current implementation:I generate a PDF from a Visualforce page and store it in Salesforce. I retrieve a pre-configured DocuSign template using its unique ID. I use the dfsle.Envelope class to attach both documents to an envelope and send it for signing using the dfsle.EnvelopeService.sendEnvelopes method. I retrieve the status of the sent envelopes using dfsle.StatusService.getEnvelopeStatus.Code Excerpt: Apex Code:dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity(orderRec.Id)); myEnvelope.withRecipients(new List<dfsle.Recipient> { dfsle.Recipient.fromSource(orderRec.Owner.Name, orderRec.Owner.Emai

Need help on how to use docusign js, for a seamless experience on frontend and not use iframe embed as it doesnt helps in UX. I tried examples given on github but they are too old . Can someone help me how to use docusign e sign feature with next js app to render forms using docusign js instead of iframe embed.

{ "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" } ] } } ]} 

We finished our integration with Docusign and we just wanted to create solutions landing page so that our mutual customers can find us on your site like this: https://partners.docusign.com/s/partnerfinder Anyone have any ideas on how to do this?

When trying to start code-example-java app checked out from github, I got the following error. Any clue? Thanks.com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "Groups" (class com.docusign.core.model.manifestModels.ManifestGroup), not marked as ignorable (4 known properties: "Examples", "Name", "examples", "name"]) at [Source: (StringReader); line: 1, column: 80143] (through reference chain: com.docusign.core.model.manifestModels.ManifestStructure["APIs"]->java.util.ArrayList[2]->com.docusign.core.model.manifestModels.APIs["Groups"]->java.util.ArrayList[1]->com.docusign.core.model.manifestModels.ManifestGroup["Groups"])        at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)        at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:1127)        at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProp

How should I embed a web form instance in my app?

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 everyone,We're excited to share that we've integrated DocuSign with Odoo for the first time, and everything is working perfectly! We’ve reached the go-live phase and, after around 20 API calls, we were able to activate it. Now, the app shows as live in production.However, we’re still seeing the message: “This document is for demonstration purposes only.”Are we missing something? Is there an additional step we need to take to remove this message and ensure the integration is fully live?Any insights would be greatly appreciated. Thanks in advance!

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