BoldSign Blogs

  In this webinar, Gayathri Annamalai, Software Developer at BoldSign, demonstrates how BoldSign AI Search helps you find what you need in seconds using conversational search. Instead of relying on multiple manual filters, you can type a request that includes details such as status, signer, owner, or date, and AI Search returns relevant results quickly. If you missed the webinar or would like to watch it again, the recording is available on our YouTube channel and is embedded. Webinar recap The webinar opened with a look at common challenges users face when searching with traditional filter-based methods, especially when multiple conditions are needed or when users do not remember where a document is stored. Gayathri then introduced BoldSign AI Search and shared practical examples showing how it interprets intent, combines conditions automatically, and returns accurate results across your BoldSign account. The session also covered how you can refine or broaden results by adjusting...

Controller-based APIs (ASP.NET Core Web API with [ApiController]) are the strongest default for large, long-lived APIs because they ship with conventions, discoverability, and mature MVC extension points for enforcing cross-cutting policies consistently.  Minimal APIs are a great fit for smaller or focused services (microservices/internal APIs) when you want an endpoint-first model and you’re willing to enforce structure intentionally with route groups, conventions, endpoint filters, and feature modules.  In most real workloads, this choice impacts maintainability and team consistency more than raw performance (see Microsoft’s controller-based Web API guidance at “Create web APIs with ASP.NET Core” on  Microsoft Learn  and  Minimal APIs ).  What’s the difference between controllers and Minimal APIs in .NET 8? What are controllers in .NET 8 Web API terms? Controllers map routes to controller action methods inside ...

  Collecting accurate input from multiple signers becomes challenging when the same terms must be agreed upon by more than one party. In API-driven eSignature workflows, this often leads to duplicated fields, manual reconciliation, or custom validation logic, adding complexity and increasing the risk of errors. Collaborative fields in BoldSign, available through the API, solve this. They make it easier to collect agreed-upon values for budgets, addresses, comments, or project details in multiparty signing workflows. What are collaborative fields in BoldSign and how do they work via API Collaborative fields in BoldSign allow multiple signers to edit the same form field during a signing workflow. Instead of each signer only completing their assigned fields, collaborative fields let authorized participants change shared information before a document is fully executed. When used through the API, collaborative fields are configured within the field definition using the collaborationSett...