Right now I'm exploring potential options for automating the process of creating and configuring new DocuSign developer accounts via API calls, as this would allow my team to greatly reduce the work needed to setup and configure these accounts manually. I can't find any information in the current DocuSign API documentation that would allow for this, and the only question I could find online was Is it possible to create a DocuSign developer account via REST calls? from 2019.
Is it possible to create new developer accounts via an API? The POST requests utilized by the UI don't look to be designed in a way that would easily allow for this.
There's an endpoint in the eSignature API called Accounts:Create that enables creating new accounts.
However, it's important to note this:
This method is restricted to partner integrations. You must work with DocuSign Professional Services or DocuSign Business Development, who will provide you with the Distributor Code and Distributor Password that you need to include in the request body.
Related
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.
Helpers, I want to use Connect services with my DocuSign rest APIs integrated website. Could anyone help me out, Where can I get these in the GitHub? Basically the need is:
Once the document is fully executed, it will be routed via DocuSign connect to a folder which aligns with the name of the employee. This will require work on both the elected system as well as the DocuSign API to configure.
No problemo! These days, I suggest using an intermediate PaaS to queue and deliver the webhook notifications to your application which can live safely behind your firewall.
Here's a blog post on the technique. Note that we have PHP example software for this technique.
Once your PHP app is notified that an envelope is complete (fully signed), just download the documents from DocuSign and store them in your file system. Easy Peasy!
I have a standard DocuSign account and I want to add an integration key but I am not able to add that key as there is no option to in my standard account to add the key. Further, I want to hit DocuSign API either through nodejs-sdk or postman to create and send an envelope with the use of the template. So, for this what should I do? Can anybody help, please?
Sounds like you're just getting started with the DocuSign eSignature API. Welcome! We have a variety of resources that you will find helpful.
I would start here on the DocuSign Developer Center.
To begin experimenting with our API, you'll first need to create a demo sandbox account. Within this account, you can provision your own integrator keys. Later down the road, you will follow our "Go-Live" process to transition your integration to our paid, production environment.
Once you have your account created, I would suggest you check out this quickstart code example.
That should get you started!
You should create a new developer/sandbox account to create an integration key. You cannot do that in production.
For node.JS we have a few different resources you can use, the most complete one is our code example "launcher" that can be used as a full app to try the code. We also have a quickstart that you an use without configuring the API authentication part.
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.
Has anyone out there created an API to kick off docusign from within the equote module in Autotask?
I can't locate any references of autotask customers using docusign, nor docusign 'autotask' customers.
From the DocuSign perspective, DocuSign can be integrated with any system that allows integration. DocuSign offers both a REST API and a SOAP API, both of which enable you to add DocuSign eSignature transaction management functionality within the app being integrated. The DocuSign Developer Center contains a wealth of information about the DocuSign APIs (http://www.docusign.com/developer-center).
Since Autotask has an API that promotes "creating seemless integrations with leading...cloud- and managed-services tools" (http://www.autotask.com/main-pages/solutions/integrated-modules-features/open-api), I see no obvious reason that DocuSign couldn't be integrated with Autotask. i.e., provided that Autotask allows you to implement integration code that makes either REST API or SOAP API calls to another system, and use the API responses that you receive to subsequently implement the desired action(s) in Autotask (via their API), then integrating DocuSign with Autotask is certainly feasible.