The Official DocuSign Java Client

Requirements

• Java 1.9+
• Free Developer Sandbox

Compatibility

• Java 1.9+

Note

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.

Installation

Note: DocuSign uses Eclipse with Maven for testing purposes.

Maven:

1. In Eclipse, create a new project by selecting File -> New -> Project.
2. In the New Project Wizard , expand Maven , then select Maven Project.
3. Leave Create a simple project unchecked.
4. Select Next , then provide a unique Group and Artifact Id.
5. In the directory where you've saved your project, open the pom.xml file.
6. In the pom.xml file, locate the dependencies node.
7. Add:

<dependency>
  <groupId>com.docusign</groupId>
  <artifactId>docusign-esign-java</artifactId>
  <version>3.11.0-RC2</version>
</dependency>

8. If your project is still open, restart Eclipse.

Dependencies

This client has the following external dependencies:

• io.swagger:swagger-annotations:jar:1.5.17
• org.glassfish.jersey.core:jersey-client:jar:2.29.1
• org.glassfish.jersey.media:jersey-media-multipart:jar:2.29.1
• org.glassfish.jersey.media:jersey-media-json-jackson:2.29.1
• com.fasterxml.jackson.core:jackson-core:jar:2.10.1
• com.fasterxml.jackson.core:jackson-annotations:jar:2.10.1
• com.fasterxml.jackson.core:jackson-databind:2.10.1
• com.fasterxml.jackson.datatype:jackson-datatype-joda:jar:2.10.1
• com.brsanthu:migbase64:2.2
• junit:junit:jar:4.12
• com.apache.oltu.oauth2:org.apache.oltu.oauth2.client:1.0.2
• com.auth0:java-jwt:3.4.1
• org.bouncycastle:bcprov-jdk15on:1.60

Code Examples

Launchers

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.

Proof-of-concept applications

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.

OAuth Implementations

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:

• JWT (JSON Web Token)
• [Implicit Grant] (https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-implicit)

Support

Log issues against this client through GitHub. We also have an active developer community on Stack Overflow.

License

The DocuSign Java Client is licensed under the MIT License.

Additional Resources

• DocuSign Developer Center
• DocuSign API on Twitter
• DocuSign For Developers on LinkedIn
• DocuSign For Developers on YouTube