eSignature API

Could you please advise us on the alert and how to to mitigate it  

Hello I have one integration App deployed on PRD.Endpoint /oauth/userInfo returns me account with host: https://eu.docusign.net.What if I want to cooperate with accounts from different regions?Should I have accounts on each region and apps for them?Should I create new apps for regions on my one existing account?Is it possible my current app will be able to connect with accounts from all regions? BR

Hello. I’m trying to create a back-end system that can automatically retrieve an access token without any user interaction so that it can send out documents for signing. The samples I’ve encountered PDFs for signing have required me to authenticate using my developer account. Is there a way to get an access token programmatically without any user interaction?I appreciate any help you can provide.

Hey,I’m sending via API to a signer an envelope created from template, which has fields to fulfill including attachments (multiple)I need to separate the attachments that are added by the signer, sometimes it’s just one page, sometimes multi-page documents.I already https://www.docusign.com/blog/developers/getting-signer-attachments-using-the-esignature-rest-api and I don’t get desired outcome.What I have noticed is that once the signer add any attachment it’s added to the document as new page, and there is not ID I could use to distinguish which page is from initial document, or is an attachmentHow can I separate the initial document and each attachment filed?

Hi all,I’m using the following JavaScript in my application:async function startSigningCeremony(signingUrl) { // Set the clientId to your application's Integration Key let clientId = "28ef2184-4fc9-4ae0-b77b-a055fb0727ac"; // Integration key // Check if signingUrl and clientId are provided if (!signingUrl || !clientId) { throw new Error("signingUrl and clientId must be set"); } const signingConfiguration = { url: signingUrl, displayFormat: 'focused', locale: 'en', style: { branding: { primaryButton: { /** Background color of primary button */ backgroundColor: "magenta", /** Text color of primary button */ color: "white", } }, signingNavigationButton: { finishText: "Agreed!", // default is Submit // 'bottom-left'|'bottom-center'|'bottom-right', default: bottom-right

I have been sending email to sign document through esignature rest Api using python (Backend), I am facing problem while signing ceremony , i am not able to click the links , it seems the link is not clickable , not redirecting to weblink, though it was clickable earlier . is this possible , if yes, then please guide me through the steps .

After I promoted my APIKEY from Developer Account to Production, when running “SigningViaEmailTest”, theEmail sender is “dse_demo@docusign.net” Email Subject is “***Test Document***<<my custom email subject>>”. This should be “<<my custom email subject>>”. Email Body contains “This document is for demonstration purpose only.”. This should not be displayed. Email Body contains <<my DocuSign Profile name>> and <<Email>>. Though I am setting EnvelopeDefinition.setSender(UserInfo), the default values on my Docusign profile are coming.

I have done custom integration using docusign api with Salesforce, now client want that whenever the recipient opens the document sender should get to know also when it signs it, however using CC feature just let the sender know it got signed not Viewed, if i directly use docusign this sender gets a mail stating the recipient viewed, Any idea ? 

Hi, I’m running into an issue where I have 2 Documents with anchor strings to be used for text fields. The first Document has 1 page and has AnchorString “A” placed in order for the signer to input text during the DocuSign experience. The second Document has 2 pages, in each page there is a anchor string placed for this document, however no action is needed to be taken by the signer and the text tab for this document should just be readonly. The reason why it should just be readonly is because the Signer should have visibility to this document so we are placing a ‘hidden’ tag on the document for visibility. I would like to reuse the same ‘text’ anchor string for this Signer so that it can serve a multipurpose, is there a way to allow a signer to input text using an anchor string and also use the same anchor string to serve as a way to allow them to view a document during eSign? The text tabs for each purpose would of course be configured differently with unique labels. It seems that du

Hello everyone! I have a question. I want to send an envelope to the signatory through the CRM system. The documents inside the envelope are different every time, so I cannot use the templates in docusign or fix the signature position in the document. What I want is to manually specify the signing location in the file every time it is sent. How can this requirement be implemented?

Hey, lately I’ve encountered a very strange behaviour of the platform. When i try to visit `https://app.docusign.com/api/accounts/{account-id}/envelopes/{envelop-id}/documents/1`, disregarding if I’m already logged in, platform starts redirecting me with all these oauth bullshit. And those redirects definitely have some markers, that tell it to redirect me back, to the page I intend to visit, but something goes wrong and I eventually stop on `https://apps.docusign.com/send/page-not-found` landing page. The fun part begins, when I try to visit the same document with Postman, when i add exactly the same request params as my browser (cookies and stuff) - system does not want me to re-authenticate, it simply returns my document. Help me understand, if it’s a bug or a feature? 

I’m following this tutorial and hitting an error when I get to step 3.  I’m using the Node.JS SDK and the error I’m getting back is: "status":400,"text":"{\"errorCode\":\"FORMAT_CONVERSION_ERROR\",\"message\":\"The data could not be converted.\"}" I’ve tried many different files, all DOCX, including very simple one-line docs and docs from the sample projects with the same issue.  I can send all these docs as normal envelopes. In the docs here it says:Document generation is available in all developer accounts However, I don’t see any settings mentioned in this blog post on my account, so I’m wondering if the above is still true. Appreciate any advice/guidance anyone may have, thanks!!

Olá, bom dia.Estou tentando fazer a integração do CRM com o meu CRM e ele pede pra que Efetue 20 chamadas de API com sucesso. Como realizar essas chamadas? Aguardo!

The update API under Templates seems to be not working. Unable to set autoMatch as false for the templates via the Docusign eSignature REST API

I’ve implemented an imbedded signature request integration using the javascript library https://js-d.docusign.com/bundle.js, submitting signingUrl with displayFormat as ‘focused’. It’s implementing an iframes response into the div signing-ceremony div. I don’t want frames or iframes. I don’t want a second scrollbar right inside the first. I want this in a div tag - no frames. It looks like the content inserted starts with an iframe with id - js-library-iframe. Inside that, there’s another html start, header, body - and another iframe - id ds-signing-document - which has yet another html start, header, body, and multiple sections - one with a scroll bar. The code coming in from the javascript seems excessively complicated when all I want is the document with the ability to sign. Is there any way I can avoid all the iframes and the section with the scroll bar? I’d like the div to just expand with the content so if a user needs to scroll, they can scroll with the browser scroll bar, and t

Hi I need to get info about logged user within oAuth 2.0 flow, no with getUserInfo endpoint.I can't use scope 'openid'.Is there any way to retrieve id of admin who claims consent? BR

I'm using DocuSign eSignature with both a developer account and a Business Pro account. I've successfully developed some apps in my developer account, and after going through the Go Live process, everything integrated smoothly. For each app, I've received an envelope from the DocuSign API team containing all the necessary details.However, I'm facing an issue:When I try to fetch all envelopes using the following endpoint: `https://docusign.net/restapi/v2.1/accounts/{accountID}/envelopes` I can retrieve all my envelopes, except for those sent by the DocuSign API team. These specific envelopes don't show up in the list. On the other hand, when I use this endpoint: `https://docusign.net/restapi/v2.1/accounts/{accountID}/envelopes/{envelopeID}` and pass the envelope ID from the DocuSign API team, I'm able to fetch the envelope without any errors.Can you explain why this is happening? Is this behavior normal?

I want to send pdf to specific users to their email and i want to track the the user will sign my pdf or not it this possible with docusign and if yes then how i implment in my node js project? Any idea any one

I’m using the url returned from createSenderView and I managed to edit preview and edit the fields :)  I would like to download the PDF before sending it to, Is it possible?When I’m using the api of documents/archive I’m getting the PDFs empty (without the fields I configured). Is there an option to download it with the configured fields? (in the same state the sender would get it). 

Hello, I am develping an app that uses power automate and the Docusign connector. My issue is that I want multiple different users to use the app. So I need to make a separate docusign connection for each one on the platform. The issue is that when deploying to production I should authenticate again and login for each connection separatelly as you can see in the screenshot, and this is only an initial deploy, more user are to be added. Is this the right way to do it? In this case I need to gather everyone when I want to deploy to log in separetelly and do the 2 factor authentication? Are there any guidlines on how to move from docusign demo connectors to Docusign in production?  aanmelden = sign in

I completed the creation of new anchor tags for 'Date Signed' to be used as a DocuSign tag, and the necessary changes were made to include the new DateSigned tab on the controller side. However, the problem is that the DateSigned value is prepopulating with the current date when the document is opened. While DateSigned is treated as a property in DocuSign, similar to InitialHere and SignHere, it isn't loading correctly. I applied the date logic in the report, but the same approach isn't working for DateSigned.What mappings are required to ensure that the DateSigned field only displays the date when the signature is actually added in a C# MVC application?

def get_docusign_client(): api_client = ApiClient() api_client.set_base_path(DOCUSIGN_API_BASE_URL) logging.info(f"Using API base path: {DOCUSIGN_API_BASE_URL}") with open(DOCUSIGN_PRIVATE_KEY_FILE, 'rb') as private_key_file: private_key_bytes = private_key_file.read() try: # Request JWT user token oauth = api_client.request_jwt_user_token( client_id=DOCUSIGN_CLIENT_ID, user_id=DOCUSIGN_USER_ID, oauth_host_name=DOCUSIGN_AUTH_SERVER, private_key_bytes=private_key_bytes, expires_in=3600, scopes=['signature', 'impersonation'] ) logging.info("JWT token successfully obtained") # Set the Authorization header access_token = oauth.access_token api_client.set_default_header('Authorization', f"Bearer {access_token}") # Verify the token and get user info user_info = api_client.get_user_info(access_token) logging.info(f"Token verified for use

I already app one app live in Docusign prod, now i am pushing one more app from Docusign demo account to Docusign prod that is connected to different SF instance & usecase is little different, since my prod account is common for both apps what other think would remain common like the API account id, user Id & just the integration key would be different, is it correct understanding?

{"error":"invalid_grant","error_description":"user_not_found"} while making http client calling to generate token

Hi,I am getting below error “ANCHOR_TAB_STRING_NOT_FOUND” (The specified Anchor Tab string was not found in the document. Anchor Tab String "\SignHere58105\" not found. Anchor Tab String "\SignHere58110\" not found.) Although I can see these strings on the document.