Developer

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.

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 asynchron

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": [        "

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 { $envelopeSumma

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()); }compari

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

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

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?

How to create an envelope with one or multiple documents and a template using C# SDK. Documents are just for information references only, no tab/field on it.Template is the page which defined signer.

Is there currently a way to update a remote signer to be an embedded signer instead, after the signer has already been created? I tried using the envelopesAPI’s updateRecipients() method from the PHP SDK with a mapped version of my recipients with clientUserIds assigned to them (since this is my understanding of what makes a signer “embedded”). But, when doing so, I still wasn’t seeing an embedded signer’s view for the signer whose clientUserId I had updated.  

Hi! I just published a new YouTube video on automating field placement in Docusign templates using AutoPlace.You’ll learn how to:Set up AutoPlace in both the classic and new Docusign interfaces. Use anchor text to position fields accurately, even for dynamic-length documents. Leverage AutoPlace in API integrations for seamless workflows.Say goodbye to manual field alignment with this step-by-step guide! You can find it here:  Sofian Saoudi | Founder @Solusign Consulting - Docusign PartnerNeed help with Docusign?

Hi Successfully Complete 20 Attempts for Developer API testing, So when i click into Go Live then Status said , that can take upto 48 hours , but i am still waiting from last 7 Days for Approval, Docusign  is not Approving it .. Please help me to Approve it … i am very disappointed from Docusign Support , Very Very Confusing …  

Hi DocuSign community!Project Goal: I'm building a standalone web application for the Docusign hackathon where I want users to:Log in to my web app using their DocuSign account Once logged in to my application, they should see all their DocuSign contracts/envelopes The application is completely separate from DocuSign, just using DocuSign for authentication and fetching contracts I am planning to have a python application in the backendI'm new to DocuSign and would greatly appreciate if someone could guide me through the proper process of implementing this. What would be the right approach and what are the key steps I need to follow?Thank you in advance for any help!

After I moved the program to production, when I called envelopesApi.createEnvelope(accountId, envelopeDefinition), I got this error.Error while requesting server, received a non successful HTTP code 400 with response Body: '{"errorCode":"USER_AUTHENTICATION_FAILED","message":"One or both of Username and Password are invalid."}' what should i do  

Hi everyone! I’m running into an issue with DocuSign's envelope API recently and I’d love some more insight as to why.I start by creating a two-signer envelope. One signer is embedded from my external integration, and the other is added within the sender view in DocuSign. After adding signer fields, I use the "Preview" button to check that the fields show up for both signers. Both signers have clear signing fields. However, when I create a recipient view through my integration, no signer fields appear for the remote signer. Here is the envelope prior to pressing “Preview”.Blue = added externallyYellow = added during the “Sender view” Here’s how the fields for the signer I added within DocuSign's “sender” view appeared when I was using the “Preview” button.