TL;DR: Choose the BoldSign web app when your team wants to upload, send and track documents itself, with no code. Choose the BoldSign API when you want signing inside your own app or website, run by your software. Many teams use both.
Your sales team sends a few contracts each week. Meanwhile, your product team wants customers to sign their terms without leaving your app. Both need electronic signatures, but they need them in different ways.
We offer two ways to work: a web application and an API. This guide explains what each one does, who it suits and what each plan costs.

What is the difference between the BoldSign web app and the API?
The web app is a website where people send and track documents by hand. The API is a set of tools developers use to build signing into their own software.
Think of a coffee machine in the office kitchen. Anyone can walk up and press a button, and that is the web app. The API is more like the pipes and parts a café uses to build coffee into its own counter.
Who should use the BoldSign web app?
The web app suits teams that want to start sending documents today, without technical help. You sign in, upload a file, add fields and send it.
It fits these cases well:
- Teams that send contracts, offer letters or forms by hand.
- Businesses that want a simple way to sign without building a custom integration.
- Teams that need to start quickly without asking IT or developers for time.
You can sign in to the BoldSign web app from any browser.
What can you do in the BoldSign web app?
The web app covers the full cycle of a signature request. You upload a document, add signature fields, send it and track who has signed.
- Send one document to many signers at once with bulk send, each with their own copy.
- Share one signing link with a group using bulk links, handy for event waivers.
- Add, edit and delete recipients and change document properties with Edit document.
- Get automatic and manual reminders and an audit trail for every document.
With bulk links, each person who opens the link enters their name and email, then signs their own copy. You do not need their names in advance.
Who should use the BoldSign API?
The API suits companies that want signing to happen inside their own app, portal or website. It needs a developer to set up and maintain.
It fits these cases well:
- Software companies that want customers to sign inside their product.
- Businesses that need a signing workflow built around their own steps.
- Teams that want documents sent by their systems, with no one clicking Send.
- Companies that send a large number of signature requests from their own software.
Our BoldSign API page shows sample code and lists software development kits (SDKs) for Python, Java, Node.js and other languages.
What can you build with the BoldSign API?
You can build sending, signing and tracking into your own software. Here are the main building blocks.
Embedded sending and signing
Your users prepare and sign documents inside your app, in a frame on your own page. Our guide to embedded signing for in-app contract signing walks through an example.
Text tags
Placing fields by page position is hard when a document changes from one customer to the next. Text tags solve that: you type short tags such as {{sign|1|*}} into the document.
BoldSign turns each tag into a real field when you send. The tag text stays in the file, so most people set it to white on a white background. See how to add document fields using text tags.
Sending on behalf of others
A software company can send documents in the name of its own customers. You add each customer as a sender identity, and they approve it before you can send for them.
Our guide to sending documents on behalf of others using APIs covers the steps. Multitenant software as a service (SaaS) products use this often.
Webhooks and automation
Webhooks tell your system the moment a document is signed or completed. Your app can then act on that status instead of checking again and again.
Read why webhooks matter in an API integration for the details. For automation without code, you can connect BoldSign to other apps through Zapier.
How do you choose between the web app and the API?
Start with who will send the documents: a person or your software. These four questions settle most choices.
- How many documents do you send? The web app handles everyday volumes. Large volumes sent by your software suit the API.
- Should signing happen inside your own app? Choose the API. Choose the web app when signing in BoldSign is fine.
- How closely should the workflow follow your own steps? The API lets you shape every step. The web app’s standard flow covers most needs.
- Do you have developers to build and maintain an integration? The API needs them. The web app needs none.
Still unsure? Our support team can help you weigh it up and can help developers with an integration. Ask through the support portal.
Which BoldSign plan do you need, and what does it cost?
The web app and the API have separate plans. All figures below come from the BoldSign pricing page in November 2026, and prices are in USD.
Web app plans are billed yearly. Essential costs nothing, Growth is $5 per user a month and Business is $15 per user a month. Premium costs $99 a month for unlimited users.
Bulk send and bulk links start on the Business plan and are also on the Premium plan.
The Enterprise API plan starts at $30 a month and includes 40 envelopes, with $0.75 per extra envelope. It includes two users, and it is the plan for live API access. Embedded signing, text tags, sending on behalf, webhooks and Zapier are part of it.
You can test the API for free in a sandbox, with no credit card needed. The web app plans come with a 30-day free trial.
Which way will you start with BoldSign?
Pick the path that matches who will send your documents. Each one lets you try it before you pay.
- Start a 30-day free trial of the web app and send your first document.
- Create a free API sandbox account and test your integration.
- Book a demo to see both the web app and the API with your own documents.
Frequently asked questions
What is the difference between the BoldSign web app and the BoldSign API?
The web app is a ready-made site where you upload, send and track documents yourself. The API lets developers add signing to their own software, so users never leave it.
Do I need a developer to use BoldSign?
You need one only for the API. Anyone on your team can send and track documents in the web app without writing code.
Can I use the BoldSign web app and the API together?
Yes. Many teams send everyday documents from the web app and use the API for signing inside their own product. Each one is billed under its own plan.
How much does the BoldSign API cost?
The Enterprise API plan starts at $30 a month with 40 envelopes, and each extra envelope costs $0.75, as of November 2026. Testing in the sandbox is free.
Is there a free way to try the BoldSign API?
Yes. A free sandbox account gives you full API access for testing, with no credit card needed. Sandbox documents carry a test watermark and are deleted after 14 days.
Do signers need a BoldSign account to sign?
No. Signers open the document from their email or from the link you share, and sign without creating an account.
Are documents signed through the BoldSign API legally binding?
Yes, when they meet the same rules as any electronic signature, such as the signer agreeing to sign electronically. Each document gets an audit trail, whether you send it from the web app or the API.
Which BoldSign plan includes Zapier?
Zapier is part of the Enterprise API plan, as listed on our pricing page in November 2026. The web app plans list it as not included.