Developer

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?

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?Book a call with me🌎 www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube

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. But, here’s how it looks when creating a recipient view for that same signer. Any ideas as to why this is? 

Dears,The requirement is to have the signatures of all the approvers of Purchase Contract in the contract document generated in SAP.There is already a workflow setup in SAP for the Approval process, now once a user approves the contract in SAP inbox, I need to get the signature of the approver on the document and send the workflow to further approvals.Is there any API to directly open the document for signing and sending the response back to SAP System!?Or any feasible approach or insights would be helpfulThanks

Hi,I’ve developed an integration with Docusign, and initiated the review process multiple times after the integration has been rejected for unknown reasons. (The request logs that where supposed to tell me the reasons didn’t work). Now, I started the review process again but with a manual process through the support ticket I opened. I’m still waiting for their response until now. What can I do and who can I contact about that?

JWT GrantI am new to Docusing and was going through the documentation. I stumbled upon the Authorization Grant of the Platform 101 docs, and read the above excerpt. Can anyone clarify what does this mean If you use a single login for all users in your integration, you should use JWT Grant.  Using single login for all of the integration users mean what? Does that all follow the same login/signup method or the same credentials?

Hi guys, I want the signers to be able to sign all pages of all documents, i.e. page by page they can click on the (SignHere) tab.I can also consider the option of them signing only the first page and the signatures being replicated on the others.Is this possible using Java SDK?

import axios from "axios";import docusign from "docusign-esign";import fs from "fs";import path from "path"; const getAccessToken = async () => {  const apiClient = new docusign.ApiClient();  apiClient.setOAuthBasePath("account-d.docusign.com");   const privateKey = fs.readFileSync(    path.join(process.cwd(), process.env.NEXT_PUBLIC_SIGNUP_CLIENT_SECRET || "")  );  const response = await apiClient.requestJWTUserToken(    process.env.NEXT_PUBLIC_SIGNUP_CLIENT_ID,    process.env.NEXT_PUBLIC_SIGNUP_USER_ID,    ["signature"],    privateKey,    3600  );   return response.body.access_token;};where i can find these issues? tried to use this, but have error AUTHORIZATION_INVALID_TOKEN 

Hi! I just published a new YouTube video about simplifying your sales process with Docusign and Pipedrive integration.You’ll discover:The limitations of the standard Docusign for Pipedrive integration. How to enhance workflows using third-party integrations like Docusign on Pipedrive. A fully automated custom integration using Make.com to generate documents, track statuses, and sync data seamlessly—no manual steps needed.Learn how to save time and streamline your sales process with automation. 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 create sendview url and got the ip address is 20.236.201.80.So we nslookup it:nslookup apps.docusign.comServer: 223.5.5.5Address: 223.5.5.5#53 Non-authoritative answer:apps.docusign.com canonical name = apps-geo.docusign.com.akadns.net.apps-geo.docusign.com.akadns.net canonical name = apps-na.docusign.com.akadns.net.Name: apps-na.docusign.com.akadns.netAddress: 20.236.201.80 but we not find this ip in the Docusign endpoint IP addresses of https://www.docusign.com/trust/security/esignature. for these near range is only include: IP range: 20.236.201.102 - 20.236.201.103 CIDR notation: 20.236.201.102/31  we not find this update in the recently Release Notes.please update the new range which need update. thanks. FreeLink🌍 DocuSign Partner | Partner Profile🏆 2024 APAC Reseller Growth Partner of the Year🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant.📊 DocuSign Community Leaderboard Top 5 contributor.🚀 Ex

I have use case where I need to uniquely identify a recipient. With REST API, it works fine. However, with SOAP, response does not return RecipientId as documented.https://demo.docusign.net/api/3.0/dsapi.asmx?op=RequestStatus<RequestStatusResponse xmlns="http://www.docusign.net/API/3.0"> <RequestStatusResult> <RecipientStatuses> <RecipientStatus> <Type>Signer or Agent or Editor or Intermediary or CarbonCopy or CertifiedDelivery or InPersonSigner or SigningHost</Type> <Email>string</Email> <UserName>string</UserName> <RoutingOrder>unsignedShort</RoutingOrder> <Sent>dateTime</Sent> <Delivered>dateTime</Delivered> <Signed>dateTime</Signed> <Declined>dateTime</Declined> <DeclineReason>string</DeclineReason> <AutoRespondedReason&