Developer

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"],

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.EnvelopeServi

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

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, s

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?

In my application i am using iFrame to display the docusign embedded view.i am able to complete the sign and read the event and perform operations and navigations in my app successfully in local environment. But the issue is when this is tested in production environment, I am able to sign and redirect url is being called giving 200 response but nothing is happening after that.  same code is working fine with local environment and failing in production environment. I am not understanding is it because of any configuration issue or what.The difference I could see in the network requests is below request is failing. I don’t know exactly this is the problem. PFA belowI am using react router Route to handle the docusign url redirection like below<Routepath={urls.docusignComplete}

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!!

Good afternoon,Currently we are using our production account for development of our product. This is proving limited due to the number of envelopes we require.Is it possible to use the developer sandbox environment for our development purposes using the same integration key? If this is possible would it have a knock on effect on our customers that are already using this integration key?Again, if this is possible would be then have to go through the process of converting it back to a production environment again, i.e. make 20 successful API calls?Thank you in advancePeter HaynesFocus Micro Systems

Hello,I’ve been trying all weekend but I just cannot get this to work, so hopefully the experts here and guide me through what I’m missing.  I’ve tried a number of combinations and nothing is working.  What I want to do, is create an In Person Signing event, where the delivery driver (under the host account) signed the document saying he has delivered the shipment, and then passes the device to the customer for them to sign their portion.  In a mockup, I got it to work but I can’t get it to work in a full run through with an embedded signing request with the PHP SDK.Heres what I got:$document = new DocuSign\eSign\Model\Document( [ 'document_base64' => base64_encode($file_content_in_bytes), 'name' => 'TestFile', 'file_extension' => 'pdf', 'document_id' => '1' ] ); //Find Driver Area

This is regarding the create Envelope flow. There is a default settings at individual account level notifying users to match templates when you upload documents to an envelope. Default settings behavior: Automatic template matching compares uploaded files with saved templates. Based on sensitivity settings, you can apply a matching template to your document automatically or with a notification. The template applies recipients, messages, and signing fields. There is a provision to disable this default settings at individual account level. Could anyone please help me know if there's way to disable this default settings for all users at Docusign level.

How do you disable envelope ID stamping in the document? I have set Envelope id stamping to false, yet it is still not disabled.

Hi! I just published a new YouTube video on setting up Docusign admin settings for your organization. You’ll learn how to secure your account, manage permission profiles, and optimize your setup for a better signing and sending experience. You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎

Hello,We’ve a couple of requirements listed below - To generate a document which needs to have an image embedded on the document. Image is stored inside Salesforce. To generate a document which needs to have an image embedded on the document. Image is the signature of a recipient which has previously signed another document which has similar or almost same information as the new one.I can see that this API - getRecipientSignature | REST API | Docusign - can fetch the user signature. But imageBase64 attribute is not returned in the response. I observed that the signatureType attribute is “rubberStamp” in the response. How to achieve this ? Should I use eSignature API ? If yes, how to get the base64 for recipient’s signature ? Should I use DocGen API ?