Skip to content
Java SDK

eSignature SDK for Java applications

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

Create free API sandboxBook a walkthrough
  • Install from Maven or Gradle
  • API key or OAuth 2.0
  • Webhooks for every status change
Your CompanyPreviewSend
Assignee
David
SERVICE AGREEMENT
Company signatureSign here*
Client signatureSign here*
Agreements.javaJava SDK
DocumentApi documentApi = new DocumentApi(client);DocumentSigner signer = new DocumentSigner();signer.setName("David");signer.setEmailAddress("david@cubeflakes.com");EmbeddedDocumentRequest request = new EmbeddedDocumentRequest();request.setTitle("Service Agreement");request.setSigners(Arrays.asList(signer));request.setSendViewOption(
  EmbeddedDocumentRequest
    .SendViewOptionEnum.PREPARE_PAGE);request.setShowToolbar(true);EmbeddedSendCreated embeddedSendCreated =  documentApi.
    createEmbeddedRequestUrlDocument(request);String sendUrl = embeddedSendCreated.sendUrl;
Sample Java 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 Java code from BoldSign’s docs that creates this embedded request

Trusted by 100,000+ organizations worldwide

Samsonite
Ryanair
Hyatt
Sony
Crumbl Cookies
Payroc
Cost Plus
The problem

Why is adding eSignatures to a Java 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 Java SDK, you get all five from your Java code.

  • Capture is the small part

    Drawing a signature on a canvas is a short job. Proving who signed, and when, is not.

  • The PDF has to be sealed

    Sealing needs a trusted certificate that you buy and renew, plus a timestamp on every action.

  • Maintenance never ends

    Reminders, status polling, and document storage stay with your team long after launch.

The solution

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

The BoldSign Java 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 Java code hands the document and signers to BoldSign, which emails each signer a private link.

  • Embed signing in your product

    BoldSign returns a signing URL your app can frame. The signer signs the document inside your app, without leaving it.

Capabilities

What can your Java app do with the Java eSignature SDK?

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

  • Send documents for signature

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

    See the eSignature API

  • Sign inside your app

    Render the signing page in your own Java pages, so the signer never leaves your product.

    See embedded signing

  • Prepare and send in your app

    Your users place fields on the PDF and send it without leaving your Java app.

    See embedded sending

  • Send from templates

    Keep a reusable template on file, then send it to new signers from Java.

    See templates

  • Check who is signing

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

    See signer authentication

  • Know when it is signed

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

    See webhooks

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

Get started

How do you implement electronic signatures in Java?

You implement BoldSign eSignatures in Java in 3 steps: install the SDK, authenticate, and send.

  1. Install from Maven or Gradle

    implementation "com.boldsign:boldsign-java:7.0.2"

    Gradle shown; Maven adds the same artifact to pom.xml. Check Maven Central for the current version. Runs on Java 8 or later.

  2. API authentication

    ApiClient client = Configuration.getDefaultApiClient();client.setBasePath("https://api.boldsign.com");client.setApiKey("Your-API-Key-Here");

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

  3. Send the document

    DocumentCreated document = documentApi.sendDocument(...);

    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.Write a Java method that sends a document for signature with the BoldSign Java SDK.

See the full Java walkthrough
Why BoldSign

Why choose BoldSign for Java developers

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

  • Generated model classes

    Every request and response is a typed Java class from the SDK. The compiler catches a wrong field before you run the code.

  • Write Java code with your AI coding tool

    BoldSign’s coding assistant (MCP) 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

    Work through every endpoint in a free sandbox before you pay anything.

  • Signers need no account

    No BoldSign account and no download for the people who sign.

  • Legally binding signatures

    Signatures you collect with BoldSign are legally binding 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 audit covers its security controls for SOC 2 Type 2. The Compliance page in your account lists each standard it meets, shown below.

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

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
HIPAA logo

HIPAA Compliance

Enabled

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

View Details
PCI DSS logo

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
CCPA logo

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
AICPA SOC logo

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
US flag

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
EU flag

eIDAS (SES)

Compliant

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

View SES Policy
EU flag

eIDAS (QES)

Enabled

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

View QES Policy
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, data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.

What it costs

Limits and costs to know before you send from Java with BoldSign

The BoldSign Java SDK is free to install from Maven Central. 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
Good to know
  • 2,000 API requests an hour per account The sandbox allows 50 an hour.
Related

More guides for building eSignatures in Java

  • Page

    All eSignature SDKs

    Compare the five official BoldSign SDKs.

    See all SDKs
  • Page

    Embedded signing

    Open the signing page inside your own app.

    See embedded signing
  • Code samples

    Java and Angular example

    See an Angular front end call the BoldSign Java SDK to send and sign a document.

    View samples on GitHub
  • Guide

    Build an AI agent

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

    Read the guide
Common questions

Questions about the Java eSignature SDK

Is there a Java digital signature SDK?

Yes. The BoldSign Java SDK, published on Maven Central as com.boldsign:boldsign-java, is BoldSign’s official SDK for Java. People sign electronically, and BoldSign seals each completed PDF with an AATL certificate.

How do webhooks work with the Java 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 Java app never polls for status. Set up a webhook.

Does the Java SDK support OAuth 2.0?

Yes. Pass a bearer token with setAccessToken instead of an API key. See OAuth 2.0 setup.

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

Pass your region’s base URL to setBasePath, such as api-eu.boldsign.com for Europe. US accounts need no change. See all base URLs.

Can I test the Java SDK for free?

Yes. Create a free BoldSign API sandbox, then use its API key with the Java SDK. Sandbox documents are for testing only.

Get started

Send your first document from Java

Open a free BoldSign API sandbox, install the Java SDK from Maven Central, and send your first document.

Create free API sandboxBook a walkthrough
  • 30-day free trial
  • No credit card required

Last updated: October 18, 2026