FlowVerify REST API
Document signing, built into your product
Create and send envelopes, reuse templates, track status and receive signed webhooks from your own systems. Recipients sign in the FlowVerify signer app, so every signature keeps its verification and audit trail.
send from a template
curl -X POST https://api.flowverify.co/v1/templates/{template_id}/envelopes \
-H "Authorization: Bearer fv_live_xxxxxxxx" \
-H "Idempotency-Key: order-1042" \
-H "Content-Type: application/json" \
-d '{
"recipients": [
{ "role": "signer_1", "name": "Asha Rao", "email": "[email protected]" }
],
"reference": "order-1042"
}'What you can build
Send from your own productCreate envelopes from your documents or your templates, assign recipients, place fields and send — all in a few calls, safely retried with idempotency keys.Templates and bulk sendReuse prepared documents with roles and field layouts. Send one, or fan a draft out to thousands of recipients and follow the job.Track and downloadPoll a compact status view, read the full audit history, and stream the signed PDFs and the Certificate of Completion when done.WebhooksSigned, retried events for every envelope, recipient and approval transition, with a 30-day delivery log and one-click replay.
How a signature happens
The API prepares and sends; people sign in FlowVerify. That split is what makes the result legally sound.
- 1Your system creates and sendsA template or your own PDF, recipients, fields — then POST /send.
- 2The recipient is emailedOptionally verified by a one-time code or Aadhaar before the document opens.
- 3They sign in FlowVerifyConsent, identity and every action are recorded in the audit trail.
- 4You get the resultenvelope.completed hits your webhook; download the signed files and the certificate.