Skip to Content
FlowVerifyDevelopers

Bulk send

Send the same document to many people, one envelope each, and follow the job.

Bulk send takes a draft with one file and fields assigned to a single signer and creates one envelope per recipient in the background — the same document, personalised per person, each with its own signing link, status and audit trail. All envelopes share a bulk_group_id.

Bulk send needs the Business plan or higher; the per-request cap depends on the plan.

Start a job

Prepare the draft as in the Envelopes guide with exactly one signer (the placeholder whose fields every recipient inherits), then:

curl -X POST https://api.flowverify.co/v1/envelopes/{id}/bulk-send \
  -H "Authorization: Bearer fv_live_xxxxxxxx" \
  -H "Idempotency-Key: policy-ack-2026-q3" \
  -H "Content-Type: application/json" \
  -d '{
    "recipients": [
      { "name": "Asha Rao",  "email": "[email protected]" },
      { "name": "Ravi Kumar", "email": "[email protected]" }
    ],
    "subject": "Please acknowledge the updated policy",
    "message": "Two minutes, one signature."
  }'
{
  "success": true,
  "data": {
    "object": "bulk_send_job",
    "id": "…",
    "bulk_group_id": "…",
    "source_envelope_id": "…",
    "status": "queued",
    "kind": "initial",
    "total_recipients": 2,
    "succeeded": 0,
    "failed": 0,
    "progress_pct": 0,
    "created_at": "…"
  }
}

Duplicate email addresses are dropped. A second bulk send for the same draft while one is running answers 409 state_conflict with details.job_id.

Follow the job

curl https://api.flowverify.co/v1/bulk-send-jobs/{jobId} -H "Authorization: Bearer fv_live_xxxxxxxx"

status moves queued → running → completed | partial_failure | failed | cancelled. When it finishes, the bulk_send.completed webhook fires with the same object. Each created envelope also emits its own envelope.sent and later transitions, so per-recipient tracking works exactly like single envelopes; list them with GET /envelopes?search=<bulk_group_id> or read them from the webhook payloads.

Limits and quota

  • Each recipient consumes one envelope of the monthly quota; the request is refused up front when the remaining quota is smaller than the list (403 plan_limit_exceeded).
  • recipients accepts up to 5,000 entries per request; the plan's BULK_SEND_MAX_RECIPIENTS may be lower.
  • Bulk send draws from the expensive rate-limit bucket.

On this page