Structuring a Bulk Signing Workflow

Bulk signing in Hoicko is achieved by pairing a pre-configured, template-ready signature profile with its TOKEN and cURL command, then triggering that same API call programmatically for every document in a batch — rather than manually clicking "Sign Document" one at a time.

Why API-Driven Bulk Sending Beats Manual Sending

Manually opening each document and clicking Sign Document does not scale past a handful of files. Every Hoicko signature profile dashboard exposes a TOKEN and a COPY CURL button specifically so bulk and automated workflows can call the signing action directly from external systems — a CRM workflow engine, an HRMS onboarding pipeline, or a custom script.

Step-by-Step: Setting Up Bulk Sending

1. Choose or create the right template profile for the document type you're bulk-processing (see Section 3.1 for template setup).
2. Copy the profile's TOKEN and the ready-made command via COPY CURL.
3. Integrate the cURL call into your batch process — a script, scheduled job, or workflow automation tool that loops through your document list.
4. Stagger large batches if your volume is very high, to avoid overwhelming downstream systems and to make failure isolation easier.
5. Monitor the This Month / Success / Failed stat cards immediately after a batch run to catch systemic issues (like a bad Pdf Text trigger) before they affect the entire batch.
6. Review the Analytic table to confirm each document in the batch was processed with a SUCCESS status.

Common Bulk Sending Use Cases

• HR onboarding: offer letters and policy acknowledgments signed automatically as part of an HRMS workflow (note "HOICKO LMS" as a "Created By" source in real signature profiles, showing this integration pattern already in use).
• Dealer/vendor agreements: contracts pushed through CRM/Dealer module workflows at scale.
• Compliance re-certifications: recurring documents signed on a schedule without manual intervention.

Frequently Asked Questions

Q: Does bulk sending require a developer to set up the API integration? A: Typically yes for the initial cURL/API integration, though your workflow automation tools may support the calls without custom coding depending on your platform.

Q: What happens if one document in a bulk batch fails? A: Only that specific document's signing attempt fails and is logged as FAILED in the Analytic table — other documents in the batch are unaffected, since each is a discrete API call.

Q: Can different documents in the same batch use different signature profiles? A: Yes — since each API call references a specific profile's TOKEN, you can route different document types to their matching templates within the same overall batch job.