eSignature API

Once signing the is complete the embedded event returned back in the callback url is coming as "viewing_complete" instead of "signing_complete"

Our B2B software has an embedded e-Signature integration with DocuSign where we allow our software users to create envelopes and tag recipient fields for other software users.  Our integration utilizes a “system user” who authenticates to the customer’s DocuSign account and all subsequent envelopes are created and signed on behalf of that system user. For the error message: Account lacks sufficient permissions.  In-session permission required when specifying a captive recipient.the customer’s system user has the “DS Admin” permissions profile.  I welcome any ideas where the client’s DocuSign Admin can go to enable a “in-session permission”?

I have created a application in developer account and verified it after making 20 API calls. I am using JWT authentication. After that I logged in to my production account and granted access again using https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=<YOUR_CLIENT_ID>&redirect_uri=<MY_REDIRECT_URL>.I also updated the UserId and API Account ID. Now when I am trying to send document to sign using my application, I get error {"Error while requesting server, received a non successful HTTP code with response Body: {\"error\":\"consent_require

Hi Community,Does anyone use DocuSign with Lone Wolf here? I need help with my first e-signing and sending docs out for e-signing. According to Lone Wolf, my DocuSign account is already integrated with Lone Wolf. Lone Wolf reps are not trained for DocuSign support. I’ve put in a support request to DocuSign. If you’re so inclined, Help!   

When downloading the envelope via the application, the completed fields are not shown in the document and the signatures are not shown eithernote: I am using the development environment, my account is not yet in productionapp.get('/envelopes/:envelopeId/documents', async (req, res) => {  await checkToken(req);  const envelopesApi = getEnvelopesApi(req);  const envelopeId = req.params.envelopeId;   my code:  try {    const docs = await envelopesApi.listDocuments(process.env.ACCOUNT_ID, envelopeId);    res.json(docs);  } catch (error) {    console

Hi everyone,I need some help with the DocuSign Go-Live process. I’ve been trying to get my Integration Key (5adb2409-a79c-4616-8a0c-79de07f2d449) approved for production for over a month, but I keep getting declined without any reason provided.Here’s what I’ve done so far:✅ Read and implemented all troubleshooting documentation✅ Tried with multiple Integration Keys✅ Passed automatic review (20 successful API calls, no polling)❌ Go-Live manually declined multiple times (first two attempts took 3-5 days, latest one was rejected within hours)❌ No emails or notifications explaining the rejectionI’m stuck and don’t know what else to fix. Has anyone faced this before? How can I get feedback on why the integration is being declined?Any insights would be greatly appreciated!

Hello, I want to implement the CSC (Cloud Signature Consortium) API integration (TSP API with CSC), but i can't find any description. Could someone send me a link that describes the integration steps or a documentation? Example is also appropriate if available.

Hi everyone, Docusign newbie here. Not sure which category to post this in so apologies in advance on that one.I work for a MSP. Our client uses Dayforce HR platform. In order for docusign signature box to pop up in browser we want to assign an Azure policy.The HR website is https://us242.dayforcehcm.com:443Should I allow this URL https://na2.docusign.net/Signing/?insession=1&ti=f53d6cb0d3f64a96a295c0be724e7e9eor what should it be shorttened to?Thanks in advance!

I have installed Docusign App Launcher in my Salesforce developer org. I am using the generate_and_convert REST API to generate the documents and then I am sending these documents using sendEnvelope method of EnvelopeService ApexToolkit. I have the requirement of getting a list of documents as and when it comes and then updating them onto an Envelope and finally send the Envelope. For this I have created an empty envelope with a recipient and sent the Envelope with Boolean false.Contact myContact = [SELECT Id,FirstName,LastName,Email,Phone FROM Contact WHERE Name = 'Test Contact']; dfsle.Envelope myEnvelope = dfsle.EnvelopeService.getEmptyEnvelope(new dfsle.Entity('mysourceId'))    .withRecipients(new List<dfsle.Recipient> {        dfsle.Recipient.fromSource(            myContact.FirstName + ' ' + myContact.LastName,            myContact.Email,            myContact.Phone,            'Signer 1',            new df

Hello! I’m currently automating our contract generation process using DocuGen (DocuSign eSignature) but have recently encountered an issue. Specifically, when I populate a text field (e.g., {{test_field}}), the field no longer accepts line breaks. This functionality was working correctly about a week ago. Could you please advise me on how to resolve this issue? Thank you!

Hi everyone,I’m trying to integrate with the eSignature API with a product that has Docusign integration, but it might be old because it requires a PFX file.Is anyone able to help confirm whether integration with eSignature using a PFX file is still available?If so, does anyone know how to obtain the PFX file? We have the public and private key files, as well as the certificate, but the generated PFX (using open SSL) does not work.ThanksMike 

The files are downloading but the document does not show the signatures, the filled fields are blank. I want the complete document, with the filled fields and the signatures, can someone help me? my code:  app.get('/envelope/:envelopeId/documents', async (req, res) => {  await checkToken(req);  let envelopesApi = getEnvelopesApi(req);  const { envelopeId } = req.params;   try {    let results = await envelopesApi.listDocuments(process.env.ACCOUNT_ID, envelopeId, null);       res.json({      envelopeId: results.envelopeId,      docum

I created a template with a SignerAttachmentTab (optional) inside it on Docusign.Before creating an envelope, I get the SignerAttachmentTabs of a signer and override the value of the property Optional to make it become required.But when I sent an envelope, the UI was confusing me. There were 2 overlapping tabs.Do you guys know a better way to control the property Optional before creating an envelope?

I have been trying to place signature image directly without having the user to sign it. I have used sign here tabs and added stamp tabs in it. But in the received document, it is still expecting the user to manually sign it.I have researched enough,I am not finding any resource which solves my problem.here is the code took some help from AI. This does seem to work. Is it even possible to achieve this? If yes, how?```args = { "account_id": jwt_values["api_account_id"], "base_path": jwt_values["base_path"], "access_token": jwt_values["access_token"],}api_client = create_api_client( base_path=args["base_path"], access_token=args["access_token"],)env = EnvelopeDefinition( email_subject="Please sign this document set",)env.documents = []document2 = Document( # create the DocuSign document object document_base64=base64.b64encode(fi

I’m trying to generate a document with parameterized where i’m creating a template when it doesn’t already exist, generate the envelope, and update the fields.The fields in the document are being set as {{FieldName}} as suggested by documentation, but the GetEnvelopeDocGenFormFields() for the envelope is returning no fields and any attempt to use the update throws an error.i’ve added a simple version of my code bellow.How is the sender field parameterization supposed work?    public async Task TestCode()    {        var fileName = "test_document";        string docBase64;        using (FileStream fs = new FileStream($"E:\\{fileName}.docx", FileMode.Open, FileAccess.Read))        {            using (var ms = new MemoryStream())            {                fs.CopyTo(ms);                var bytes = ms.ToArray();                docB

How to reproduce my bug : Generate a enveloppeView Sign the enveloppe The signing.on(‘sessionEnd’) isn’t triggered I was a valid docusign integration and it works on dev environnment 

Are these url s correct? $baseUrl = "na3.docusign.net/restapi";$consentUrl = "https://account.docusign.com/oauth/auth?response_type=code&scope=$scope&client_id=$clientId&redirect_uri=$redirectUri"; the JWT headers$payload = [        'iss' => $clientId,        'sub' => $apiUserId,        'aud' => 'account.docusign.com',        'scope' => 'signature impersonation',        'iat' => $now,        'exp' => $now + 3600 // 1 hour expiration    ]; $tokenUrl = "https://account.docusign.com/oauth/token";$config=$apiClient->getConfig();    $config->setHost('https://na3.docusign.net/restapi');

I’m getting “USER_AUTHENTICATION_FAILED: One or both of Username and Password are invalid. Invalid access token” when I call create_envelope.I know the access token is correct after it’s generated because “get_user_info” is returning the correct account id and username, but by the time I try to create the envelope, it says the access token is invalid.in the code below, after “request_jwt_user_token”, the print commands are displaying the correct account id and username.I have been stuck on this issue for a few days now and any help would be GREATLY appreciated!Code:import base64from cryptography.hazmat.primitives import serializationfrom docusign_esign import ( ApiClient, EnvelopesApi, EnvelopeDefinition, Signer, Tabs, SignHere, InitialHere, Recipients, Document,)from docusign_esign.client.api_exception import Api

I am building a SMS extension app for workflow when customer add a step to send a SMS ,the custom UI will get open where he add the number to which he wants to send SMS and the message body? as well as I want to fetch the contacts from the DB which already present in my DB to show him in a dropdown options for sending message? 

When using the “combined” API option on Java SDK I don’t get the certificate of completion bundled on the PDF. But, If I use the “archive” option I get a ZIP file with the documents and the CoC.I need to get the CoC with the compleated action, how to do this? The documentation on the EnvelopesAPI to download documents  “getDocument" states:You can also use this method to retrieve a PDF containing the combined content of all documents and the certificate [...] To retrieve the combined content replace the `{documentId}` parameter in the endpoint with `combined` the

I'm working on a new application that has integration to Docusign to allow customer to sign documents using the embedded flow. The way it works is we generate the signature URL and show it inside a modal so customers can sign without leaving our application.So far so good. Everything was working properly until we promoted the application to production.All of a sudden we've started to see {"error": "consent required"} errors in the call that generates the access token that is used in the envelope api calls. Our application is written in Python and we are using the request_jwt_user_token function in the Python SDK. I'm clueless as to why this is working in staging but not in production. I've updated all the necessary parameters with their production values but I'm

I'm working with a template and I want to add an attachment to it, but this error is returned. Here's the code:  let document1;   try {    let response = await fetch(anexoFuncionario);     if (!response.ok) throw new Error('Erro ao baixar o arquivo');    let contentType = response.headers.get('content-type');    let fileExtension = 'pdf';     if (contentType.includes('image/png')) fileExtension = 'png';    else if (contentType.includes('image/jpeg')) fileExtension = 'jpg';     let arrayBuffer = await response.arrayBuffer();    let base64FileContent = Buffer

I have a web app in PHP and JS for front. I am connecting to Dcusign through the JWT and exchanging it for an access token, but i keep getting this error "Decoding JWT did not workUnexpectedValueException: "kid" invalid, unable to lookup correct key in /html/htdocs/mrt_dgheorghe/vendor/firebase/php-jwt/src/JWT.php:477"The code for JWT looks like this: $payload = [ 'iss' => $clientId, 'sub' => $apiUserId, 'aud' => 'account-d.docusign.com', 'scope' => 'signature impersonation', 'iat' => $now, 'exp' => $now + 3600 // 1 hour expiration ]; $privateKey = file_get_contents($privateKeyFilePath); $jwt = JWT::encode($payload, $privateKey, 'RS256', $keypairID); //kid $publicKey=file_get_contents('publicKey.key'); try{ $decodedJWT=JWT::decode($jwt,$publicKey); print_r($decodedJWT); echo "This is

When fetching envelope details based on filters using ListStatusChanges, the request contains customField as the account number and folderIds as sentitems, with include = "custom_fields" (to retrieve other custom field values).Before executing this request, we call the token API, but the token creation sometimes returns a non-successful HTTP code, though not all the time.What could be the issue? We are implementing it as mentioned below.var _apiClient = new ApiClient(_baseurl);token = _apiClient.RequestJWTUserToken(_integratorKey, _userID, _baseurl, Encoding.UTF8.GetBytes(PrivateKey), 1, Scopes);TokenGeneratedAt = DateTime.Now;

Hello, We were getting ready to “Go-Live” with our first DocuSign integration but when we went to start the process, it is showing that we don’t have 20 consecutive Api calls. Upon closer review, it looks like the “GetUsers” endpoint (list | REST API | Docusign) is registering as Failed when it cannot find a user. This doesn’t make sense because it is still a successful call is it not? We are using this to check and see if the user exists before creating the signature request. If they do not exist then we call the user Add API.  Any insights into this? Is there a better approach that I am missing? Or do we just need to get past this initial fail and run multiple more