eSignature API

Is it possible to use HS256 symmetric encryption algorithm for generation of JWTs? I can only see the asymmetric encryption RS256 used in the walkthroughs. I am trying to consume https://account-d.docusign.com/oauth/token with a JWT to get an access token, but it would be easier if this was possible with HS256 JWT encryption. 

hello guys how are you all   i think that you will be great at alll guys i have very serious issue guys i need such akind of mail that works for docusign developer account creation i have tried many kinds of of mail but not to avail plz let me know that which mail is used for creating the docusign developer account creation

We have Success Factors Recruiting and have used the standard API to connect to Docusign for e-signing the offer letters, work contracts etcThe SF editor is quite poor and despite my efforts to date I cannot get the ‘ok in SF preview’ to be the same in Docusign. I have tried explicit inline CSS, using tables and using CoPilot to help me with variations of simple HTML that is then rendered correctly in Docusign. The Text is too large on the whole when it gets to Docusign.The issue I think is that the SF end is HTML that Docusign tries to convert to a PDF - we use ‘tokens’ or preset field variables in the SF side to populate fields like name date etc.Would be very appreciative of anyone who has navigated this issue or can help with guidance on further steps to trythanksDarren

Hi, We have a problem with the option to decline to sign, using the python sdk with sms authentication, we still have the decline button even when adding the property in to the DocuSign_SignResource file and add the file in the brand admin.In addition, as soon as we click on the decline button, the signature is rejected without any reason being given.Do you have a solution? 

Hi,I'm developing a service that returns a sign-embedded URL for the front end using the .NET (C#) SDK var docuSignClient = await CreateClientAsync();var envelopesApi = new EnvelopesApi(docuSignClient);var recipientViewRequest = new RecipientViewRequest{ AuthenticationMethod = "none", ClientUserId = recipientId.ToString(), ReturnUrl = returnUrl, UserName = recipientName, Email = recipientEmail, FrameAncestors = new List<string> { "http://localhost:7777", "https://apps-d.docusign.com" }, MessageOrigins = new List<string> { "https://apps-d.docusign.com" }};var viewUrl = await envelopesApi.CreateRecipientViewAsync(_docuSignConfiguration.APIAccountId, envelopeId.ToString(), recipientViewRequest);return viewUrl.Url;However, when I use the returned URL with DocuSignJS Focus View, I get the following error:Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'none'". I've

Hi , I am using DocuSign Connect to connect to an API . API uses OAuth and an additional security using an header . How do I pass an additional header to the api ? Thanks for the help .

Hello everyone, I hope you are all well. I am integrating with Docusign using the PHP SDK in Laravel. Everything was working perfectly until a request came up that I should have 2-factor authentication. I did it via SMS. I was able to send 1 envelope successfully. After that, I am only receiving this error:"error_code" => "RECIPIENT_LIMIT_EXCEEDED""message" => "The recipient limit on the envelope has been exceeded. The cumulative recipient limit has been exceeded."I am only sending 1 recipient.A part of my code:Note: I changed the phone number to an example one but I am passing on the real one. $signers = [new Signer([ 'email' => $client->email, 'name' => $client->full_name, 'recipient_id' => '1', 'client_user_id' => $client->user_id, 'tabs' => new Tabs(['sign_here_tabs' => $signHereTabs]), 'email_notification' => new SignerEmailNotifications([ 'send_email' =>

I need to add another record type to dropdown box of NetSuite Docusign Setting (Custom Record). Just appears 6 records type (Customer, Estimate, Invoice, Opportunity, Purchase Order and Sales Order)I want to add Expense Report to send via Docusign for approval 

I am getting blank document in email when sending through API

Hi everyone,Just want to ask this question that’s been bugging me.We currently have an existing package for Salesforce DocuSign Apps Launcher - DocuSign Negotiate and a DocuSign Plan (which I’m not sure of) cause it was purchased 4 years ago. When I tested the Docu Gen Api , it was working on our demo sandbox. But am not sure if that’s going to work in our current live production. So, my idea is -- can we use the existing apps and integration key that’s in our production right now for our custom api integration build or do we still have to go through the api go-live process where we have to push the integration keys from Developer to Production account? Appreciate all your inputs!

Hi,Recently I’ve been trying to set up an integration between DocuSign and an external system.I completed the setup in a Developer account, finished the 20 test connections and passed the go-live review (on the 2nd attempt).However, the integration still does not appear in our Production account’s “Apps and Keys” page.The Apps and Keys page of the Developer account shows our integration, stating that the Go-Live review has passed with a link to the Production account. When this link is used, I’m taken to the empty Apps and Keys page of our Production account.I submitted a ticket to DocuSign support about 2 weeks ago, and they have so far not been helpful at all.Any assistance that could be provided here would be much appreciated.Thanks.

I am attempting to populate the values in a custom tab (type: list) by making a call to a REST API we host.  The use case is that we are having residents of a senior living facility who are signing lease disclosures in Docusign, and we want them to indicate the name of the facility (from a list) and their resident ID from the electronic health records system they use at the facility.  Both of those lists are ever-changing, so they need to be dynamically updated as each envelope is created and sent.My question is, is there a way to dynamically populate a custom tab list by calling a REST API?

1. After filling in the corresponding template in docusgin, is there a "save" or other status? Can the third-party system - Hesi obtain it? 2. After filling in the template and pushing it to Hesi for approval (non-sending status), is there a way to prevent the business party from modifying the contract template content in docusgin to avoid inconsistency with the approval content? 3. For fixed templates, because they are pushed to the third-party system - Hesi for approval, the system will automatically send the contract to the customer for signing, so can the send button of these templates be canceled or restricted? Prevent the business party from sending manually.

Problem:The redirect after signing url can only set through Account Settings.Current situation:Currently, when an envelope is created in our app, an email is sent to the user via DocuSign (Remote signing).A link is also generated where the user can access the Envelope through our app (Embedded signing). So we combine remote and embedded signing.This method works, but there is a problem regarding the redirect Uri definition when signing remotely.The redirect Uri is only taken from the account settings. A defined uri in the branding is ignored, as is a redirect uri that is specified directly during the API call. Additional Infos:In the envelope definition the embeddedRecipientStartUrl in the signer object is set to “SIGN_AT_DOCUSIGN” and the clientUserId is defined which is later used for the RecipientView link generation.

Hi, I need a consultant to do an integration with a CV CRM. Who can help me?

Hi everyone,I'm working with the DocuSign API to track the status of individual documents within a multi-document envelope. My goal is to determine whether each document has been signed separately, but I only see status tracking at the envelope level.I’ve tried the following: Used GET /envelopes/{envelopeId}/documents, but it only retrieves documents, not their status. Checked recipient statuses, but they apply to the whole envelope. Explored webhooks, but I’m unsure if they can provide document-specific updates. Questions: Is there a way to track individual document status separately? Would splitting each document into its own envelope be the best approach? Can DocuSign Connect provide document-specific events? Thanks in advance for your help!

I was wondering if anyone is using DocuSign within their Online Banking Portals. If you do, how are you doing this? What kind of forms are you using? It seems our online banking vendor is not on DocuSign’s list of vendors. Thanks, 

I am using eSignature API with the C# SDK, working in developer/test mode. I have everything working really well, except for my Connect webhook isn’t getting event notifications. I have a working endpoint which tests well using CURL and a mock SIM payload. And the Admin Connect logs show ‘Success’ for every event. But my callback listener nor the server register any incoming requests. In my code I create a list of Envelope events and later add them to the Envelope object’s EventNotifications list object.List<EnvelopeEvent> envelopeEvents = new List<EnvelopeEvent> {    new(){ EnvelopeEventStatusCode = "Sent"},    new(){ EnvelopeEventStatusCode = "Delivered"},    new(){ EnvelopeEventStatusCode = "Completed", IncludeDocuments="true"},    new(){ EnvelopeEventStatusCode = "Declined"}};envDef.EventNotifications = new List<EventNotification> {    new EventNotification("SIM", EnvelopeEvents: envelopeEvents, RecipientEvents: recipientEvents )};I am able to sign my PDF forms an

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”?

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?

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!   

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 productionapp.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') {      t

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

Hello, I want to implement the CSC (Cloud Signature Consortium) API integration (TSP API with CSC), but i can't find any description. Could someone send me a link that describes the integration steps or a documentation? Example is also appropriate if available.

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!