Choosing between create template vs. embedded template in BoldSign

In BoldSign, both Create template and Embedded template are used to build reusable eSignature templates but they have some key differences and use cases:

1. Create template – Backend automation

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

• Purpose: Automate template creation via backend processing
• API Endpoint: POST /v1/template/create
• User Experience: No UI interaction
• Use Case:
  • Auto-create loan agreements
  • 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 create template API

2. Embedded template – In-app user control

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

• Purpose: Enable users to create templates interactively
• API Endpoint: POST /v1/template/createEmbeddedTemplateUrl
• 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 template creation embedded within an iFrame.

Summary table: Key differences

Which should you choose?

• Choose Create template for speed, scale, and backend automation.
• Choose Embedded template for user control, customization and interactive workflows.