eSignature API

We use Docusign eSignature APIOne of our customers needs to set up a QES, and some of the signatories have last names with diacritical marks (e.g., a slashed "o" or umlauts).Could this potentially cause any issues with identity verification?

Hello,I’m currently sending some documents to be signed in french language.I have templates host in my api resources in HTML format. I use openhtmltoolpdf to format my html documents as pdf. My freemarker templates contain some form fields to enable recipients to fill all the info with any PDF reader.I use some DocusignDate and the html attribute data-pdf-form-field="true" then request docusign to transform the pdf fields with transformPdfFields.The recipients receive the form well formatted except the date fields.When i change the regional settings of my admin account, the format of date fields is well updated but the validation is not working anymore.  May anyone help me please ? Regards,Antoine

Dear Support,We are getting this error on a production account. This is happening after the consent was provided. The token is successfully retrieved using method RequestJWTUserToken. But GetUserInfo/CreateEnvelope return error.Error while requesting server, received a non successful HTTP code with response Body: {"error":"internal_server_error","reference_id":"c02eb179-6bba-474c-8a25-94d3772219cb"}Thanks,Tahir

Hello Everyone!We deployed Docusign embedded signing into our own system. We do know that our users can change their signature style, using templates, drawing, and images during the Signing process. We would like to develop a maintenance page in our system so that our users are able to change their signature before the Signing process. Afterward their signature style will be used in the Signing process on the other day Is it possible to do that? How can we do it? Looking forward to your guidance. Thank you

Our company needs to integrate payments with Stripe into an agreement signing process. The business wishes to restrict payments to only ACH transfers. Is there a way to set this?The AllowedPaymentMethods property of the PaymentDetails, seems to be where this may be set, and it accepts a List<string> of allowed payment methods. I could not locate any documentation for the correct value to allow ACH transfers. Any idea of what that value may be, or if there is another way to restrict the payment type allowed?  

I am looking for an API by which i can get information of user who has given shared access right of another user.Example: User A has shared his/her access with user B. so from API how can I get this information that User B has this right to view/edit envelope of User A. Thanks.

The source file which I use in my code is clear, but the envelope sent to email is bad quality. Please help me

I grant consent to an app that has gone live on Production. When I send an envelope using the access token of my account, will the app creator pay the fees, or will I?

I need to get information of user who all have access to shared folder under template in DocuSign via API also i am not getting this information of shared folder under Folder view from CData.

I need help with the POST request body for creating a DocuSign envelope. I want to create an envelope using a template and prefill custom fields. Here's my current request body:{  "templateId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",  "templateRoles": [    {      "email": "email@gmail.com",      "name": "Recipient Name",      "roleName": "Signer 1"    }  ],  "status": "sent",  "customFields": {    "textCustomFields": [      {        "name": "name",        "value": "john"      }    ]  }}Is this the correct structure for the request body?

DocuSign is failing to load on the front end; I can see the spinner and "Powered by DocuSign," but the actual document is not appearing while using DocuSign JS with embedded.

Using an an SDK to create an envelope. I need to have 2 checkboxes and want client to only be able to choose exactly 1 of those 2 checkboxes. Tried doing something with the group, but it still allows having both empty. function makeEnvelopeCDM(email: string, name: string, document: any) {const docusignAny = docusign as any;const env = new docusignAny.EnvelopeDefinition();env.emailSubject = 'Please sign this document set';let doc = new docusignAny.Document.constructFromObject({documentBase64: document,name: 'Installer Quotation',fileExtension: 'pdf',documentId: '1',});env.documents = [doc];let signer1 = docusignAny.Signer.constructFromObject({email: email,name: name,recipientId: '1',routingOrder: '1',});let si

Refused to connect to 'https://telemetry-d.docusign.net/api/v1/TelemetryWrapper' because it violates the following Content Security Policy directive: "connect-src 'self'Is preventing render and im using v2 of the api $recipient_view_request = new RecipientViewRequest([ 'assertion_id' => $assertion, 'authentication_method' => 'none', 'client_user_id' => $userId, // must match with clientUserId set on the signer 'return_url' => $_SERVER['HTTP_ORIGIN'] . '/coeus/?tab=success&signed=1', // Where to redirect after signing 'user_name' => $name, 'email' => $email,]);

Hello,I am a developer of a software package that integrates with docusign.  Our customers purchase the license and use our admin tool to update the integration information.  Our code then uses that authentication to make the calls. We have a certain customer who is asking us to allow them to configure an integration key per user.  Meaning they’d like us to enhance our user setup admin to give them a place to save the oauth information per user.I’ve read the documentation and understand that it’s recommended there be a single integration key per integration between docusign and the third party software (our suite).  Their reasoning to the best of my understanding is to allow different integrations for users in different regions or countries (I’m not certain the actual differentiation). We proposed enhancing our current admin (where they now enter a single integration key and authentication to docusign) to allow multiple entr

Hi,I'm working on an Docusign integration using the embedded flow and one of the requirements is after the user signs the document we capture the timestamp of the signature. After reading some of the docs and going through the code samples, there's still something not really making sense to me. How can I fetch the signing metadata after the user is redirected back to my application? I ran the code sample but the only parameter I get is a `signing_complete` event in the query string. I was expecting to get an "envelopeId" as one of the query string parameters so that I could use this parameter to issue a request to the EnvelopeRecipients:list endpoint.

I am using developer account, Below is my configuration and yet on opening the e-sign URL, the recipients are not asked to login. Basically any user with access to the URL is able to put their signature. How to configure this correctly ? 

We are using the Embedded View for signing but for some reason the loading spinner is eternalI don't see issues in the console Any idea of what is happening? I'll appreciate any help

Hello community,I have a Bulk Action stuck “in progress” for way longer than it should be. This is done through automation utilizing the Admin API, however, we cannot seem to terminate or make any other request until this user export request completes. Is there any way I can resolve this? Any help is much appreciated.

Yesterday I corrected an Envelope. After I re-sent, it disappeared. I’ve logged a case and explained 4 times that I've searched in every folder I can and used every search filter available. I keep on getting a response to search in a different folder, even though I keep on explaining that I already did the search. No one is helping, they just tell me to do what I already did.

Hello,So I got the API integration almost working perfectly, just one hangup which I hope I’m just missing a setting somewhere.I’d like to setup an In-Person Signer but without their name pre-filled.  We are delivering goods to a company, so we know the company name and general email inbox to send the documents.  We just don’t know who is going to be there to receive the goods, could be John Smith, Jack or Jane Doe.  The In Person Signer is able to change to their name when signing, but would be nicer to have it already blank.How can we accomplish this? Thanks,Brian

const jwtLifeSec = 24 * 60 * 60; // 1 day in seconds (3600 * 24) const dsApiClient = new ApiClient();dsApiClient.setBasePath(this.configService.get<string>('docusign.base_path'),); const results = await dsApiClient.requestJWTUserToken(this.configService.get<string>('docusign.integration_key'),this.configService.get<string>('docusign.user_id'),[this.configService.get<string>('docusign.scope')],this.privateKey,jwtLifeSec,);I added like that ti’s not working. it’s always return expire_in : 3600I wana more than. How can I do that Please someone help me.

{ "emailSubject": "Please DocuSign This NDA for ABC Company", "emailBlurb": "Please let us know if you have any questions.", "status": "sent", "templateId": "{{NDA Template}}", "customFields": { "textCustomFields": [{ "name": "entityID", "value": "1234" }] }, "templateRoles": [ { "roleName": "Customer", "email": "{{Signer Email}}", "name": "{{Signer Name}}", "tabs": { "textTabs": [ { "tabLabel": "company", "value": "ABC Company" } ] } } ]} 

Hi,One of my documents failed to deliver because of an incorrect e-mail addressBut all the API response lists is that the envelope has status “sent”:{ "resultSetSize": "3", "startPosition": "0", "endPosition": "2", "totalSetSize": "3", "nextUri": "", "previousUri": "", "envelopes": [ { "status": "sent", "...": "..." }, {...} ]} I would like to recognize an issue like this so I can report it in the module we’ve been building, but have been unable to do so with “listStatusChanges” or “Envelopes:Get”. Is it not the status?Am I missing some other field?Do I need a different request?

Hello,I’d like to send a draft envelope via DocuSign API. The application uses ASP.NET Core.What I’ve done so far, I retrieved the envelope with GetEnvelope and set Status as “sent”, then I called Update method to change the envelope status.The envelope contains one Document, and 2 Recipients. And I received an error as follows : Error calling Update: {"errorCode":"INVALID_REQUEST_PARAMETER","message":"The request contained at least one invalid parameter. Value for 'purgeState' must be 'documents_queued' or 'documents_and_metadata_queued' or 'documents_dequeued' or 'documents_and_metadata_and_redact_queued'."}I tried to set PurgeState as “documents_dequeued” (1) or “documents_queued” (2) but I received different error messages : (1) documents not in the purge queue, and (2) the envelope must be completed first, which is not the case.I just want to send the draft envelope with documents to sign after storing the envelope id in our database, s

Hello DocuSign Community,I am using the DocuSign Monitor API in my developer account and have noticed an unusual behavior in the API responses. Specifically, records with the data field having attributes such as IDs, IPs, or user agents are returned as a list of individual characters rather than as a single string.For example, instead of:"userId": "abab12"the API response gives: "userId": ["a", "b", "a", "b", "1", "2"]This behavior is not consistent across all records and only occurs in certain records. Is this the intended behavior of the API, or could it be a potential bug?