Developer

I am switching to a different email application and need to convert my MBOX files. What is the safest way to convert them without losing emails, attachments, or folder structure? 

I am a developer/consultant setting up a DocuSign API integration for my client using Make.com. I have a question about the Go-Live verification process.Here is my situation:- I created a DocuSign Developer (Sandbox) account under my own name (Abdul Rehman) and my own email- My client has an active DocuSign eSignature Standard production account under their business email (*****@*****.***)- The production account admin is Edgar Samuel Cornejo Farias - I created an Integration Key in my developer account and submitted the Go-Live form- During the Go-Live PowerForm verification process, it is asking for ID verificationMy questions are:1. Can I (Abdul Rehman) complete the ID verification as the Application Manager/Developer, while linking the integration key to my CLIENT's production account (Account ID: xxxx)? Or does the person verifying their ID need to be the admin of the production account?2. If the Application Manager and

Hi, I’m still in sandbox.My use case is we send the envelope to a signer. After they complete signing, we need to fill other fields for the second signer before they view the document. I’ve implemented sending the the envelope to the first signer with pre-populated fields. But after the first signer completes and I update the fields for the second signer, the second signer still sees those fields as empty.I’ve tried both envelopesApi.updateRecipients()andenvelopesApi.updateTabs()Neither of those made the fields pre-populate when the second signer loaded up the doc.Is this possible to implement? How should I go about it?

We're using the EnvelopeViews: createSender endpoint to embed the tagger/sender view in our application. We need to control the display language of the embedded sender view based on the user's account language.Following the documentation, we append the locale query parameter to the URL returned by the API: https://app.docusign.com/...?locale=deThis approach works correctly for the recipient view (createRecipientView) — the signing UI displays in the expected language.However, for the sender view (createSenderView), the locale parameter appears to be ignored entirely. The UI always displays in English regardless of the locale value.Our setup:Using the new API format with EnvelopeViewRequest (settings object with startingScreen: "Tagger", sendButtonAction: "redirect", etc.) The locale parameter is appended as a query parameter to the returned URL (e.g., &locale=de) Tested with multiple locale values (de, fr, etc.) — none ta

Hello, When setting up a tool using the DocuSign API, do you need to login and sign with a personal account?In our case we are setting up a DocuSign integration with our internal Software for customers.So a customer must personally sign and be liable for all signatures done in Docusign under that application?

Hello, I had a docusign working application in development environment where I was calling apis from nodejs application. I created a JWT key using the call back by going here : https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature&client_id={iKey}&redirect_uri={callback}I used integration key and user id as shown on my screen. This setup was working fine.  Then I moved to a new setup by just promoting the application to production. For this I had to add a new member to my account as they have administrative rights to my account. Once I did that, I am not able to make any requests. I even updated the docusign links in my app as follows: DOCUSIGN_AUTH_SERVER="account.docusign.com"DOCUSIGN_BASE_PATH="https://na3.docusign.net"I also updated the JWT by hitting account.docusign.com instead of account-d.docusign.com in the above but I am still getting error of: DocuSign error data:

I am calling Docusign EnvelopeService to send emails with documents. How can I track if the email is bounced back due to non-existed email address? 

I am in the admin - > integration section.  I was expecting to see something liek API and keys in the title  . I did try the app and keys, but the only option is Authorization Code Grant. I don;’ see an way to change it,   Figure 2.   What am I missing?Figure 1Figure 2  

I have the trial for Docusign for salesforce. I have create a template and a button to generate a document. I have all the Docusign permission sets including administrator and each time I go to click on te button to generate the document I get this error Failed to initiate document generation. Please try again later or contact your administrator for assistance. You must have Docusign generator permissions to perform this operation Is anyone able to help ? The online chat is not working on the DocuSign website

We currently use a DocuSign button on the Salesforce Contact record to manually send DocuSign envelopes, and that process works correctly.We are now automating this workflow so Salesforce will:Automatically create a DocuSign envelope using a DocuSign Template Generate and store the recipient signing URL on the Contact record Sync that URL to Account Engagement (Pardot) Use the signing link inside Account Engagement emails However, we are unable to generate the signing URL programmatically, and we need assistance identifying the correct configuration or method to create the Recipient View (signing link) via Salesforce automation.

Hi, We have developed an integration with the DocuSign REST APIs.Over the past few weeks, we’ve observed that a few POST /envelopes requests have taken longer than usual to respond, resulting in timeouts in our system. However, these requests eventually complete successfully on the DocuSign side.To better calibrate our timeout configuration and avoid failures, we would like to better understand the expected performance characteristics of the POST /envelopes API.We would appreciate it if you could share the p99 response time metrics for the POST /envelopes API, as this will help us appropriately tune our timeout settings.TIA

Hi everyone,I’m building a Make.com scenario to create a DocuSign envelope from a template and automatically prefill fields in the document.What works: The envelope gets created successfully (status: created) The recipient (“Kunde”) is set correctly (name + email are correct) What doesn’t work: None of the DocuSign fields get prefilled (even a static test value like "Test123" doesn’t show up) This is the JSON body I send in Make (DocuSign “Make an API Call”):{ "status": "created", "templateId": "XXX", "templateRoles": [ { "roleName": "Kunde", "name": "{{4.Accountname[1]}}", "email": "{{7.ContactEmail}}" } ], "recipients": { "prefillTabs": { "textTabs": [ { "tabLabel": "vorname_nachname", "value": "T

Hello,I am developing an integration on my Demo Account (Sandbox) and I am receiving the error "ACCOUNT_LACKS_PERMISSIONS" when testing the WhatsApp/SMS delivery feature.Could you please enable "Phone Authentication" and "WhatsApp Delivery" for my account?API Account ID: ( redacted )Thank you.

Hi, I would like to request information regarding the languages supported in the DocuSign Envelope when using the Apex Toolkit, specifically through Recipient.EmailSettings? I found this Supported Language List. List. However, I would like to confirm whether the following languages are currently supported, or if there are any plans to add support for them in the future:Walloon Language (wa) Flemish/Belgian Dutch (nl-BE)Could you please clarify this for me? Thank you for your time and support. Kind RegardsWilly

Created App and Key with Redirect URI and RSA Key Pair. Sent request in format https://account-d.docusign.com/oauth/auth?    response_type=code    &scope=YOUR_REQUESTED_SCOPES    &client_id=YOUR_INTEGRATION_KEY    &redirect_uri=YOUR_REDIRECT_URI. Replacing with my value. Code returned is of typ:MT and Payload is not JSON format. Instead it is in binary format

Hello,I’m experiencing an issue with the option “Use the sender’s company name.”When I enable this checkbox, I expect the sender name shown to recipients to switch to the brand/company name. However, even after checking the option, the sender name does not change and still appears as the individual sender rather than the brand.Am I misunderstanding the purpose of this setting? Could you clarify what this option is supposed to do, and under which conditions it affects the sender name?Thank you in advance for your help.

  Hello DocuSign Community,  We are hitting the ENVELOPE_ALLOWANCE_EXCEEDED error on our Developer Demo account, and the error occurs both via the REST API AND the web interface. This rules out the "API has separate limits from web" explanation mentioned in previous threads.  Environment:  - Account type: Developer Demo (sandbox)  - Authorization server: account-d.docusign.com  - API base path: demo.docusign.net/restapi  - Integration method: REST API via official PHP SDK (docusign/esign-client v8.6)  - Error code: ENVELOPE_ALLOWANCE_EXCEEDED  - Error message: "The envelope allowance for the account has been exceeded"  Critical detail:  The same error appears when trying to send envelopes through:  - ✗ REST API calls  - ✗ Web interface (appdemo.docusign.com)  This suggests either a system-wide bug or an account-level issue, not an API-specific quota.  Su

We have a published webform - "id":"3527eec7-2c68-43f0-aca9-9eb51c4e7a16","accountId":"d09a0de1-8019-4bf8-a56c-46916ffdf531". When users complete it, is it possible to have it trigger Connect to send a webhook request? I don't see anything related to WebForms in the list of possible triggers for Connect - maybe it is not supported or maybe it is under a different name? Thank you!

Current process:The Sales User creates the Contract and becomes the Owner of the Contract.The Manager then clicks “Send to DocuSign.”Currently, the reply email is being sent to the Manager’s email address.Requirement:The reply email should be sent to the Sales User’s email address, not the Manager’s.We are sending the envelope using Apex code as shown below. We need a solution in Apex code like below instead of API.myEnvelope = dfsle.EnvelopeService.sendEnvelope(myEnvelope, true);Please do it this is a high priority. We are waiting for a solution.

I have several brands within a company and I would like to set the BrandID dynamically via Apex based on some specific criteria. However, I could not find any documentation regarding setting BrandId via Apex. I tried asking AI about it and even found information suggesting that dfsle.Envelope API doesn't support setting brand IDs programmatically.Could you please confirm whether it is possible to set the BrandId programmatically? If it is not supported, I would appreciate an official confirmation. Kind RegardsWilly

Hi, I have a template docx where I want to put payment details with QR code image (different for each user).I’ve already tried all of the following (`payment_qr_code` = Base64 encoded image).And none of it displayed anything, it just prints the string/html tag. I use the https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/documentgeneration/updateenvelopedocgenformfields/ API.

I am trying to develop a Docusign integration with a dev account. After 20-30 envelopes the API just gives up with a permanent ENVELOPE_LIMIT_EXCEEDED error. Not very helpful for a developer.The support live chat I can’t seem to get to do anything - click the button and nothing happens. Trying to login to support gives me an auth error. How can I contact support to get them to lift this limit. I’m on my second developer account already and I don’t want to keep creating them.Anyone know the email address for support or some way of sorting this?

Calling Login with https://www.docusign.net/api/3.0/credential.asmx fails with "One or both of Username and Password are invalid."  The Login call is made by using “[IntegratorKey]Username” as the username.This just started recently.  I was only made aware of it today, so it could have started today.  All my customers are down. Is it possible that the API has changed and I never received any emails? We got our Integrators Key in 2013 and have not made any changes to this code in quite a while.

Hi all, we had DocuSign Apps Launcher working on our test Salesforce sandbox. I’ve migrated to the User Acceptance Testing sandbox and am getting a ‘Page doesn’t exist - Enter a valid URL and try again’ when we click the ‘Send with DocuSign’.I’ve set up a new template on the UAT sandbox and that’s working, there’s a corresponding IK on my Apps & keys dashboard, so it’s connected to my dev account.The button is calling:{!URLFOR($Site.BaseUrl + '/apex/dfsle__sending', null, [sId = Farm_Visit__c.Id])}I’ve tried swapping out the /apex/… with endpoints for REST & SOAP to no effect. I wasn’t really expecting that to work but /apex/ isn’t listed on the endpoint page listing so figured it was worth 30 seconds to cut’n’paste.I'm assuming that $Site.BaseUrl is correct (https://demo.docusign.net but I don’t know how to check that from Salesforce. That is wha