What are the benefits of the Embedded Send API over the Send Document API?
BoldSign provides multiple API endpoints to initiate eSignature workflows. The Send Document API is designed for backend automation where a document is sent immediately after the request. The Embedded Send API takes a draft-first approach—creating a draft and returning an embedded URL so you can review and finalize everything before sending.
API endpoints
| API | What it does | Endpoint |
|---|---|---|
| Send Document API | Sends immediately after request | POST /v1/document/send |
| Embedded Send API | Creates a draft and returns an embedded URL to finish setup, then send | POST /v1/document/createEmbeddedRequestUrl |
Why Embedded Send is beneficial
| Area | Embedded Send API (Benefit) | Send Document API |
|---|---|---|
| Send behavior | Creates a draft (nothing is sent until you click Send) | Sends immediately |
| Review before sending | Built-in review + preview in draft | No pre-send review step |
| Recipient management | Add/remove/edit recipients while draft is open | Recipients typically set at send time; changes require additional update calls |
| CC recipients | Edit CC in draft | Set at send time; updates require extra call |
| Private message | Edit private message in draft | Set at send time; updates require extra call |
| Authentication & delivery | Adjust delivery/authentication before send (email/SMS/access code, etc.) | Set at send time; updates require extra call |
| Signer language | Change in draft | Set at send time; updates require extra call |
| Signer type/role | Change in draft | Set at send time; updates require extra call |
| Title/message/tags | Editable until final send | Set at send time; updates require extra call |
| Reminders & expiration | Tune in draft | Set at send time; updates require extra call |
| Files | Add/remove/replace files in draft | Files are sent immediately; changes require extra call |
| Form fields | Visual field editing + save/reopen (multi-session) | Often requires programmatic field setup; large forms can be time-consuming |
| Save & continue later | Save & close draft; reopen anytime | Not available—request sends immediately |
| Schedule send | Set/modify schedule before sending | Can schedule at send time; changes require extra call |
Benefits of the Embedded Send API
1) Draft-first workflow (most important benefit)
Embedded Send creates a draft instead of sending immediately, so you can validate everything before recipients ever receive an email/link.
Result: fewer mistakes and less rework.
2) Easier recipient and CC control before sending
You can update recipients/CC while the draft is open.
Result: no need to restart the workflow if someone changes.
3) Security and delivery settings can be finalized at the right time
Authentication and delivery preferences can be adjusted during the draft stage.
Result: you can confirm security requirements before the document goes out.
4) Better handling of complex forms
Draft mode supports step-by-step field configuration, saving, reopening, and continuing later.
Result: faster and safer form preparation—especially for documents with many fields.
5) Save, preview, and proceed (staged preparation)
Drafts can be previewed, saved, closed, and reopened for further edits before sending.
Result: supports collaboration and reduces “sent too early” scenarios.
6) Flexible timing controls
Reminder/expiration settings and schedule send can be adjusted while the draft is open.
Result: delivery timing stays aligned with real-world workflows.
When should I use the Embedded Send API?
Use Embedded Send API when you need:
-
A review/approval step before sending
-
End users to visually prepare documents (fields, recipients, settings)
-
Save and resume preparation later
-
Complex or high-volume form fields that are easier to build incrementally
-
Scheduling that may change until the final moment
Summary
If your workflow benefits from control before sending, choose the Embedded Send API. It enables a draft-based experience where you can refine recipients, files, settings, fields, and scheduling before the document is delivered—making it easier to avoid errors and support collaborative preparation.
