I'm trying to implement the DocuSign embedded signing. I'm kind of successful with few things left.
Without a developer account it's not possible to use the API, isn't it? I both have a pro account and a free account. Then I created a developer account with the same email and password I have for the free account. But when signing a document it says:
Demonstration Document Only.
Please see the image for better understanding:
Why is this appearing? Is it because I am using a developer account that has the same credentials as the free account? Will it disappear if I create a developer account with the same email and password I have for the pro account?
If I want to work with the API then will I have to control everything from developer account? I mean add template and other relevant signing stuff. Then what's the pro account for, which I've purchased?
Also, recipient is not receiving any email. Please see the images for better understanding:
I've asked the same thing at DocuSign support, but left with no answers.
DocuSign - API Certification Process
Integrations using DocuSign APIs must go through the Certification process to operate in the DocuSign production environment. During API Certification, the Integration is examined for following DocuSign’s Security & Design Requirements. We recommend reviewing our API Requirements Guide prior to beginning development as it will streamline the certification process later.
In order to avoid delays in processing please make sure the following items have been satisfied prior to beginning the process. These are explained in further detail in the API Certification Guide.
1) Customer or Partner sales contract has been executed.
2) 20+ test
transactions have already been executed.
Please review the following guides prior to beginning the API Certification process, a sample list of questions that will be asked has also been provided:
API PDF Security & Design Requirements | API PDF API Certification InfoSheet
Please e-mail any questions regarding the API Certification process to apicertifications#docusign.com or your DocuSign Account Manager.
Related
First of all, I apologize for eventual noob questions, we are very new to the DocuSign API and are currently trying to wrap our heads around which is the most correct way of accessing the API.
I will start with an overview of our use case. We recently purchased a DocuSign prod. Account with an Organization enabled.
We have a Partner which uses a CMS Tooling which integrates with said DocuSign Account. This Tool allows for the Backoffice to create envelopes with documents inside and a url which leads to the signin ceremony through the Templates that we create inside the DocuSign Account. This url is afterwards send to the customer for them to sign the documents in the envelope. This Part is working and is currently being used.
Now what we want to achieve on our side, we have a nextJS web-app which allows the same customers (Which are the receivers of the created envelopes in the step above, same e-mail in both steps) to sign-in our web-app. We want to show the customer in a dashboard, if there are envelopes for him open that he can sign and if this is the case we want to show him the url which leads to the signin ceremony.
We were able to see that as soon as an envelope for a certain User is created through the CMS Tooling, we can see that envelope in our DocuSign Prod Account.
Now our thought process was, to show our customer his open envelopes, we just fetch all open envelopes in our DocuSign Account which match the customers E-Mail.
Is there anything wrong with this process or are we overlooking something?
And if it is okay to proceed this way which of the OAuth Flows is the correct one to use for this case?
From my understanding, the JWT Flow seems like the most reasonable one? Since the Customers that need to sign the documents, will not have any DocuSign accounts.
What have you tried to solve the issue?
We tried using the direct API Access, which worked when set up correctly but since we didn't have a OAuth Flow in place the Access token is only valid for restricted amount of time obviously and has to be refreshed. Hence we have to think first about how to grant access correctly
I would love to hear, what the right approach would be to achieve our desired result.
Once again Apologies for this kind of question, just trying to have a better understanding before we start building :)
Best regards!
According to the use case you mentioned using JWT Grant is fine as users of your integration will use a single system account to log in, you should use JWT Grant.
I would recommend going with the below link to know more regards different use cases and check the knowledge
https://developers.docusign.com/platform/auth/choose/
https://developers.docusign.com/platform/auth/oauth2-requirements-migration/
A few weeks ago I implemented my first REST integration with the DocuSign API. Things over all went smoothly and with very little complaints. One particular hang up I experienced though was some confusion in regards to the Developer account and how it relates to the General account. I started with a developer account and used the test credentials to build my integration. Once my integration passed inspection it required me to choose another paid docusign account that the integration key would "go live" on. This is all pretty straight forward.
The curve ball came when I actually went to purchase the API account and it said, "you aren't eligible to purchase this". There isn't clear instruction on the site, so my questions are:
1.) In what order does the account creation need to go? Developer > General (Paid) > API Plan (Paid)?
2.) Does DocuSign expect the user, as the customer, to purchase the plan or should that plan be purchased through my developer account?
I tried to reach out to customer service directly, but it was pretty much a, "give us all of your money, then we'll help" situation. I have several customers who are interested in this integration, but I'm not comfortable presenting this as an option until I get a better understanding of the process. Any advice is greatly appreciated.
In general, DocuSign does require a paid account to complete the Go Live process. If you - the integration owner - will not be using DocuSign yourself, you would want to reach out to the [DocuSign Partners program][1] to receive a free Partner account that can hold your integration key instead of having to purchase one.
From there, the end users of your integration can purchase their own DocuSign accounts. You could potentially act as a reseller of DocuSign if you were so inclined.
https://www.docusign.com/partners/become-partner
If you still need assistance, please email apihelp#docusign.com with this information. Someone will help you right away.
I am trying to integrate our web app with DocuSign. We expect our web app customers will authenticate and grant consent to our app to make API calls on behalf of their DocuSign accounts. Then our app will create envelopes (using access tokens to customer DocuSign accounts) and allow our app users to sign them using embedded signing.
We've built a prototype using demo account and everything works like a charm.
The only thing what is still unclear for me is how it is supposed to work after going live.
Am I right that our customer will be charged each envelop sending, since our integration makes call on behalf of their account?
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
Could anyone advise on the matter. Thanks!
Am I right that our customer will be charged each envelope sending, since our integration makes call on behalf of their account?
A. Yes, you're right. If your customer logins in to DocuSign using their own DocuSign user account, then their DocuSign account is charged. Your own DocuSign account is not involved, at all, in this scenario. Your client id (integration key) can be used by any DocuSign account user with their own account, once they grant consent to it.
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
A. I don't believe that the standard eSignature plan includes support for embedded signing.
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
A. Either Advanced Developer or a "regular" eSig account that supports embedded signing. This is for your testing purposes. If you use a regular account that supports embedded signing then your other company groups can share the account for use in sending out agreements for signature.
Also
Please sign up as an ISV with DocuSign via https://partners.docusign.com
(no charge.) Being a registered partner provides you with additional information and enables you to use the partner use license to sell your app to DocuSign customers.
Pro-tip: use your developer account to automatically test your app. Preferably once a day. New releases are first launched on the developer system about a week before production. DocuSign has thousands of tests to guard against regression bugs. But it is possible for a bug to slip through. If you detect any issues on the developer system then DocuSign will typically stop the production deployment to fix the issue.
Added
Re error message when a feature is not enabled: see this question.
Re which plans include the embedded signing feature: sorry, I don't have that information.
I can't find the Docusign Connector thing anywhere; what little info I could find in writing seemed to state it could be found under Admin, but not where. Please don't refer me to a video unless it's only about what I'm asking; it's an accessibility issue for me.
I'm trying to get a google doc signed by someone; apparently I either need to set up the Connector thing or convert to a pdf? I'm very confused by the videos in lieu of an actual how-to with links and words and stuff.
You need DocuSign for Google Drive.
https://www.docusign.com/partner/docusign-google-drive
https://gsuite.google.com/marketplace/app/docusign_esignature/66351547828?hl=en-US&pann=cwsdp
That would enable you to sign a Google Doc directly.
DocuSign has an off the shelf product for using DocuSign from Google Office apps.
DocuSign also has the Connect feature which provides webhook notifications to your API program when various events occur with your DocuSign envelopes. For example, you can ask to have your software program notified when envelopes are completed (completely signed and finalized). To use DocuSign Connect, goto the eSignature Administration tool and look for Connect in the Integrations section of the righthand navigation column.
Some DocuSign account plans don't include the Connect feature, so it isn't always there. Talk to DocuSign sales if need be. Remember that the Connect webhook system is for developers.
I want to add the docusign API with my application I create the docusign development account. I dont want to go mail to the signer. Its work automatically when my a user enter in my website and click to button go to docosign application. How i can do that. any one can help me?
Marco is right that you need to be careful about how you authenticate users who are coming into your application. The proof that the signature took place is only as strong as your authentication system. DocuSign has over 7 security options and the e-mail activation gives it more validity.
Having said all that you can absolutely embed DocuSign into your application. Here is a walkthrough on how you can embed DocuSign into your web application: https://www.docusign.com/developer-center/quick-start/embedded-signing
You cannot have a link in your application because this would reduce the value of the electronic signature: it would be more difficult to proof that the real signatory signed the document if the link was accessible not only to the recipient of the email.
DocuSign wants to be sure that their servers are the only one who manage the links for signatories.
There is no API to get the link.