Developer

Hi Team, I am using the DocuSign feature in my current application. Currently, we have two servers, DEV and QA, and I have only one developer (demo) account.What I need is, if I trigger the mail through my DEV server using the integration key, it should trigger the DEV URL in the webhook whenever an event happens for that particular envelope ID. I need the same functionality in the QA server as well, without any conflicts. If I use the same integration key for both DEV and QA with different webhook configurations in the webhook connect feature, what will happen? Also, what is the best/relevant way to approach this scenario? Regards,Adarsh

I have this error when i’m trying to send an envelope:"errorCode":"ACCOUNT_LACKS_PERMISSIONS","message":"This Account lacks sufficient permissions. Account does not have permission to set 'display' or 'signermustacknowledge' properties on document ..."this is the production account. Testing in the developer account i never get that error. What is the soultion for this issue ?  

I tried integration with Onedrive but, Error page is shown.I used personal account on microsoft.how can i integration with onedrive on docusign? It’s error page screenshot. 

Hi, It seems Navigator API is new. so previously developer need to load their list of documents by using envelopes api ?Imnot sure as well why navigator qpi right now is only have retreive a list of agreements and have no different than list envelope documents here I’m developing social medias app where I need to create docusign accounts on our backend (this is done by admin-docusign API right?), so user’s data synced with docusign and can be open with any docusign’s app integrated app. 

Jumping in late, but trying to change to OAuth for authentication.Created a new app, but not seeing where to consent. (OAuth error no consent) Tried following instructions here:https://www.docusign.com/blog/developers/oauth-jwt-granting-consentfor admin consent.  Points to send support email at go-live if missing admin piece.Tried emailing support, got a not monitored email.  Tried logging into support, but always get error email / password. Can’t figure out how to get a call back, we do have live integrations in place.  

when trying to go live with my docusign app, the first set of review passed but after i enter details of the production account, there seems to be another review which is declined without any reason.

Hello,I am using the createBulkSendRequest() function from docusign.BulkEnvelopesApi to send a bulk signing request to 20-30 signers. However, I would also like to send a carbon copy of the documents to the manager.Currently, adding the manager as a carbon copy (CC) recipient in the bulk list results in the manager receiving 20-30 individual emails—one for each signer. Is there a way to send a bulk request to 20-30 recipients while ensuring the manager receives only one email or a single copy of the documents? Thank you.

Hello!  I’m working on creating an integration using the Apex Toolkit and I’m having an issue with my envelope recipient routing order and sequence order. I’ve noticed that when constructing my envelope recipients with the envelope.withRecipients it automatically assigns my recipients a routing order and sequence number based on their order in the recipient list. I need to be able to assign those values myself so that they can align with a template I’m matching my envelope to. Any suggestions on how I can do this would be greatly appreciated! 

1. pass the go-live review,2. then select a go-live account,input the production email3.input passwordthen get error, does anyone have idea?Thanks a lot

Salesforce fields are not being displayed in Maestro WorkflowsHow can I add them?

Is there a way to customize the email sent from the Agent to customer to not have the originating senders name to be on the email from the API? On the image attached (everything in red) is there a way to put the Agents name in place of the original sender's name so the customer recognizes the document? 

We have an application the is integrated with DocuSign via the C# SDK.We allow users of our app to sign into their own DocuSign accounts to create and send envelopes which is then facilitated by the various SDK API calls.The users can successfully create and send envelopes, however if they are signed into their own accounts Connect is not capturing any events to forward to our webhook.If we sign in and use the account that is associated with our integration to send and create envelopes Connect forwards the events to our webhook as expected.Am I missing some settings within our configuration of Connect or are you not able to capture events across accounts?Is there any solution to this instead polling for envelope / recipient status changes? 

I see this documentation of docusign JS embedding to get the event just for Signing view. Is this not relevant for when we create Preview urls of Envelope? I have created and envelope and opening up a preview within an iframe. I wanted to catch events directly in my parent window but doesnt seem to be working. 

Hi,Im using the Docusign eSignature REST API (c#) to create envelopes for recipients for signing.I require my recipient to either sign the document by selecting a signature or by free hand drawing signature. Currently only the option to select a signature is showing, I see no option to choose to draw as well as select a predefined signature. I have gone into the Settings page then Signing Settings and configure the Signature Adoption configuration, and enabled the option for drawn eSignatures as suggested here :Drawn Signature | Community but this didn't work for me.This is my code: - as you can see i just have one signature achor , and one signed date achor.  SignHere signHere = new SignHere  {      AnchorString = "**signature_1**",      AnchorUnits = "pixels",      AnchorYOffset = "10",      AnchorXOffset = "20"  };  DateSigned mydate = new DateSigned  {      AnchorString = "**signed_date**",      AnchorUnits = "pixels",      AnchorYOffset = "2",      AnchorXOffset = "20",      FontS

Hi, is there event callback for elastic template, when clickwrap is rendered and user first click on agreed and than another modal show to send document to email, so I’m curious if there is event when user clicked on request document via email?

Hello,I'm having trouble creating the envelope when I set the delivery method to SMS or WhatsApp. In my tests, I send the following JSON to the Docusign API:{  "emailSubject": "Test AppBuilder - 1_1",  "documents": []  "recipients": {    "signers": [      {        "roleName": "CONTRACTOR",        "name": "Carlos Oliveira",        "email": "",        "recipientId": "",        "routingOrder": "1",        "clientUserId": "",        "deliveryMethod": "SMS",        "phoneNumber": {          "countryCode": "55",          "number": ""        },        "tabs": {},        }    ],  },  "status": "sent",  "sentDate": 1736456976955,  "completeDate": null}The country code is the country code of Brazil.I get an error while requesting server, received a non successful HTTP code [400] with response Body: "errorCode": "INVALID_PHONE_NUMBER_FOR_RECIPIENT","message": "The Phone number is invalid. Envelope definition is missing a phoneNumber for recipientId: "

Hi Team, Working on an integration utilizing template and sending an envelope. Before sending I want to generate a preview url. This preview url is different everytime I hit the api. How long does this preview url lasts? whats the best practice on generating sender views? Should I retain the generated url until the envelope is sent ? Sender API Regards, Karun

I am writing an app to download documents after being signed to integrate into our in-house application.I am having a little trouble with “public static bool HashIsValid(string secret, string payload, string verify)”In the development environment this works without error.I create a document, sign it and via connect the json and headers are sent to webhook.siteI pick up the json and x-docusign-signature-1.  I place the HMAC from development connect as the secret, the json as the payload, and x-docusign-signature-1 as verify and my json verifies.In production I do the same, I place the HMAC from admin connect as the secret, the json as the payload, and x-docusign-signature-1 as verify, but it always fails.I have also published this application out for testing.  I change connect to use the URL of my application.  I read the HMAC for development, the json and x-docusign-signature-1 are read from what DocuSign sends.  The HMAC is validated and the document is stored in the appropriate direc

We noticed that DocuSign provides a JavaScript library that seems to enhance the embedding process. However, our project is built with Angular and TypeScript, and we couldn't find documentation specific to TypeScript integration. Could you please share any documentation, resources, or tutorials that could guide us in integrating the library effectively in our environment? Your assistance would be immensely helpful.

I am using an C# example for sending documents to recipients and that works, but I want to send to an agent since I will not know the recipients, but when I add the Agent, the email never prompts for the signer emails to forward to?    Agent agent1 = new Agent   {       Email = signerEmail,       Name = signerName,       RecipientId = "1",       RoutingOrder = "1",   };     // Add the recipients to the envelope object   Recipients recipients = new Recipients   {       Agents = new List<Agent> { agent1 },             };   env.Recipients = recipients;

We have submitted to go live multiple times. We get no details on WHY it keeps being declined, and it is extremely frustrating. Now I’m being routed here to post this, hoping someone can assist. Have no idea what in the heck we are doing wrong. Absolutely abysmal experience so far. 

I want to integrate DocuSign e-signature into my React app, but I can't find any documentation. Could you please share the documentation or guide me on how to do it?

Package: DocuSign.eSign.dll (8.0.0.0)Environment: Asp.Net CoreLanguage: C#Demo code:DocuSignClient dsClient = new DocuSignClient(DocuSignClient.Demo_REST_BasePath);DSAuth.OAuth.OAuthToken oaTok = default!;List<string> scopes = new List<string>() { "signature", "impersonation" };byte[] privateKey = File.ReadAllBytes("c:\\Test\\Private.key");DSAuth.OAuth.OAuthToken tok = dsc.RequestJWTUserToken( Properties["IntegrationKey"],    Properties["UserId"],    Properties["AuthServer"],    privateKey,    1,    scopes); I have verified that the values for IntegrationKey, UserId, and the private key are set up in DocuSign correctly and turned on, and that I am using the correct values. I have verified that the authentication server is the correct one (demo.) But when I run this, it just hangs. No response. I have set this up to run asynchronously, and the same thing: it never resolves. This used to work, but it broke some time in late October I think it was. All of the example code I

We are currently implementing a DocuSign Esignature integration. Our application is multi-tenanted.  What is the best way to handle users who need to sign a document via an embedded URL without logging in. My understanding is that the user would need to log into DocuSign to generate the URL or have a embed url sent via API by a sender account. Is there a way to avoid this requirement?Some of our user will not have a DocuSign account and would not be willing to sign up. Is there another way to get the URL with minimum user interaction?Our ideal scenario would be that the user logs into our application, selects from a list of envelopes, and signs the document via a embed URL. The user should not have to login to docuSign. 

Hi DocuSign Support Team,I am reaching out regarding an issue with the API endpoint for creating contacts.When making the following POST request to create a contact:curl --location 'https://api.docusign.net/restapi/v2.1/accounts/{accountId}/contacts' \--header 'Content-Type: application/json' \--header 'Authorization: Bearer {access_token}' \--data '{  "contacts": [    {      "name": "John Doe",      "emails": [        "john.doe@example.com"      ],      "organization": "Example Corp",      "shared": "true"    }  ]}'We receive the following error response:{    "errorCode": "ACCOUNT_SPECIFIED_INVALID",    "message": "The account id provided does not exist, or is improperly formatted."}However, when the request method is changed to GET and the body is removed, the call works as expected, confirming that the account ID is valid.Could you please assist in identifying the root cause of this issue? It appears the endpoint is not processing POST requests correctly for contact creation.Thank y