• Microsoft .NET version 4.5.2+ (4.7 recommended)
• Free developer account

• .NET Standard 2.0. See .NET Standard Selector for details on versioning for the individual components in .NET Standard.
• .NET Core 2.0 or above.
• Microsoft .NET version 4.5.2+; we no longer support version 4.5.1.
• TLS 1.2

This SDK is provided as open source, which enables you to customize its functionality to suit your particular use case. To do so, download or clone the repository. If the SDK’s given functionality meets your integration needs, or if you’re working through our code examples from the DocuSign Developer Center, you merely need to install it by following the instructions below.

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

1. Create a new C# project, or open an existing one.
2. Open the Package Manager Console by either method:
   1. Select Package Manager Console along the bottom of Visual Studio
   2. Select Tools > NuGet Package Manager > Package Manager Console
3. In the Package Manager Console, type: Install-Package DocuSign.eSign.dll

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.10
• RestSharp v106.3.1
• System.ComponentModel.Annotations v4.5.0
• System.IdentityModel.tokens.Jwt v5.4.0

.NET Framework, version 4.5.2:

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

You can find on our GitHub a self-executing package of code examples for the eSignature C# SDK, called a Launcher, that demonstrates common use cases. You can also download a version preconfigured for your DocuSign developer account from Quickstart. These examples can use either the Authorization Code Grant or JSON Web Token (JWT) authentication workflow.

For details regarding which type of OAuth grant will work best for your DocuSign integration, see Choose OAuth Type in the DocuSign Developer Center.

For security purposes, DocuSign recommends using the Authorization Code Grant flow.

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

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

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