This open-source SDK is provided for cases where you would like to make additional changes that the SDK does not provide out-of-the-box. If you simply want to use the SDK with any of the examples shown in the Developer Center, follow the installation instructions below.
Note: DocuSign uses Eclipse with Maven for testing purposes.
<dependency>
<groupId>com.docusign</groupId>
<artifactId>docusign-esign-java</artifactId>
<version>3.6.0</version>
</dependency>
This client has the following external dependencies:
DocuSign provides a sample application code referred to as a Launcher. The Launcher contains a set of 31 common use cases and associated source files. These examples use either DocuSign's Authorization Code Grant or JSON Web Tokens (JWT) flows.
If your goal is to create a proof-of-concept application, DocuSign provides a set of Quick Start examples. The Quick Start examples are meant to be used with DocuSign's OAuth Token Generator, which will allow you to generate tokens for the Demo/Sandbox environment only. These tokens last for eight hours and will enable you to build your proof-of-concept application without the need to fully implement an OAuth solution.
For details regarding which type of OAuth grant will work best for your DocuSign integration, see the REST API Authentication Overview guide located on the DocuSign Developer Center.
For security purposes, DocuSign recommends using the Authorization Code Grant flow.
There are other use-case scenarios, such as single page applications (SPA) that use Cross-Origin Resource Sharing (CORS), or where there may not be a user to interact with your Service Account. For these use cases, DocuSign also supports JWT and Implicit grants. For code examples, see the links below:
Log issues against this client through GitHub. We also have an active developer community on Stack Overflow.
The DocuSign Java Client is licensed under the MIT License.