Developer

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

When trying to create recipent view url from an envelope created from a template i recieve this error.How does one idenify the valid recipient? UNKNOWN_ENVELOPE_RECIPIENTThe recipient you have identified is not a valid recipient of the specified envelope.using PHP SDK $envelopeDefinition = new EnvelopeDefinition();$envelopeDefinition->setEmailSubject("Please Sign this Document");$envelopeDefinition->setTemplateId('f8c7bf7d-xxxx-1201e093fdc9');$envelopeDefinition->setStatus('created');$envelopeDefinition->setTemplateRoles([$signerTemplate]);$recipient_view_request = new RecipientViewRequest([ 'assertion_id'=> $assertion, 'authentication_method' => 'none', 'client_user_id' => $GLOBALS['JWT_CONFIG']['ds_impersonated_user_id'], 'return_url' => 'https://localhost', // Where to redirect after signing 'user_name' => $name, 'email' => $email,]);try { $envelopeSummary = $envelopesApi->createEnvelope($accountId, $envelopeDefinition); echo

Just updated from version 5.3 to version 8 of C# esign SDK (integrating w/ .NET Framework 4.8 MVC App) to take advantage of “IncludeAnchorTabLocations”.Didn’t realize it would mean completely rewriting everything to use async since the synchronous methods now just call the async method .GetResult()public OAuth.OAuthToken RequestJWTUserToken(string clientId, string userId, string oauthBasePath, byte[] privateKeyBytes, int expiresInHours, List<string> scopes = null) { CancellationTokenSource cts = new CancellationTokenSource(); return TryCatchWrapper(() => RequestJWTUserTokenAsync(clientId, userId, oauthBasePath, privateKeyBytes, expiresInHours, scopes, cts.Token).ConfigureAwait(false).GetAwaiter().GetResult()); }comparison of v7 (synchronous-safe) w/ v8 (synchronous-unsafe)Took me way too long to figure out why the application was hanging. Warning to anyone out there upgrading to v8 -- beware of deadlocks if you’re not using the async methods

I have an application that I am connecting to DocuSign esignature and connect. I have configured connect event to for recipient signed/completed and reassign. When a recipient signs the envelope it is working fine and sending a recipient-completed action via connect. However, when I reassign via the email sent as part of the envelope - connect sends a recipient-completed event for the initial signatory, immediately followed by a recipient-reassign event. I would expect it to only send the reassign event.  Is there a way to configure it to only send the reassign event in this scenario? Or is it possible in the recipient-completed event to tell whether the recipient actually signed or not?

Hi! I just published a new YouTube video on how to set up real-time data verification using Docusign Apps.You’ll learn:The difference between data validation and data verification. How to verify bank accounts, emails, addresses, and more. How to integrate third-party apps like Smarty for address checks or Twilio for email verification.This setup reduces errors, improves compliance, and speeds up document workflows! You can find it here:  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

We ❤️ hearing from our community! And we want this Developer Group to be a place for questions, collaboration, and insight from fellow community members and Docusign staff. Here’s the final step in the Docusign Discover Scavenger Hunt. Reply here with thoughts on the question above to finish the scavenger hunt and earn your shiny, new, exclusive Docusign Discover Scavenger Hunt Badge. 🏅Your badge will show up in your profile in the next week! 

We are currently working on integrating DocuSign with our MySQL database using the low-code ETL tool Integrate.io. During the integration process, we've encountered an issue related to the redirect URI.Our primary question is whether it is possible to integrate the DocuSign API without requiring the user-authorization step to generate an access token. Specifically, we want to confirm if the integration can be achieved using only the client secret and integration key, bypassing the need for individual user authentication.Additionally, we're wondering if there are any other authorization grants, other than JWT, that might be more suitable for this situation.

The customer is using our integration with DocuSign and has access to both a regular DocuSign account and a CFR Part 11 account. However, they are consistently directed to the regular DocuSign account, regardless of their actions. Even when the user logs out and explicitly logs in with the Part 11 account or sets it as their default, they remain unable to access it and are continuously connected to the regular DocuSign account.is there a way via the APIs to provide the customer the option to select between the regular and Part 11 accounts when using the same email address?

Why is API Usage Center showing zero API calls against my integration key? I have been testing using this key since last 1 week.

Hey everyone I'd like to personally invite you to participate in the Docusign Hackathon: Unlocked 💡 pre-registration is now open through November 19 and hackathon kicks off November 20 with prizes available up to $50k . Check out full details and sign up here.About the hackathon: Participants can use a suite of new Docusign for Developers platform capabilities and tools to create a solution in one of the following categories:AI-ify Your World - Use AI to unlock insights from your Docusign agreements and build innovative solutions. Hack-for-Good - Build an innovative solution with Docusign's developer platform to help a non-profit achieve its mission. Making the Impossible...Possible - Use Docusign technologies to code an innovative solution that tackles a seemingly impossible challenge.Hackathon Dates: November 20 - January 27Judging: January 27 - February 16https://unlocked.devpost.com/#hacklathon

I hope to achieve this function. I write my signature in the signature panel, then click sumit. The signature positions of the two documents I preset above can be signed. Can this function be achieved?