For AI agents & bots

DocFlow is an upload-and-sign e-signature service that your agent can drive end-to-end — without DocFlow ever being able to read the documents. This page is the shortest path to integrating.

Start here: sign yourself up — no human needed

POST /api/v1/signup with { email, agent_name } creates your own bot account and returns a df_test_ key immediately — no web form, no approval. Guards: 3 signups per IP per day; disposable email domains are rejected. Your test key works in the full flow with applied caps: 50 test processes/day, documents up to 10 MB.

To go live, verify your identity automatically — confirm an email code (POST /api/v1/bot/verify-email/request → POST /api/v1/bot/verify-email/confirm) or publish the DNS TXT record from the signup response and call POST /api/v1/bot/verify-dns/check — then create your df_live_ key with POST /api/v1/keys. Live caps on the free bot plan: 10 live documents/month, up to 5 signers per document, 60 requests/minute per key. Over a cap you get a clear QUOTA_EXCEEDED error — never a silent failure. The owner can suspend a bot account (all its keys rejected until reactivated) and sees every bot's plan, caps and usage.

What you can automate

  • Start a signing process from an uploaded document (PDF, DOCX converted to an HTML payload, or image): sequential or parallel, with signers, approvers and copy recipients, deadlines, access codes and per-signer private notes.
  • Poll process status: sent → opened → signed/approved → completed → delivered → purged (or expired / declined).
  • Receive webhooks for every transition (metadata + SHA-256 only).
  • Download the encrypted final signed PDF after delivery — decrypt it with the key your agent generated. Window: 7 days, then it's purged forever.
  • Record reminders, replace a participant who hasn't acted, and cancel in-flight processes.
  • Work safely with df_test_ keys: test processes stay in the test environment, separate from live data.

The 5-minute path

  1. Sign up by API — POST /api/v1/signup — and get a df_test_… key on the spot (or use a human's account: they create keys in Settings → API). Keys go in Authorization: Bearer …. Verify + POST /api/v1/keys when you need a df_live_… key.
  2. Generate an AES-256-GCM key in your agent. Encrypt the payload JSON. Keep the key — losing it means losing the document, by design.
  3. POST /api/v1/processes with ciphertext + ordered signers. You get a link token per signer.
  4. Deliver each signer their link: {app}/#/sign/{token}?k={your-key}. Humans sign in a browser; no account needed.
  5. Watch webhooks or poll GET /api/v1/processes/{id}. On delivered, decrypt final_cipher_text with your key.

Full reference: API documentation + OpenAPI 3.1 spec · Machine summary: llms.txt

Prefer tools? Connect over MCP

DocFlow also runs a remote MCP server (Streamable HTTP) at https://getdocflow.eu/mcp — the same capabilities as tools your agent runtime can call directly: docflow_create_process, docflow_get_process, docflow_list_processes, docflow_download_signed_pdf, docflow_get_audit_trail, docflow_cancel_process, docflow_remind_signer, docflow_replace_signer, docflow_request_feature. Authenticate with the same API key (Authorization: Bearer df_live_…) — no separate credential. Full catalog, connection snippets, a live tool-call playground and the server.json registry manifest: MCP server page.

Missing a capability? Don't just stop — tell us

Call POST /api/v1/feature-requests (API key optional) or use the feature-request form. Say what you were trying to do, what's missing, and your use case. Never include document content. Requests are proposals: the owner personally reviews and approves every feature, and submission doesn't guarantee implementation. Requests that conflict with DocFlow's principles (no document storage, E2EE, minimal log, free signers) are declined by design.