Developer

Hello DocuSign Support Team,We are using the DocuSign Webforms API and need assistance with the following steps after a user completes and signs the webform:Once the form is signed, we want the signed PDF document to be automatically sent back to our system. The signed PDF should then be attached to a specific case in our system for record-keeping and further processing.Could you please provide guidance on how to configure this process using the Webforms API, specifically on how to retrieve the signed PDF and attach it to a case?

please update the link of DocuSign data residency:https://www.docusign.com/trust/privacy/data-mgmt-privacy FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant.📊 DocuSign Community Leaderboard Top 5 contributor.🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Hi, all! I’m recently encountering an issue where the access code prompt isn’t appearing for signers that I add during the “CreateSenderView” step of my workflow. Workflow: Person A creates an envelope through an external DocuSign integration and adds Signer A as a recipient of said envelope. Person A proceeds to the sender’s view on the DocuSign site. (This is done using envelopesAPI()->createSenderView()) Person A adds a new signer, Signer B. Signer B is assigned an access code. Person A returns to the external DocuSign integration and creates a recipient view for Signer A to sign. (This is done using envelopesAPI()->createRecipientView()). Signer A is prompted to enter their access code, enters, and completes signing.  Person A creates another recipient view for Signer B once Signer A has finished.  Signer B is not prompted for an access code and doesn’t see the fields added for them to sign.Note: Person A is authenticated in this integration using OAuth and has a different em

Hi,I have a usecase where contracts are created using a salesforce workflow through a user and I am trying to purge those contracts via APIs. While purging documents I am getting an error that only the sender can add documents to purge queue.I am purging documents via APIs and docusign does not allow to add API user to act on behalf to docusign Users. Is there a workaround for this which would enable be to purge documents created by other users?

Hi Dev Folks,i have posted my problem here, can any one help me to solve that issueThanks.

Hi,I am implementing docusign envelope/ esignature api using docusign SDK,I have implemented CreateEnvelopeAsync() successfully, but if i had put wrong email address for recipient signer then recipient signer email bounced or autoresponded. in that situation i am updating recipient signer with sign here tabs, and recipient updated successfully. but when signer opens email and going to review envelope and to do sign then the sign here tab not displayed with AnchorString at specific AnchorYOffset and AnchorXOffset on the document.So please provide any solution.Thanks. below the code of c# .net core for update recipient and tab public async Task<RecipientsUpdateSummary> UpdateRecipientsWithTabs(string envelopeId, DocuSign.eSign.Model.Recipients recipients, UpdateRecipientsOptions options = null) {     try     {         RecipientsUpdateSummary updateSummary = null;         OAuthToken authToken = AuthenticateWithJwt();         Account acct = GetDocusignUserAccountInfo();         var d

Dear all, I need to configure for US colleagues the next API connection. I look for the following but for all available US Pen in DocuSign : {"signatureProviderId": "412","signatureProviderName": "transsped","signatureProviderDisplayName": "Trans Sped SAFE/eIDAS digital certificate","priority": "2","isRequired": "false"}Normally I use the API explorer tool but it doesn't catch the US pensDigiCert US Signer Held Notary U.S. USAID PIV PIV Smart CardsRegardsolivier 

We are using the apex toolkit in Salesforce to generate documents and then create an envelope. However, once the envelope has been created, we would like to allow the user to view the envelope and make adjustments before actually sending. Is there any way to provide the user with (or redirect the user to) the Send with Docusign view after creating an envelope with the apex toolkit? A screenshot of what I’m talking about is below.  

We received an email from the above address and our inquiring if this is a legitimate email address, since it states that a grand jury subpoena has been requested.  Hoping you can determine if it’s a scam or if we will need to respond to the email.Thank you. 

Hi everyone,I'm developing a DocuSign extension and need public legal documents to test it. I'm looking for real legal documents that are free and available for testing purposes, without using any private or confidential information. Any suggestions would be greatly appreciated. Thank you!

Hi All, I am having a basic query related to Docusign API. This query is more of API related rather than Docusign related, however still posting here as it concerns Docusign. I am following this video for querying docusign API. Here at timestamp 5:44 the API body is passed as ‘x-www-form-urlencoded’(snapshot attached). However, I am making this API call using my automation tool(Uipath) which lacks the ‘x-www-form-urlencoded’ interface similar to postman. It is possible to pass the body as JSON instead of ‘x-www-form-urlencoded’? I tried passing JSON body as below but it didn’t work. {“grant_type”: “authorization_code”, “code”: “<code>”} Thanks! 

We have successfully sent 20 API calls, submitted them for review, and marked the first task as complete. However, after submitting for go-live, it is still showing as 'Pending Approval.' Is there anything we need to do to expedite the approval process?

 Hi, I have developed a Screen Flow for sending contract documents, utilizing the 'Send With DocuSign' action (apex-dfsle__EnvelopeConfigurationBulkRequest). Below is the screenshot for reference.(2- Flow element) The envelope is sent immediately when the flow reaches this element step. I want to allow the user to preview the template before it's sent. The template's options have been set to 'Place Fields'.(1- Options) However, it behaves as if it's set to 'Send Now' when I send it through Flow. Is it possible to preview the envelope before sending, as if we are sending it using a button in the page layout? Thanks. 1- Options 2- Flow element 

Hello everyone!I’m developing an integrator to send documents from our ERP to DocuSign for digital signatures. The email sending is working, but I’m encountering an issue with WhatsApp sendingMy project uses Node.js with TypeScript, so I’ve typed the recipient using the interface exported from the @types/docusign-esign library. However, this interface doesn’t include the “phoneNumber” attribute, which is needed to send the phone number object as shown in the example project (see the images below).My Project:Node.js eSignature REST API Example: Could this be a missing attribute in the library’s interface?

Hello,I am trying to implement a change in the docusign process. Our docusign is registered with a service account and all templates are created using that service account. When a user in Dynamics CE generates a docusign letter it sends out the document from the service account email address. So the receiver of the email when returns the document it goes back to the service account. This is creating a bit of confusion as we have multiple people on the team who send out documents from docusign. I tried to change the email address on the docusign user entity in MS dynamics and created the user with the same email in docusign. It send out the email from the users email address XXX-username@email.com but it is not working for all users. Thanks in advance.!

I have an app key setup and live in production. When a user clicks a button on my page I create an envelope and send a PDF with a request to Docusign for the user to sign. This has been working for several years. Is it possible to use the same app key to send a different PDF for signing, or do I have to create a separate app key?The return URL will be different for the other PDF, but it looks like I can add multiple return URLs to the app key configuration.

I am following the tutorial from this page: How to get an access token with Implicit Grant | DocusignI have an href to the following URL: https://account-d.docusign.com/oauth/auth?response_type=code&scope=impersonation%20signature%20organization_read%20user_read%20account_read%20dtr.profile.read&client_id=#redacted#&redirect_uri=https://localhost:7054/dsauthWhen I follow this href I am directed to log in and grant permission.  I am successfully redirected back to https://localhost:7054/dsauth.  I capture the token from the “code” query parameter.When I try to use that token in the header to list users, I receive 401 unauthorized.  I can’t find any documentation to help resolve the problem, and as far as I can tell I’m following the example perfectly.I am using C# and RestSharp to make the calls.  Following is the relevant code: async void GetUsers() { var client = new RestClient("https://account-d.docusign.com/oauth/userinfo"); var request = new RestRequ

We are currently using DocuSign keys in Oracle Integration Cloud (OIC) for a KYC process that is live and functioning well. Now, we have a new requirement to implement DocuSign for a separate employee onboarding process. I have a few questions regarding this: Since we already have a DocuSign key in the production environment for the KYC process, can we reuse the same key for the employee onboarding process? The flow for both processes is similar: Define a template in DocuSign (the templates differ for each process). Use these templates in our integration. Once an envelope is signed (by a customer or employee), the information is processed via a "Connect" configuration. For these two separate processes, can we set up two independent "Connect" configurations in DocuSign? If having two "Connect" configurations is possible, how can we ensure they do not overlap and that each configuration only handles the relevant process?

I have made a number of API submissions during PoC process, these have been delivered either to the Sent or Drafts folders. I have gathered the envelopeId’s and can access the envelopes directly, however they do not appear in the Agreements view. (The latest viewed one does appear if I navigate to Sent/Draft via the info on the envelope detail view, but it only shows the one envelope). How can I see a list of all my Drafts?  PS> Is it possible to select and send multiple drafts at once?

Is is compulsory to create a developer account and then migrate to production after submitting app for review? Can I create app in production environment directly to use DocuSign API?

Here is my scenario:In Salesforce, I have an Opportunity that can be related to multiple Opportunity Documents (custom object). There are three Opportunity Documents: Non-Disclosure Agreement, Contract, and Onboarding Policy Agreement. We created Gen templates for each of these.Each document may have a different person that needs to sign. For example, Bob may need to sign the Non-Disclosure Agreement and Contract while Alice needs to sign the Onboarding Policy Agreement. As such, we have a "Signer" field captured on Onboarding Document.Lastly, there could be multiple of one document on an Opportunity that needs to be signed. For instance, we may have two copies of a Non-Disclosure Agreement that needs signature for one opportunity.Our thinking is that we could create an LWC that leverages the apex toolkit to allow a user to, at any point, select one or more Opportunity Documents and then click a button called Generate Envelope. Using the Bob/Alice example above, the LWC (referencing th

Hi! I just published a new YouTube video on integrating Excel Desktop with Docusign for seamless document automation.You’ll learn how to map Excel data to Docusign templates, generate envelopes automatically, and review drafts—all without manual entry. Plus, I’ll explain why Excel Online might be an even better choice for certain workflows. You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

Hello,I am trying to implement a counter-signature functionality in DocuSign sandbox env and encountering an issue where the envelope does not transition to the "Completed" status as expected. Below is the workflow I am attempting to implement and the problem I am facing: Template Setup: My template has two roles: Customer (Role 1): Configured as need to sign, with required text fields and a signature field. This role has a routingOrder of 1. Company (Role 2): Configured as need to sign, with required text fields only. This role has a routingOrder of 2. Envelope Creation: At the time of envelope creation, I programmatically fill all required text fields for the company role using the API ( also try to fill text fields after the customer signature complete ) . The customer role receives the envelope and is expected to sign and complete their part. Customer Signing: The customer role completes all required fields and signs the document. At this stage, the customer should not se

Hi All, I am working on creating an envelope using API explorer in developers.docusign.com. I am able to send the document if I am not attaching any tabs to the document. However I am getting the below error if I am attaching tabs to the document. Kindly assist me with this issue. I have updated the url and body of my request. {  "message": "Bad Request",  "response": {    "errorCode": "UNSPECIFIED_ERROR",    "message": "Object reference not set to an instance of an object."  }} URL:/restapi/v2.1/accounts/<accountId>/envelopes Body:{  "documents": [    {      "documentBase64": "<base64ForTheDocument>",      "documentId": "1",      "fileExtension": "pdf",      "name": "document",      "tabs": {        "signHereTabs": [          {            "anchorString": "Signature:",            "documentId": "1",            "anchorXOffset": "1",            "anchorYOffset": "0",            "anchorIgnoreIfNotPresent": "True",            "anchorUnits": "inches"          }        ]      }    

Hello, I am working on developing a web application that requires integration with Docusign to request signature of some documents, just to put you in context my application sends an SMS to a user and depending on the user's response the document signature request must be sent, the request must be sent by SMS and also the entire envelope creation process must be done in my API without requiring user intervention, so I want to know if this project idea is reasonable and what authentication method I should use for this project. I would greatly appreciate if you could help me with this question. I only have to add that my API is being developed using NodeJs. Thanks in advance.