---
title: "BoldSign Python SDK"
description: "Python eSignature SDK: send documents from your Python code, install from PyPI, and track every request by webhook. Start in a free API sandbox."
url: "https://boldsign.com/python-sdk-electronic-signature/"
---

Python SDK

# eSignature SDK for Python applications

Send documents for signature from your Python code with the BoldSign Python 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 PyPI
- API key or OAuth 2.0
- Webhooks for every status change

Your CompanyPreviewSend

Assignee

David

SERVICE AGREEMENT

Company signatureSign here\*

Client signatureSign here\*

agreements.pyPython SDK

document_api = boldsign.DocumentApi(api_client)signer = boldsign.DocumentSigner( name="David", email_address="david\@cubeflakes.com")request = boldsign.EmbeddedDocumentRequest( title="Service Agreement", signers=\[signer], send_view_option="PreparePage", show_toolbar=True)embedded_send_created =\
  document_api.\
    create_embedded_request_url_document(\
      embedded_document_request=request)send_url = embedded_send_created.send_url

Sample Python 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 Python code from BoldSign’s 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 Python 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 Python SDK, you get all five from your Python code.

- ### Signature capture is the small piece

  A signature widget is a day of work. The record that proves it is not.

- ### The record has to survive scrutiny

  A sealed PDF needs a trusted certificate you buy and renew, with a timestamp on every action.

- ### Upkeep lands on your team

  Reminders, status checks, and document storage stay in your own code after launch.

The solution

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

The BoldSign Python SDK gives your 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 Python code sends the document and signers to BoldSign, which emails each signer a private link.

- ### Embed signing in your product

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

Capabilities

## What can your Python app do with the Python eSignature SDK?

With the BoldSign Python SDK, your Python app handles the whole signing flow. Every completed PDF is digitally signed with an AATL certificate.

- ### Send documents for signature

  Send a contract or form from Python 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 Python app, so the signer never leaves your product.

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

- ### Prepare and send in your app

  Your users place fields and send the document from your own Python screens.

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

- ### Send from templates

  Store a template with its fields once, then send it to new signers from Python.

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

- ### Check who is signing

  Choose a check for each 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 route, then download the signed PDF and audit trail.

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

Works in: server-side Python apps, such as Django, Flask, and FastAPI projects. Keep the SDK on your server, since it carries your API key.

Get started

## How do you integrate signatures into a Python app?

You integrate the BoldSign Python SDK in 3 steps: install, authenticate, and send.

1. ### Install from PyPI

   `pip install boldsign`

   Runs on Python 3.7 or later.

2. ### API authentication

   `configuration = boldsign.Configuration(host="https://api.boldsign.com", api_key="Your-API-Key-Here")with boldsign.ApiClient(configuration) as api_client:`

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

3. ### Send the document

   `document_api = boldsign.DocumentApi(api_client)api_response = document_api.send_document(...)`

   The response 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/).Write a Python function that sends a document for signature with the BoldSign Python SDK.

[See the full Python walkthrough](https://developers.boldsign.com/sdks/python-sdk/)

Why BoldSign

## Why choose BoldSign for Python developers

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

- ### Typed models, not raw JSON

  Every request and response is a Pydantic model. Your editor autocompletes fields and catches typos before you run the code.

- ### Write Python 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

  Test each endpoint in a free sandbox and finish the integration before you pay.

- ### Signers need no account

  People who sign need no BoldSign account and no 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. An independent SOC 2 Type 2 audit covers its security controls. Each standard it meets is listed on your account’s Compliance page, 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 Python with BoldSign

The BoldSign Python SDK is free to install from PyPI. 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 Python

- 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

  ### Flask example

  Add BoldSign signing to a Flask app, with the signing page inside your product.

  [Read the guide](https://boldsign.com/blogs/embed-the-esignature-solution-into-your-python-application.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 Python eSignature SDK

### Is there a Python digital signature SDK?

Yes. The BoldSign Python SDK, published on PyPI as boldsign, is BoldSign’s official SDK for Python. 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 a Flask app?

Yes. The BoldSign Python SDK installs in Flask like any PyPI package. The [Flask guide](https://boldsign.com/blogs/embed-the-esignature-solution-into-your-python-application.md) walks through a full example.

### How do webhooks work with the Python 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 Python app never polls for status. [Set up a webhook](https://developers.boldsign.com/webhooks/setting-webhook/).

### Does the Python 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?

Set your region’s base URL as the host in the SDK configuration, such as api-eu.boldsign.com for Europe. US accounts need no change. [See all base URLs](https://developers.boldsign.com/sdks/python-sdk/).

### Can I test the Python SDK for free?

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

Get started

## Send your first document from Python

Open a free BoldSign API sandbox, install the Python SDK from PyPI, 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
