Embedded signing that keeps users in your app
BoldSign’s Embedded Signing feature puts the signing page inside your own application. Your users finish the agreement on the screen where they started.
- API sandbox with no credit card
- Signing events posted back to your code
Trusted by 100,000+ organizations worldwide
Sending your users somewhere else to sign breaks the flow
The moment a signature request leaves your product, the job stops being yours. Your user waits for an email and opens a page in someone else’s brand. They come back only if nothing goes wrong.
How do your signers sign inside your app?
With BoldSign, your signer opens the document inside your app, signs, and carries on. The signing page loads in an iframe, popup window, or new tab.
-
No account, no password
Your signer opens the document from your app and signs there. No BoldSign account is needed.
-
Your brand on the signing page
Your logo, your colors, and your own signer disclaimer show on the embedded signing page.
-
No BoldSign email in the way
Switch off BoldSign’s own emails for a request. Send your own emails instead, triggered by webhooks.
-
You pick the page after signing
You decide where your signer goes once they sign, such as a confirmation page in your app.
-
Decline and reassign, if you allow it
Signers can decline the request or hand it to someone else. Hide either button in your brand settings when your flow has no use for it.
Why choose BoldSign for embedded signing
BoldSign suits product teams who want signing inside their own software. You skip building and maintaining your own signing page.
-
Uptime you can check yourself
BoldSign’s SLA commits to 99.99% uptime each calendar month. Measured uptime runs at 99.999%, which you can verify on status.boldsign.com.
-
Support at no extra cost
Chat, email, and ticket support come with your account. You never buy a separate support tier.
-
Signers are not seats
A signer who completes a document adds no user to your account.
Who builds this eSignature API and its SDKs?
BoldSign is built by Syncfusion, which has made developer components for 25+ years. Your eSignature API comes from a team that builds tools for developers every day.
- 25+ years building developer tools Syncfusion started in 2001.
- 1 million+ active developers
- 1,600+ components For web, mobile, and desktop apps.
How are your documents kept secure and legally valid?
Signatures you collect with BoldSign are legally binding under the ESIGN Act, UETA, and eIDAS. Every document is encrypted twice with AES-256.
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.
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.
HIPAA Compliance
EnabledEnable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.
PCI DSS
CompliantPayments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.
CCPA & CPRA
CompliantEnsures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.
SOC 2 Type II
CompliantBoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.
UETA & ESIGN
CompliantBoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).
eIDAS (SES)
CompliantBoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.
eIDAS (QES)
EnabledEnable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.
Limits and costs to know before you add embedded signing with BoldSign
BoldSign’s embedded signing comes with these costs and product limits. Prices are in USD.
- $30 Enterprise API plan, per month Includes 40 envelopes a month.
- $0.75 per extra envelope After the 40 included each month.
- 2,000 API requests an hour Per account in production.
Can your users prepare and send documents from your app too?
Yes. BoldSign also embeds the prepare page. Your users upload a file, place fields on it, and send without opening BoldSign.
| Embedded link | What it puts in your app | Who uses it |
|---|---|---|
| Embedded signing | The signing page for one named signer | Your customer or their counterparty |
| Embedded sending | The prepare page, with drag and drop fields | Your own user, sending an agreement |
Each one is a link your server requests and your own page loads. The embedded sending guide covers the prepare page.
How do you add embedded signing to your application?
With BoldSign, you create the document, request the signer’s link, and load it in your page. Your code then listens for the result.
Which languages do the eSignature SDKs support?
BoldSign has official eSignature SDKs for C#, Node.js, Python, Java, and PHP. Each one wraps the REST API, including embedded signing, and its source code is on GitHub.
What do you get for an end-to-end eSignature integration?
With BoldSign, you get every piece from document prep to go-live. Each part works out of the box through one REST API and its SDKs.
- Prepare
Fields placed for you
Put text tags such as
Read about text tags{{sign|1|*}}in your file, or let BoldSign detect fillable PDF form fields. Either way, your code skips field coordinates. - Embed
Plug and play signing UI
The signing and sending pages drop into an iframe, ready out of the box.
Try the live demos - Track
Webhooks your server can trust
Subscribe to events such as Sent, Viewed, Signed, Completed, and Declined. Each delivery is signed with
Verify webhook eventsHMAC SHA-256, so your server can verify it. - Store
Signed copies back in your system
Download the signed document and its audit trail through the API. File both next to the original record in your own system.
- Secure
API key or OAuth 2.0
Send an API key in the
Read about authenticationX-API-KEYheader, or use anOAuth 2.0bearer token. Scopes limit each app to the access it needs. - Ship
Sandbox to live with one key
Build on a free sandbox key and try calls with ready-made Postman requests. Sandbox documents are watermarked and deleted after 14 days. To go live, swap in a live key.
Compare sandbox and live keys
Questions about embedded signatures
What is an embedded signature?
An embedded signature is signed on a page shown inside another application. The signer never leaves that app to sign. The term sometimes means the digital certificate stored inside a signed PDF. BoldSign covers both: you get an embedded signing link, and every completed document is also digitally signed.
How is embedded signing different from emailing a signing link?
An emailed request, the kind sent by tools for sending SaaS contracts for signature, takes the signer from their inbox to the BoldSign signing page in a separate tab. An embedded request shows that same page inside your app, so the signer stays on your screen. The BoldSign API supports both ways.
Do signers need a BoldSign account to sign inside my app?
No. A signer opens the embedded signing link from your application and signs there. They create no BoldSign account and pay nothing.
How much does an embedded eSignature API cost?
BoldSign charges $0.75 per envelope on the Enterprise API plan. That plan starts at $30 a month and includes 40 envelopes. The API pricing page lists every tier.
Can I test embedded signing before I pay?
Yes. The BoldSign API sandbox is free and needs no credit card. Create documents, generate embedded signing links, and load them in your own page while you build. Start from the getting started guide in the developer documentation.
Does embedded signing work on mobile?
Yes. The BoldSign signing page is responsive. It renders inside a mobile web view, a mobile browser, or an iframe on desktop.
Can my app send documents on behalf of its users?
Yes. With BoldSign’s sender identities, your app sends signature requests on behalf of another user. That user approves it first, as the sender identity guide explains.
Can AI coding assistants work with BoldSign?
Yes. The BoldSign MCP server connects AI assistants to your account. In plain language, they send documents from templates, check status, send reminders, and revoke documents.
Is a document signed through an embedded link legally binding?
Yes. A document signed through an embedded link has the same legal standing as one signed from an email. Both carry the same audit trail. See eSignature legality by country.
Put signing where your users already are
Build against the free BoldSign sandbox today, then switch the key when you go live.
- 30-day free trial
- No credit card required
Last updated: October 19, 2026