Developer

We have recently got DocuSign for our company and integrated it with our OneDrive app. The sync between the two keeps slipping. We need signed documents to be saved to the original forlder. Can anyone advise on where this could be going wrong? It just saves to the primary folder in OneDrive. We had it setup initially but it keeps changing. 

i want to use DocuSign Api Service to send document for digital Signature but the problem is that i want sign box in specified row of document so i want to change the width accordingly but their is only one option which is scaleValue so is there any option or api with any payload by which i can fix the height and width as per my require ment

Hi! I just published a new YouTube video on how to automate contracts faster using Docusign CLM for Salesforce. You’ll see how to generate contracts in one click with Salesforce data, send them for signature, and track status directly in Salesforce. I also show how signed contracts and key terms flow back into Salesforce automatically, saving hours of manual work and reducing errors across your process. Watch the full video 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

I’ve placed the anchor tags for my document in a 3 column table.  The first cell has anchor tag \c1\ for recording a Text Tab value for signer’s company, the second cell has anchor tag \n1\ for recording the signer’s full name, and the last cell has anchor tag \s1\ for recording the signature.The problem is that the displayed value for the anchor tags are not wrapping within the cells of the table.  So if the company names or signer’s names are long, they run into the values of the other cells causing the text to overlap.  Is there a way to force the injected text to wrap in the cell and respect the layout where the anchor tag is defined? I’ve tried to specify the “width” property to 100 and “anchorUnits” property to “pixels” (also tried “inches”), but it doesn’t seem to affect anything:"recipients": {    …    "signers": [      {       ...        “Name”: “Sample Name”        "tabs": {          "signHereTabs": [            {              "anchorString": "\s1\",              "anchorUnits

We build signing envelope via API. We often have multiple signers in our envelope and are currently signing sequentially. We use the TextTabs to put read-only text on the document. And, we are putting those tabs on the lowest order recipient. The tabs, in this case, have a transparent background and overlay nicely on-top of the document. Lately, I was asked to parallelize the signing process (i.e. send the document to multiple recipients at the same time). We tried a few things to make this work: Copy the tabs to all recipient. This caused issues since we were exceeding the Maximum number of tabs in an envelope (we have a lot of documents in our envelope). So, this option was not acceptable.  Use the shared option on the tabs. When using shared, all recipients would see a white background on the tab. Even if required and locked were set to ‘true’.  Use the global option “When an envelope is sent, write the initial value of the field for all recipients”. This was working pretty well for

Hello,I am attempting to implement JWT Grant authentication for my DocuSign integration in a developer account (demo.docusign.net). I consistently receive the following error when making API calls (e.g., oauth/token endpoint):"Authenticatie mislukt (400): no_valid_keys_or_signatures"This translates to no_valid_keys_or_signatures.Here's what I've done so far:I have created an RSA Keypair within my DocuSign developer account for my Integration Key. I am using the Private Key from this newly generated keypair. I have confirmed that it's copied completely, including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- headers/footers, and that there are no extra spaces or missing line breaks. I have correctly set my CLIENT_ID (Integration Key), USER_ID (API Username), ACCOUNT_ID, and DOCUSIGN_BASE_PATH (https://demo.docusign.net) in my application's environment variables. I have performed the required user consent grant by navigating to the consent URL (https://account-d.d

Hi, I am using the C# eSign SDK and am trying to allow users to open a sender view for envelopes that they are not the sender on, but have been granted shared access to. i.e. User A creates a draft envelope and User B opens the sender view for that envelope.The documentation says I need to attach a header ( X-DocuSign-Act-On-Behalf) with the principal user id (User A’s id) as the value in order to act on their behalf.Here’s what I am doing generally in my code (language is Visual Basic). I am using the agent user’s (User B) access token and base uri:DSClient = New DocuSignClient(baseUri & "/restapi")DSClient.Configuration.DefaultHeader.Add("Authorization", "Bearer " & accessToken)DSClient.Configuration.DefaultHeader.Add("X-DocuSign-Act-On-Behalf", principalUserId)...EnvelopesApi.CreateSenderView(accountId, envelopeId) The problem is when I add the header and make the API call, I get an error back:{errorCode: “ACT_ON_BEHALF_USER_NOT_ALLOWED”,errorContent: "An 'Act on Behalf Of'

I’m trying to receive webhook notifications from DocuSign on my endpoint but the request fails with the error:"The request was aborted: Could not create SSL/TLS secure channel."My Azure web App Service to supports TLS 1.3 minimum. DocuSign webhook requests fail when attempting to connect.Does DocuSign support TLS 1.3 for webhooks? If not, is there a workaround or fix to make this work?

Hi DocuSign Community,We’ve developed a system that integrates with DocuSign to access templates and send offer letters directly from our portal. In our setup, users log in to our portal with their DocuSign accounts, and from there they can access their templates and send offers through DocuSign using eSignature API.So far, we’ve been testing successfully using a Sandbox account. To move into production, we understand that we need a Partner Production account. We have already filled out and submitted the required form for this, but we haven’t received any response yet.Has anyone else experienced delays with this process? Is there a recommended way to follow up or escalate the request to get our Partner Production account enabled?Any guidance would be greatly appreciated.Thanks in advance!

Hello everyone,I’m encountering a problem when accessing the DocuSign Developer Portal:- URL: https://developers.docusign.com/platform/account/  - After logging in, the page stays completely blank (only the header appears).- In DevTools Network tab, the request to `/api/user/settings` returns HTTP 500.- On the console, I see the error:    TypeError: Cannot read properties of undefined (reading 'account_name')Steps already tried:- Tested in Chrome and Edge (both latest versions).- Cleared cache and cookies, used incognito mode.- Tried on different networks and devices.- Extensions like AdBlock are not the root cause.It seems the frontend cannot proceed without user settings.  Has anyone experienced something similar? Any workaround, or is there a direct way to reset or repair account settings?Thank you for your help! 

We host in-person meetings, and want the attendees of the meeting to sign the meeting document via a tablet that gets passed around.  We don’t know who the attendees/signers will be, or how many, but we want them to sign the document within our web application.  After a lot of experimentation with Docusign’s APIs, we’ve taken this approach:We create an envelope (POST to /restapi/v2/accounts/{accountId}/envelopes) with 100 allocated signers (the maximum allowed and hopefully more than will ever attend our meetings).  These are placeholder signers.  Our document also has 100 lines allocated for recording attendee information which feature anchor tags for recording the signature (\s1\, \s2\, etc.), anchor tags for the attendee’s name (\n1\, \n2\, etc.), and anchor tags for recording the attendee’s company (\c1\, \c2\, etc.)   As each attendee enters their information on the tablet, we call Docusign’s recipient-update API endpoint (PUT to /restapi/v2/accounts/{accountId}/envelopes/{envelop

 Hi DocuSign Community!I'm implementing embedded signing with Focused View/Click to Agree using the eSignature JavaScript SDK. I need to display the embedded document in a dialog/modal within my page.Question: Does Focused View provide any built-in dialog/modal component for displaying the embedded document (similar to Click API), or do I need to implement my own custom UI container where the document will be embedded?I've checked the documentation which covers styling the container div, but I want to confirm if there are any built-in presentation options before building a custom solution.Thanks! 

curl --location 'https://demo.docusign.net/restapi/v2.1/accounts/44a2f9ab-3470-4650-b2e6-ac8a4dfea066/envelopes/cf7b3774-9987-4833-a90f-2a66e0a1afbd/views/sender' \--header 'Authorization: Bearer eyJ0eXAiOiJNVCIsImFsZyI6IlJTMjU2Iiwia2lkIjoiNjgxODVmZjEtNGU1MS00Y2U5LWFmMWMtNjg5ODEyMjAzMzE3In0.AQoAAAABAAUABwAAOgdG_s_dSAgAAKLLpwbQ3UgCAEz2CsEDomdHhcUDVEctjgkVAAEAAAAYAAIAAAAFAAAAHQAAAA0AJAAAADZhZTY0YTNkLTRiMjEtNGM1OC04MzU1LTA1ZGU0NTU4NzgzYiIAJAAAADZhZTY0YTNkLTRiMjEtNGM1OC04MzU1LTA1ZGU0NTU4NzgzYhIAAQAAAAYAAABqd3RfYnIjACQAAAA2YWU2NGEzZC00YjIxLTRjNTgtODM1NS0wNWRlNDU1ODc4M2I.DLenJSax1U2_6ASAm9tYR1GCqQTVj37eDJHhSURCMfNKZ2CYLWn-X-NKTVIaYF-xTA51tZtHiSXqiQI-t171Aqk6GnqEEW4oLChLFotkEBoJUvPj3UvUu_87-PDp1meJJmqzYUiOVeF2iHZijdFEWU0apBRbAujitSNyU4R7SEWAZO8i9xUq70lf0heo9qnGs1qWdlRqn5R-rady1ufdrJxlH2vKAoTsPSYCXnvImYWRZyKx5c_kndFUdBMF_JpMZsObhgDXbRH5pBT0hGgxhN1rsaJBY-RdTT_vrYCs4DVux8rduk5cnoZbGBzqK04b_IMncNXKpqqG5GFZFYoXKA' \--header 'Content-Type: application/json' \--data '{  "returnUrl": "https://pms.imi

Send to p**************

We've met the following criteria and we're thinking that this is a platform bug because what we're seeing in the go-live dashboard isn't reflecting the "declined" state that's indicated in Go-Live process documentation. We have a status of “Ready to submit” but received decline email. We have the IAM Standard subscription. Here are the criteria we're meeting:- We have, and are submitting this request from, a dev sandbox account and integration key- 20 or more successful API calls in a 24 hour period- Integration exclusively using OAuth 2.0 for authentication- Active production account with a plan activated (this account)- Admin privileges on both the dev and prod accounts- Review submitted via the actions -> go live process- Logs are clean- We’re thousands of calls below the rate limits- The go-live request attached to this message is the one that's been declined twiceWe’re not getting anything in the dev dashboard indicating a declined state, only that it’s ready to submit, even af

We are trying to reach the docusign admin Apis, using authorization code grant for authentication. We are getting the below responses for both Get and post user .Please help me understand where is this going wrong.Below are the steps I am following Get Authorization Code using https://account-d.docusign.com/oauth/token https://account-d.docusign.com/v2/organizations/OrganizationID/users?Authorization=Bearertoken Response code 200,<!DOCTYPE html> <html lang="en" class="account-server"><head>    <meta charset="utf-8">    <meta name="viewport" content="initial-scale=1.0">    <title>Docusign</title>        <link rel="icon" href="https://docucdn-a.akamaihd.net/olive/images/2.64.0/global-assets/ds-icons-favicon-default-64x64.svg" type="image/svg+xml">    <link rel="canonical" href="https://account-d.docusign.com/" />    <base href="/">     <script type="text/javascript" nonce="WZtc7MttxuYURuw2RQY0y6bwija69tP4ZmORK1dq3Lg=">   

Has anyone integrated DS with infoEd?

Hi,I’m attempting to leverage the embedded URL function in the apex toolkit where a user can initiate a contract and have a user sign on their device in person using embedded URL to docusign.I’m requesting an envelope using this code:         // 2. Create empty envelope tied to CPA        dfsle.Envelope env = dfsle.EnvelopeService.getEmptyEnvelope(            new dfsle.Entity(cpa.Id)        );        // 3. Attach DocuSign template        dfsle.Document doc = dfsle.Document.fromTemplate(            dfsle.UUID.parse(templateUuid),            'Customer Product Agreement'        );        env = env.withDocuments(new List<dfsle.Document>{ doc });        // 4. Create embedded recipient (⚠️ role name must match template role exactly)        dfsle.Recipient signer = dfsle.Recipient.newEmbeddedSigner(            cpa.Primary_Contact__r.Name,            cpa.Primary_Contact__r.Email,            String.valueOf(cpa.Primary_Contact__c) // clientUserId = Contact Id        ).withRole(           

Hi Team,I am using REST API to create envelope and get it signed by supplier. Once its signed, on top of that signed document we need to add CEO signature automatically. Is it possible in DocuSign. I see its not possible to add directly on my analysis. Can we use composite templates to get this done. Any thoughts would be appreciated.Thanks in advance.

For three days, I have clicked the button for Promote to Production. I click through to my paid account, select the user there, and the system then says there will be a go live decision in 48 hours.24 hours later, I go back, and the Promote to Production.Looking to contact someone in Support fails, as the question mark only has the Support Center, and no option to contact support.How, exactly, do I go live if the automated system doesn’t work and there isn’t support to contact? Or do I need to rewrite my integration to use a service that actually works? 

Has anyone had any success adding an Intelagree integration at the org level? We have multiple accounts under our DocuSign org but having a hard time getting the integration to work.