BoldSign Blogs

  We’re excited to share the new HubSpot + BoldSign integration. This integration brings easy, secure document signing right into your HubSpot CRM. No more switching between apps—send, track, and manage signed documents in one place. This helps your team: Save time on preparing and sending documents. Reduce manual data entry and errors. Keep your sales and customer workflows in HubSpot. Here’s what you can do with the integration and how to get started. What you can do with the HubSpot + BoldSign integration 1. Quick setup Connect HubSpot and BoldSign in just a few clicks. You don’t need technical skills to get started, and your signing workflows stay connected to your existing HubSpot data. Connect BoldSign 2. Reusable templates with mapped fields Create templates in BoldSign and map them to HubSpot fields. When you send a document, contact details like names, emails, and other key fields fill in automatically—no retyping needed. Create Template 3. Pre-filled documents from HubSpo...

  Ensuring documents are signed on time is essential. Setting an expiration date adds a layer of security to the document, ensuring it is only valid for a specified period. You can configure an expiration date for your document through the BoldSign API by specifying the expiration value with the expiration date type. Once the expiration date is reached, the document will no longer be available for signing. Code snippets Let’s see how to add expiration date via the BoldSign API in various programming languages. curl -X 'POST' \ 'https://api.boldsign.com/v1/document/send' \ -H 'accept: application/json' \ -H 'X-API-KEY: {your API key}' \ -H 'Content-Type: multipart/form-data' \ -F 'Message={document message}' \ -F 'Signers={ "name": "alexgayle", "emailAddress": "alexgayle@boldsign.dev", "signerType": "Signer", "formFields": [ ...

  Queues offload slow, noncritical work into background processes, so your API can respond quickly while heavy tasks run asynchronously. This is useful when endpoints remain slow or fragile even after typical optimizations like indexing, caching, and connection pooling.  By introducing asynchronous processing with queues, you can:  Reduce API response times.  Prevent cascading failures.  Scale background workloads independently.  Improve the user experience without a full system rewrite.  Who should use asynchronous queues in APIs?  This pattern is best suited for:  Backend engineers maintaining slow or brittle endpoints.  System architects designing scalable REST or gRPC services.  API owners handling unpredictable or third-party-dependent workloads.  If your API performs tasks like file processing, email sending, report generation, or external in...

  When preparing documents for electronic signatures, knowing the exact coordinates (X and Y values) for placing form fields can be challenging. Traditional methods often require manual calculations, which are time-consuming and prone to errors. A more systematic and efficient approach involves using text tags within the document. In this blog post, we’ll explore using BoldSign text tags via the API to dynamically position form fields in eSignature requests. Using Text Tags with BoldSign Document Preparation:  While generating the document, you insert specific text tags where you want form fields to appear. The details of this syntax will be explained in the next paragraph. Tag Recognition and Replacement:  Once the document is uploaded into BoldSign, the system scans the document for these text tags. It then automatically replaces each tag with the corresponding form field. This ensures that the form fields are precisely placed where the tags were located in the docum...

  Single sign-on (SSO) simplifies access to multiple applications by allowing users to use a single set of credentials instead of logging in separately to each application. This is not only wonderfully convenient but also enhances security by reducing the number of passwords users need to remember and providing a centralized control point for administrators. What is Auth0? Auth0 is an authentication and authorization platform for SaaS applications and services. It provides various features, including SSO, multifactor authentication (MFA), and social login, to help developers secure their applications. With Auth0, developers can easily add authentication to their applications without worrying about underlying security details. How does Auth0 SSO work? Auth0 uses its Universal Login toolkit to define the login flow, a key feature of an authorization server. Every time a user attempts to log in to an application using Auth0, the application redirects to Universal Login, and Auth0 gua...

  If you are integrating the BoldSign API into your application, you need reliable, real-time visibility into what your documents are doing: Did someone sign the document? Was it declined? Is it ready for the next workflow step? Without reliable updates, teams end up hacking around the problem with manual checks, API polling, or delayed notifications. That means slower workflows and a higher chance of missing critical events. BoldSign Webhooks fix this by pushing events to your application as they happen. But there’s a key architectural decision you need to make before turning them on:  Should you use App-Level Webhooks or Account-Level Webhooks? Short answer:  Use App-Level Webhooks when you need tenant or integration isolation for multitenant SaaS, per-client routing, and separate staging and production environments.  Use Account-Level Webhooks when you want one simple webhook endpoint ...