Published on
It’s a sunny day, and you decide to take a hike. It’s a scenic route, far from the city, where your thumb could obscure the skyscrapers on the horizon. Your mind is gushing with gratitude and excitement about the game-changing housing business you have built, along with a rental app designed for students. A solution that will help thousands of students find affordable rental accommodation easily and quickly. You breathe in the fresh air with pride with an imaginary pat on your back — just thinking about the impact it will create.
Your product, much like your business, is modern and innovative. The digitized onboarding makes it easy for students to log in to your app, explore apartments from your multiple listings, and choose one they love. To seal the deal, they only have to electronically sign the lease agreement within your app powered by Signeasy API. That’s it!
But then, out of nowhere, a sudden thought intrudes this perfect moment and brings your chin down. To finish onboarding these happy tenants, the property owner i.e. you, also must legally countersign hundreds of contracts in the queue. January is around the corner, and you don’t want to keep these students in a state of worry or wish to sign documents one by one.
Table of Contents
What if you can sign multiple lease agreements using a simple click-and-accept flow? Signeasy’s Bulk Sign feature is designed for this use case exclusively, where a signer would only need to group a bunch of pending documents waiting on them and sign them in one go.
If you’re already using Signeasy to provide an eSigning experience within your platform, all you need to do is:
Fret not, we’ll show you exactly how to do that.
Bulk Sign’s use case demands the envelope signature requests to be sequential with the counter-signing recipient the same for all the documents. Use the create or send envelope endpoint with your API access token and an original file to create two or more signing requests with the same counter-signing recipient.
For convenience, you can import the Signeasy API v3.0 Postman collection and navigate to the Envelopes folder and use the Create or send an envelope endpoint with the following payload.
{
"recipients": [
{
"first_name": "Mario",
"last_name": "A",
"email": "[email protected]",
"recipient_id": 1
},
{
"first_name": "Luigi",
"last_name": "B",
"email": "[email protected]",
"recipient_id": 2
}
],
"sources": [
{
"id": 59925063,
"type": "original",
"name": "agreement",
"source_id": 1
}
],
"is_ordered": true,
"message": "This is a test request.",
"embedded_signing": false,
"aadhaar_enabled": 0,
"fields_payload": [
{
"recipient_id": 1,
"source_id": 1,
"type": "signature",
"required": true,
"page_number": 1,
"position": {
"x": 60,
"y": 520,
"height": 50,
"width": 250,
"mode": "fixed"
},
"additional_info": {
"format": "string"
}
},
{
"recipient_id": 2,
"source_id": 1,
"type": "signature",
"required": true,
"page_number": 1,
"position": {
"x": 320,
"y": 520,
"height": 50,
"width": 250,
"mode": "fixed"
},
"additional_info": {
"format": "string"
}
}
]
}
{
"id": 5050860
}
Create two more envelopes.
5050874, 5051530
Bulk Signing requires all the parties to have signed except the one who is about to counter-sign the document. So ensure all the previous parties in the queue have finished signing the documents.
Once it is the counter-signing party’s turn to sign in all three envelopes, Initiate a POST request to the Create Bulk Signing request endpoint with the following payload.
POST → https://api.signeasy.com/v3/rs/bulk/sign/
Request Payload
{
"signer_email": "[email protected]",
"pending_file_id": [
5050860,
5050874,
5051530
],
"display_info": {
"title": "Here goes the title",
"text": "Additional information for the signers"
},
"redirect_url": "https://signeasy.com/api"
}
Response
{
"url": "https://app.signeasy.com/bulk-sign/?hash=07f9e5afc4e749afa533cb7a258c34feb0aea1804e2841b78df2b8fdd1aa8d3e&data=eyJyZXF1ZXN0X2lkIjogMzYyLCAiZGlzcGxheV9pbmZvIsdfgeyJ0aXRsZSI6ICJIZXJlIGdvZXMgdGhlIHRpdGxlIiwgInRleHQiOiAiQWRkaXRpb25hbCBpbmZvcm1hdGlvbiBmb3IgdGhlIHNpZ25lcnMifX0=&version=2.1&next=https%3A//signeasy.com/api",
"request_id": 363
}
The `request_id` in the response can further used to check the status of the bulk sign request once the counter-signing party initiates their bulk sign process in the next step. Since bulk signing is done as an asynchronous batch process, it’s handy to check the request’s status. Or, you can rely on the webhook events associated with the bulk sign statuses.
Navigate to the URL you received in the response in the previous step. You’ll be presented with a bulk signing interface. Go ahead and sign the document.
You’ll only have to sign once to complete the signature on all three documents waiting on you.
If the bulk signing action gets declined or completed, a webhook event could be fired if you’ve subscribed to the events. You can also check the status of the Bulk Sign request by initiating a GET request to the Fetch bulk signing status with the `request_id` you received in step 3.
GET → https://api.signeasy.com/v3/rs/bulk/sign/{request_id}/track/
Response
{
"status": "completed",
"documents": [
{
"id": 5050860,
"status": "completed"
},
{
"id": 5050874,
"status": "completed"
},
{
"id": 5051530,
"status": "completed"
}
]
}
With Bulk Sign, you save time and also significantly improve the end-user experience while achieving lightning fast contract turn around times.
Bulk Signing is now available for all our v3.0 customers who are on the API Advanced Plan. Please take a look at our documentation to start exploring. If you have questions about integrating Bulk signing into your existing workflows, you can always reach us at [email protected]. We’d be happy to help you.