The intended use for the Bulk Sending feature is sending a large number of documents from templates. Document templates are a well-known component in eversign. However, sometimes we want to use one template to generate many documents simultaneously (the Bulk of documents).
We have already implemented the Bulk-sending in eversign UI and documented virtual endpoints in eversign API.
Bulk Sending Process
The Bulk Sending can be implemented with these steps:
The first step is to call Get Bulk Sending Blank CSV endpoint will generate CSV template from a specific template. This step is vital because different templates might have various CSV structures. Also, if a particular template is updated, the CSV structure probably changes.
Once a user generates a blank CSV template, the next step is to populate this CSV file with data. This data describes Bulk sending documents we want to create from our template.
The next step is to validate if CSV content is correct. For this, we exposed an endpoint to validate Bulk sending CSV. Common validations check if all required fields are present and if data is in the correct format (i.e., email has proper structure).
In the case of failing validation, API will provide a detailed response with validation issues. Once we resolve all validation issues, we can create a Bulk Job.
The endpoint that creates a Bulk Job will trigger the validation process in the background to be extra safe. This way, if integration does not implement the validation step, API will ensure that validation will occur nevertheless.
The final step is to create a Bulk Job with the provided endpoint.
Fetching Bulk Job data/status
Users can perform following actions to check upon the existing Bulk Job(s) data:
Bulk sending has the potential to enrich the user experience of your integration significantly.
Before implementing it, you should be aware of these constraints.