hao-qian/docusign-csharp-client

The Official DocuSign C# Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.

The Official DocuSign C# Client

Requirements

• Microsoft .NET version 4.5+ (4.6.1 recommended)
• Free Developer Sandbox

Compatibility

• .NET Standard 2.0. See .NET Standard Selector for details on versioning for the individual components in .NET Standard
• .NET Core 2.0
• Microsoft .NET version 4.5+
• TLS 1.2

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

NuGet Package Manager:

1. Create a new C# project, or open an existing one.
2. Click Tools -> NuGet Package Manager -> Manage NuGet Packages for Solution.
3. Search for DocuSign.
4. Select DocuSign.eSign.dll.
5. Click the check box next to your project name.
6. Click Install.

Package Manager Console:

1. Open or create a new C# project.
2. Open the Package Manager Console by either:
3. Clicking Package Manager Console along the bottom of Visual Studio
4. Clicking Tools -> NuGet Package Manager -> Package Manager Console
5. In the Package Manager Console, type: Install-Package DocuSign.eSign.dll

Dependencies

This client has the following external dependencies:

.NET Standard v2 and .NET Core:

• Microsoft.CSharp v4.5.0
• Microsoft.IdentityModel.Protocols v5.4.0
• Newtonsoft.Json 11.0.2
• Portable.BouncyCastle v1.8.2
• RestSharp v106.3.1
• System.ComponentModel.Annotations v4.5.0
• System.IdentityModel.tokens.Jwt v5.4.0

.NET Framework, version 4.5:

• BouncyCastle v1.8.1
• Microsoft.Identity.Model.Logging v1.1.4
• Microsoft.IdentityModel.Tokens v5.1.14
• Newtonsoft.Json v10.0.0.1
• RestSharpSigned v105.2.3
• System.IdentityModel.Tokens.Jwt v5.1.4

Code Examples

Launchers

DocuSign provides a sample application referred to as a Launcher. The Launcher contains a set of 14 common use cases and associated source files. These examples use DocuSign's Authorization Code Grant flow.

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 Startexamples 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 (coming soon)

Support

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

License

The DocuSign C# Client is licensed under the MIT License.