eSignature API

After working for some time with Docusign's API I thought it would be a good idea to look into the API's 'Connect' feature (https://developers.docusign.com/docs/esign-rest-api/reference/connect/).This allows the sending of information to an application via webhooks when an event occurs for the envelope in question.Currently the only webhook listeners I have available are with Microsoft Teams and Mattermost. I have created the webhook listener in both and can send information to them using the following command: curl -H 'Content-Type:application/json' -d '{"text":"Test text 1"}' <endpoint>where `<endpoint>` is the URL of the webhook listener in either Teams or Mattermost.Next I have tried to send information from an existing Docusign envelope to Teams/Mattermost using the following perl code: use strict;use warnings;use LWP::UserAgentuse HTTP::Request::Common;use JSON;my $EnvelopeID='"92f294ba-a5a0-4a4d-ac85-f08ad5b6a09a"';my $webhookURL=q{https://site.webhook.office.com/web

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

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!

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

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=">   

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.

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.

I am sending requests via SMS using the api from Salesforce. The text that is sent is not very user-friendly. Is there a way to modify it?

Hi,I'm working on integrating a document workflow system with DocuSign via API. I'd like to know if the API allows me to initiate the signature type that someone within my company or a contractor should use to sign a document. Should it be: Electronic Signature, DS Email Signature, EU Advanced Electronic Signature (AES), or EU Qualified Electronic Signature (QES).

Hi friends,I’ve attached two images to simplify explaining this. The first one shows my PDF of the envelope (no text tab seen), and the second image shows the Correction of the envelope (with text tab “Rejected” visible). Is there a reason why I cannot see my text tab “Rejected” in the embedded signing or PDF of the envelope? Can I allow signers to see added text tabs when signing? This would help clarify if a user has rejected an envelope for all signers.Thanks

When requesting an access token via the Authorization Code Grant flow, the integration key provided in the Authorization header is not being validated.For testing, I intentionally sent an invalid or even empty integration key in the header, but the /oauth/token endpoint still returned a 200 OK with a valid access_token and refresh_token.  

I am considering using the DocuSign integration, but I would like to confirm whether it can meet my needs: the PDF HubSpot quote (created for the deal) must be automatically included in the same envelope as the contract that is sent out. Is this possible with the DocuSign API? Has anyone implemented something like this before?

In the Developer account, templates created through the Template Builder include a tab field called Data Label.However, in the Production environment, the Data Label field is not available in the Template Builder.I developed a program that populates template tabs fields using the DocuSign eSignature API. Data Label used as a key to map values from the API. Production Account Developer Account 

I have a user attempting to create envelopes via power automate. When they do so, the power automate flow returns the following error when using the CreateEnvelope action: { "errorCode": "USER_DOES_NOT_BELONG_TO_SPECIFIED_ACCOUNT", "message": "The specified User is not a member of the specified Account."}They can run the flow, which requires a successful sign in to DocuSign.They can create and send envelopes via the DocuSign web app.  The user is a user in our DocuSign tenant, and DocuSign SSO group, and seemingly identical users are not encountering the error. Things I’ve tried to troubleshoot:re-created the user’s docusign account with highest privs deleted all previously created power automate connections associated with this user in power automate  re-created the connection used when signing into the flowAny assistance would be appreciated.

Hi all, I have a question related to SAP Document Generation.When we generate a document via sap and select -Allow Digital Signature. The document will be signed via DocuSign. Do you know if it is possible to generate a document via SAP Document Generation and sign the document using DocuSign (QES) Qualified electronic signature addon? Some of our markets require QES. Any help would be appreciated. ThanksAdam

We are integrating with DocuSign using the Python SDK.We implemented retrieving the envelope sender view URL via the API so it can be edited within an iframe.The template editing screen was implemented in the same manner.The view URL functions correctly when accessing the application under development via localhost or 127.0.0.1. However, accessing it via an internal IP like 192.1.x.x or an external IP results in a 401 error.How can I make the view screen appear in an iframe when accessing via an internal IP like 192.1.x.x?  

Hi everyone,I’m trying to create an integration between RD Station CRM and DocuSign to automate the process of sending contracts to my clients. The idea is that when a deal reaches a specific stage in the CRM (e.g., “Proposal”), the system should automatically send the contract for signature via DocuSign and then update the deal in RD with the contract status and signing link.So far, I’ve found that: RD Station CRM provides a REST API to manage deals and contacts. DocuSign also provides an API to create and send envelopes for signature. I haven’t found any native integration between the two. My questions are: Has anyone implemented something similar using direct API integration or via tools like n8n / Zapier / Make? What’s the best approach to automatically update the contract status back in RD Station CRM? Are there any common pitfalls or limitations I should be aware of when building this integration? Thanks in advance for any help!

Hello,       I have written an application that makes RestAPI calls to a base URI (https://na1.docusign.net/restapi)     I do have clients that need to whitelist all URLs from their servers.     For the example above (na1.docusign.net/restapi), I will now need to have the client whitelist na1-b.docusign.net     My question is:               Does the base URI for the RestAPI calls remain na1.docusign.net.      I assume that the base URI remains the same (na1.docusign.net/restapi).      Thanks.