---
title: ".NET eSignature SDK for C# Developers | BoldSign"
description: ".NET eSignature SDK for C# apps: send documents, embed signing in your app, and track each request by webhook. Start in a free API sandbox."
url: "https://boldsign.com/dotnet-sdk-electronic-signature/"
---

.NET SDK

# eSignature SDK for .NET and C# applications

Send documents for signature from your C# code with the BoldSign .NET SDK. Signers sign in their browser from an email link, or inside your app.

[Create free API sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- Install from NuGet
- API key or OAuth 2.0

Your CompanyPreviewSend

Assignee

David

SERVICE AGREEMENT

Company signatureSign here\*

Client signatureSign here\*

AgreementsController.cs.NET SDK

var documentClient = new DocumentClient(apiClient);var signer = new DocumentSigner( name: "David", emailAddress: "david\@cubeflakes.com",var request = new EmbeddedDocumentRequest(){ Title = "Service Agreement", Signers = new List\<DocumentSigner> { signer }, SendViewOption = PageViewOption.PreparePage, ShowToolbar = true};var embeddedSendCreated =  documentClient.\
    CreateEmbeddedRequestUrl(request);var sendUrl = embeddedSendCreated.SendUrl;

Sample .NET web app at yourapp.example with BoldSign embedded: the prepare page of a service agreement assigned to David, with Preview and Send buttons, beside the C# code from BoldSign’s .NET SDK docs that creates this embedded request

Trusted by 100,000+ organizations worldwide

*Picture: BoldSign rated 4.7 out of 5 on G2*

![Samsonite](https://boldsign.com/assets/landing/trustbar/samsonite.svg)

![Ryanair](https://boldsign.com/assets/landing/trustbar/ryanair.svg)

![Hyatt](https://boldsign.com/assets/landing/trustbar/hyatt.svg)

![Sony](https://boldsign.com/assets/landing/trustbar/sony.svg)

![Crumbl Cookies](https://boldsign.com/assets/landing/trustbar/crumbl.svg)

![Payroc](https://boldsign.com/assets/landing/trustbar/payroc.svg)

![Cost Plus](https://boldsign.com/assets/landing/trustbar/costplus.svg)

The problem

## Why is adding eSignatures to a .NET app harder than it looks?

Signing is quick. Legal validity, identity checks, reminders, an audit trail, and a sealed PDF are not. With the BoldSign .NET SDK, you get all five from your C# code.

- ### The signature is the easy part

  Capturing a drawn or typed signature takes a day. The record around it takes months.

- ### The record has to hold up

  A sealed PDF needs a trusted certificate that you buy, store, and renew. Every action needs a timestamp.

- ### You own every fix

  Reminders, status tracking, and storage are all code your team writes, runs, and patches.

The solution

## How can you add eSignatures to a .NET app without building them?

The BoldSign .NET SDK gives your C# code two routes to a signature. BoldSign runs the signing behind both. Your app creates the document, names the signers, and tracks what comes back.

- ### Send for signature from your code

  Your app passes the document and signers to BoldSign, and each signer gets their own email link.

- ### Embed signing in your product

  BoldSign returns a signing URL you drop into your own page. The signer signs the document inside your app, without leaving it.

Capabilities

## What can your C# app do with the .NET eSignature SDK?

With the BoldSign .NET SDK, your C# app handles the whole signing flow. Every completed PDF is digitally signed.

- ### Send documents for signature

  Send a contract or form to one signer or several, in the order you set.

  [See the eSignature API](https://boldsign.com/esignature-api.md)

- ### Sign inside your app

  Show the signing page in your own .NET pages, so the signer never leaves your product.

  [See embedded signing](https://boldsign.com/embedded-signatures.md)

- ### Prepare and send in your app

  Your users drag fields onto the PDF and send it, all inside your .NET app.

  [See embedded sending](https://developers.boldsign.com/embedded-request/create-embedded-request-link-from-template/)

- ### Send from templates

  Store a reusable template once, then send it to new signers from C#.

  [See templates](https://boldsign.com/electronic-signature-features/templates.md)

- ### Check who is signing

  Set a check per signer: access code, email code, SMS code, KBA, or ID verification.

  [See signer authentication](https://boldsign.com/electronic-signature-features/signer-authentication.md)

- ### Know when it is signed

  Receive each status change on your webhook endpoint, then pull the signed PDF and audit trail.

  [See webhooks](https://developers.boldsign.com/webhooks/setting-webhook/)

Works in: server-side .NET apps on Windows, Linux, and macOS. Keep the SDK on your server, since it carries your API key.

Get started

## How do you start sending from a .NET app?

You send from a .NET app with the BoldSign .NET SDK in 3 steps: install, authenticate, and send.

1. ### Install from NuGet

   `dotnet add package BoldSign.Api`

   Runs on .NET Framework 4.5.2 or later, and on .NET 5 or later.

2. ### API authentication

   `var apiClient = new ApiClient("https://api.boldsign.com", "Your-API-Key-Here");`

   Connect your API key, or use an OAuth 2.0 token.

3. ### Send the document

   `documentClient.SendDocument(...);`

   The result holds the document ID.

Using an AI coding tool? Connect BoldSign’s coding assistant (MCP), then try this prompt. [Set up the coding assistant](https://developers.boldsign.com/coding-assistant/mcp-server/).Add a button to my ASP.NET Core app that sends a document with the BoldSign .NET SDK.

[See the full C# walkthrough](https://developers.boldsign.com/sdks/net-sdk/)

Why BoldSign

## Why choose BoldSign for .NET developers

BoldSign suits .NET teams that want signing in their product without building or maintaining it.

- ### One package for the whole flow

  Sending, embedded signing, templates, and signer identity checks all come from the BoldSign .NET SDK.

- ### Write .NET code with your AI coding tool

  BoldSign’s [coding assistant (MCP)](https://developers.boldsign.com/coding-assistant/mcp-server/) plugs into VS Code, Cursor, or Claude. It answers SDK questions from BoldSign’s docs, with no API key.

- ### Build it all before you pay

  Build and test the whole flow in a free sandbox, then change the key at go-live.

- ### Signers need no account

  Nobody who signs needs a BoldSign account or an app download.

- ### Legally binding signatures

  Signatures you collect with BoldSign are [legally binding](https://boldsign.com/electronic-signature-legality.md) under the ESIGN Act, UETA, and eIDAS.

Security

## How are documents sent from your code kept secure?

BoldSign encrypts every document twice with AES-256. Its security controls are independently audited for SOC 2 Type 2. Your account’s Compliance page lists each standard BoldSign meets, shown below.

Settings

Compliance

BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.

- ![US flag](https://boldsign.com/assets/landing/compliance/residency-de93bd.svg) Data Residency

  Active (US - Global)

  Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.

  [View Data Residency Policy](https://boldsign.com/security-policy.md)

- ![HIPAA logo](https://boldsign.com/assets/landing/compliance/hipaa-c34e9b.png) HIPAA Compliance

  Enabled

  Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

  [View Details](https://boldsign.com/hipaa-overview.md)

- ![PCI DSS logo](https://boldsign.com/assets/landing/compliance/pci-960f14.png) PCI DSS

  Compliant

  Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

  [View PCI DSS Policy](https://boldsign.com/security-policy.md)

- ![CCPA logo](https://boldsign.com/assets/landing/compliance/ccpa-e62333.png) CCPA & CPRA

  Compliant

  Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

  [View Privacy Policy](https://boldsign.com/privacy-policy.md)

- ![AICPA SOC logo](https://boldsign.com/assets/landing/compliance/soc2-b31494.png) SOC 2 Type II

  Compliant

  BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

  [Request SOC 2](https://boldsign.com/soc2-overview.md)

- ![US flag](https://boldsign.com/assets/landing/compliance/esign-de93bd.svg) UETA & ESIGN

  Compliant

  BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

  [View UETA & ESIGN Policy](https://boldsign.com/ueta-and-esign-act-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-ses-677fe1.svg) eIDAS (SES)

  Compliant

  BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

  [View SES Policy](https://boldsign.com/simple-electronic-signature-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-qes-677fe1.svg) eIDAS (QES)

  Enabled

  Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

  [View QES Policy](https://boldsign.com/qes-overview.md)

The compliance panel in your BoldSign account.

For IT and procurement

## Security and procurement documents for eSignature

IT and procurement teams can read BoldSign’s [security policy](https://boldsign.com/security-policy.md), data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.

- Sign-in

  ### Single sign-on and user provisioning

  Works with Microsoft Entra ID.

  [See features by plan](https://boldsign.com/electronic-signature-pricing/?plan=webapp)

- Audit report

  ### SOC 2 Type 2 report

  Available on request from BoldSign.

  [Request the SOC 2 report](https://boldsign.com/compliance-request-form.md)

- Data protection

  ### Data processing agreement

  Includes the EU Standard Contractual Clauses and the UK Addendum by reference.

  [Read the data processing agreement](https://boldsign.com/dpa.md)

- Data protection

  ### Subprocessor list

  Every third party BoldSign uses to process data.

  [See the subprocessor list](https://boldsign.com/subprocessors.md)

- Service

  ### Service level agreement

  Uptime, support response times, and service commitments.

  [Find it in the Legal Center](https://boldsign.com/legalcenter.md)

What it costs

## Limits and costs to know before you send from .NET with BoldSign

The BoldSign .NET SDK is free to install from NuGet. Live documents run on a BoldSign API plan. Prices are in USD.

- $30 Enterprise API plan, per month 40 envelopes included, then $0.75 each.

[See all limits and add-on prices](https://boldsign.com/electronic-signature-pricing/?plan=api)

Good to know

- 2,000 API requests an hour per account The sandbox allows 50 an hour.

Related

## More guides for building eSignatures in .NET

- Page

  ### All eSignature SDKs

  Compare the five official BoldSign SDKs.

  [See all SDKs](https://boldsign.com/electronic-signature-sdk.md)

- Page

  ### Embedded signing

  Open the signing page inside your own app.

  [See embedded signing](https://boldsign.com/embedded-signatures.md)

- Guide

  ### ASP.NET Core example

  Add BoldSign signing to an ASP.NET Core project.

  [Read the guide](https://boldsign.com/blogs/integrating-boldsign-esignature-apis-in-asp-net-core-app.md)

- Guide

  ### Build an AI agent

  Let an AI agent send documents through the BoldSign MCP server.

  [Read the guide](https://boldsign.com/blogs/build-ai-agent-boldsign-mcp-claude-api.md)

Common questions

## Questions about the .NET eSignature SDK

### Is there a .NET digital signature SDK?

Yes. The BoldSign .NET SDK, published on NuGet as BoldSign.Api, is BoldSign’s official SDK for .NET and C#. People sign electronically, and BoldSign [seals each completed PDF with an AATL certificate](https://support.boldsign.com/kb/article/59).

### Can I add eSignatures to an ASP.NET Core app?

Yes. The BoldSign .NET SDK installs in ASP.NET Core like any NuGet package. The [ASP.NET Core guide](https://boldsign.com/blogs/integrating-boldsign-esignature-apis-in-asp-net-core-app.md) walks through a full example.

### How do webhooks work with the .NET SDK?

Webhooks are set up once in your BoldSign account, under API then Webhooks, not in the SDK. BoldSign posts each status change to your HTTPS endpoint, so your .NET app never polls for status. [Set up a webhook](https://developers.boldsign.com/webhooks/setting-webhook/).

### Does the .NET SDK support OAuth 2.0?

Yes. Pass a bearer token to the SDK’s configuration instead of an API key. [See OAuth 2.0 setup](https://developers.boldsign.com/authentication/oauth-2-0/).

### How do I use the Europe, Canada, or Australia region?

Pass your region’s base URL when you create the API client, such as api-eu.boldsign.com for Europe. US accounts need no change. [See all base URLs](https://developers.boldsign.com/sdks/net-sdk/).

### Can I test the .NET SDK for free?

Yes. Create a [free BoldSign API sandbox](https://account.boldsign.com/signup?planId=1076), then use its API key with the .NET SDK. Sandbox documents are for testing only.

Get started

## Send your first document from C\#

Open a free BoldSign API sandbox, install the .NET SDK from NuGet, and send your first document.

[Create free API sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- 30-day free trial
- No credit card required

*Picture: A completed employment contract: signed by John Doe on 11/03/2026, all parties have signed*

Last updated: October 18, 2026
