Developer

I am using C# docusign JWT SDK to authenticate. I am able to authenticate and get an access token back where I am able to successfully call GetUserInfo to get account information, but when I create an envelope from the downloaded example, and send that to the CreateEnvelope(account,envelope), it is generating a 500 error message with Stack Trace error…“at DocuSign.eSign.Api.EnvelopesApi.CreateEnvelopeWithHttpInfo(String accountId, EnvelopeDefinition envelopeDefinition, CreateEnvelopeOptions options)”My scopes are “signature” and “impersonation” What am i not doing correctly? Thanks

Hello, . 1. Go to https://account.docusign.com/,  and sign in with your TSC email address.2. If you are prompted to enter your TSC password after entering your TSC email address, please select the “USE COMPANY LOGIN” option instead of typing in your password. Continue to log in as usual.

I’m using the SDK C# and when sending a request Envelopes::GetDocument (link) to get the documents, this fails with error:"errorCode":"USER_AUTHENTICATION_FAILED","message":"One or both of Username and Password are invalid. Invalid access token" All other API calls before calling GetDocument are passing OK - for example when calling Envelopes::listDocument (before the GetDocument) to get the list of documents, that returns succesfully. But then with same starting point GetDocument fails.We do checks for token validity etc. before calling these methods and only GetDocument respons with error. What could be the cause and what should we consider?

Hi everyone,I’m able to send out envelopes for signature in Node.js via the docusign-esign NPM package, but my text fields are not populating for some reason.  I am referencing the documentation linked here.  I’ve tried both on our developer account as well as our production account.Here is my code for creating the envelope.  I am getting the label and ID for the text fields through the Docusign API, and I have double-checked the label is correct through the Docusign webapp itself.function makeEnvelope(args) { try { let envelope = new docusign.EnvelopeDefinition(); envelope.templateId = args.templateId; let text = docusign.Text.constructFromObject({ tabLabel: TAB_1_LABEL, value: 'test text field!', }); let textExtra = docusign.Text.constructFromObject({ font: 'helvetica', font_size: 'size14', tabLabel: TAB_2_LABEL, height: '23', width: '84', required: 'false',

Hi, I’m trying to use a Production Account of a client for Go-Live.However, my developer account does not have an administrator access to their account. The client refuses to give me a full administrator access because they are afraid that I’ll get access to all other unnecessary information.Is there any alternative to this?Thanks!

   This happens with every tab when I set them to true

Hello,We’ve just updated to the Embedded Signing flow. When loading up a document the embedded loader is appearing on the left of the screen. However, there is no way to modify this. Is there something we can pass or is there a bug with our container? Bellow are the screenshots and source code //running in the console$('div[data-qa="embedded-document-loading"]').style.width='100%';//updates the loader to show as centeredApplication Code://TSconst signingConfiguration = { url: this.url, //url from service displayFormat: 'default', style: { signingNavigationButton: { finishText: 'Submit', position: 'bottom-right' } }};try { const docusign = await DocuSign.loadDocuSign(clientId); const signing = docusign.signing(signingConfiguration); /** Event handlers **/ signing.on('ready', (_event) => { console.log('UI is rendered'); }); signing.on('sessionEnd', (event) => { console.log('sessionEnd', event); i

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

I’ve created a “demo” app under the primary credentials in which I’ve got a new process coded and working in the test environment up until the receiving of the signed document from docusign.Today in production we receive signed documents at a handler hosted by us (the creating/sending of envelopes today is done with a SOAP integration). This new integration is using the REST approach to create/send envelopes (again working in demo). I would like to test receiving these signed documents generated by the REST approach, but haven’t been able to find how to configure or even view our current webhook. It appears from what I’ve gathered that this is done at “https://apps-d.docusign.com/admin/connect”. I believe the reason I don’t see anything here on our production login is that our integration pre-dates much of what is available today.My question is I would like to add a webhook for this demo app under our primary login, is this possible? If so, where? If not, what is the approach Docusign

Hi! I just published a new YouTube video on how to use Docusign's document visibility feature.You will learn how to control who can view specific documents within a single Docusign envelope, ensuring confidentiality between different parties. You can find it here:  PS: Join me every Wednesday at 9 AM PST for a free Q&A session. Click here to register! 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

Hi, I have 2 questions about Starter plan for Developer API.https://ecom.docusign.com/en-GB/plans-and-pricing/developerPlease check the link for price plans. It says 40 envelopes per month and also 5 envelopes.I didn’t understand the difference. We expect to get 20-30 applications monthly.But I wonder what happens if we sometimes exceed 40 envelopes.Will the system block requests or there will be extra charge for the exceeded envelopes. Thanks

Asp.net MVC C# rest api when i run my code in localhost the code run properly but when in deployed code in server then show error PARTNER_AUTHENTICATION_FAILEDi 

We recently started having a problem with the 5.2 version (RestSharp error). We updated to the 6.0.0 version and everything is working as expected except for calls to Envelopes API GetDocumentAsync to retrieve the signed document.It doesn’t throw any errors, and we’re handling the stream returned in the same was as before, but now these signed PDFs can’t be opened. Adobe states: “There was an error opening this document. The file is damaged and could not be repaired”.If we go into the Admin dashboard we can view and download these just fine. So there is some change in that API call, but I can’t find anything in the documentation or change logs to point to.

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'm having a problem trying to create an envelope.Getting the error:Error while requesting server, received a non successful HTTP code [401] with response Body: O:8:"stdClass":2:{s:9:"errorCode";s:27:"AUTHORIZATION_INVALID_TOKEN";s:7:" message";s:105:"The access token provided is expired, revoked or malformed. Authentication for System Application failed.";}.All credentials are properly set. Is there any extra configuration to be done with the token received through OAuth?

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?