In this session, Syncfusion Software Developer Harini Chellappa walked attendees through how to embed BoldSign eSignature workflows directly into your .NET applications. This way, you can allow users to send and sign documents without leaving your app.
If you missed the webinar or would like to watch it again, the recording has been uploaded to our YouTube channel and is embedded below.
Why embed eSignature workflows?
Embedding BoldSign’s eSignature process creates a smoother, more secure experience by keeping users within your application. Everything from preparing the document to completing the signature can happen in-app, reducing friction and improving engagement.
Benefits include:
- Seamless user experience: No external redirects or page changes.
- Consistent branding: Customize the embedded UI to match your company’s look and feel.
- Simplified control: Manage sending, signing, and tracking directly from your application.
Getting started
To integrate BoldSign into your .NET app:
- Install the BoldSign .NET SDK from NuGet.
- Generate an API key from your BoldSign account dashboard.
- Use embedded URLs to launch send and sign pages within your app.
Harini demonstrated this using a sample ASP.NET Core MVC web app, where both HR admins and employees manage documents within the same interface.
Building the embedded workflow
The session covered how to:
- Generate the embedded request URL to send signature requests.
- Use iframes to display embedded pages for sending and signing.
- Configure webhooks to track document updates automatically.
- Handle client-side events like document sent, signed, or declined.
- Customize the toolbar for a branded signing experience.
Live demo highlights
Using a fictional company called CubeFlakes, Harini showcased:
- Sending documents through an embedded request URL.
- Signing documents directly within the application.
- Implementing real-time updates via webhook listeners.
- Using custom toolbars for a consistent user interface.
- Displaying the completed document in a new browser tab.
Displaying the completed document in a new browser tab.
Best practices
- Always validate signer information before generating a signing URL.
- Use DisableEmails = true to ensure signing happens fully within your app.
- Configure a redirect URL after signing for better flow control.
- Utilize localization options for international users.
- Keep API keys secure and stored server-side.
View completed documents
The process concludes by retrieving and displaying signed documents using the document ID—providing a full, end-to-end eSignature flow without leaving your app.
Time stamps
[00:00] Introduction and agenda
[02:31] What are embedded workflows?
[03:47] Benefits of embedding eSignature workflows
[04:15] Live demo: embedded sending workflow
[06:10] How to generate an embedded request URL
[10:52] Setting up properties and disabling emails
[13:47] Handling client-side events and a custom toolbar
[16:07] Creating an embedded signing URL
[18:29] Viewing completed documents
[19:25] Conclusion
Q&A
Are the signed documents legally binding? Does this comply with the eIDAS regulations, the ESIGN act, and UETA?
Yes, signed documents in BoldSign are legally binding and the platform is designed to comply with major electronic signature regulations. Please check out our security page for more information.
Can the BoldSign UI be modified? We are using a paid-for theme in our website, so it should match with a similar type of UI.
Yes, you can customize the button colors and logo to match your UI, and you can embed it in your application.
Conclusion
By embedding BoldSign’s sending and signing workflows, you can provide users a seamless, branded signing experience that enhances trust and efficiency. From onboarding to approvals, embedded workflows streamline document processes and reduce turnaround times.
Related links
🔗 Getting started—API documentation
Send E-Signature Requests from Your App Using the BoldSign Java SDK
