Choosing between send document vs. embedded request in BoldSign

BoldSign offers two distinct API methods to initiate eSignature workflows, each designed for different integration styles and user experiences.

1. Send document – Backend automation

This method is ideal for automated workflows, as it creates and sends documents for signature directly through the BoldSign API without requiring any user interaction.

• Purpose: Automate sending documents via backend processing
• API Endpoint: POST /v1/document/send
• User Experience: No UI interaction
• Use Case:
  • Auto-send loan agreements
  • Bulk onboarding forms
  • Claims or policy documents
• Form Field Configuration:
  • Fields must be defined programmatically
  • Developers specify field type, position, page number, and recipient via code

Here is an example Python script for the send document API

2. Embedded request – In-app user control

This method allows users to create, customize, and send documents from within your app using BoldSign’s embedded UI.

• Purpose: Enable users to prepare and send documents interactively
• API Endpoint: POST /v1/document/createEmbeddedRequestUrl
• User Experience: UI embedded via iframe, popup, or new tab
• Use Case:
  • HR platforms
  • Real estate or legal apps
  • SaaS tools with user-facing workflows
• Form Field Configuration:
  • Users can drag and drop form fields like signature boxes, text inputs, and checkboxes
  • No coding required—fields are placed visually within the embedded interface.

The screenshot below shows document creation embedded within an iFrame.

Summary table: Key differences

Which should you choose?

• Choose Send Document for speed, scale, and backend automation.
• Choose Embedded Request for user control, customization and interactive workflows.