Docuflex › E-signature

E-signature platform and REST API

Docuflex is an e-signature platform with a developer-first REST API. Send documents for signature, embed signing in your own product, run bulk sends, receive signed webhooks, and get digitally sealed PDFs with a hash-chained audit trail. The API uses the same concepts as DocuSign eSignature, so integrators already know the shape.

Create a Docuflex account Read the API reference Connect your AI agent

What you get

Envelopes

Draft, send, sign and seal lifecycle driven by an explicit state machine; sequential and parallel routing; void, decline, expire; automatic reminders and expiration.

Recipients

Nine recipient types: signer, in-person signer, cc, certified delivery, agent, editor, intermediary, notary and witness; routing order; per-recipient authentication by access code, SMS one-time code, knowledge-based or ID verification.

Tabs (fields)

Sixteen field types including signature, initials, date signed, text, checkbox, radio, dropdown, SSN and attachment; regex validation; conditional show/hide logic; prefill bindings.

Documents

PDF upload inline as base64 or as a staged upload; bytes live only in object storage; SHA-256 recorded at every step.

Signing ceremony

Token-gated public flow: consent disclosure, authentication challenges, view, adopt a signature, fill fields, complete. Embedded signing inside your own app via clientUserId.

Sealing

Fields are flattened into the PDF, then a PKCS#7 (PAdES-ready) digital signature is applied. A Certificate of Completion PDF is produced and a public /verify endpoint re-checks hashes and the seal.

Audit trail

Hash-chained, append-only audit events per envelope with IP, user agent and geo capture, plus a chain-verification endpoint.

Consent

Versioned ESIGN/UETA disclosure; consent records with IP and user agent captured before any signing action.

Templates

Reusable role and field definitions, instantiated into envelopes, versioned.

Bulk send

CSV-backed recipient lists fanned out to one envelope per row, with per-row results.

Webhooks (Connect)

Per-account webhook configurations, HMAC-SHA256 signed deliveries, retries with exponential backoff, a delivery log and replay.

Authentication

API keys (x-api-key header, keys look like dfx_live_...), OAuth2 authorization-code with PKCE, and a JWT-bearer grant that mirrors DocuSign's JWT grant. Interactive login via Clerk, including Google sign-in.

API platform

Everything under /v1, zod-validated, one uniform error envelope, offset and cursor pagination, Idempotency-Key replay protection, rate-limit headers on every response, OpenAPI 3 spec.

Jurisdiction library

Seeded document library with per-jurisdiction legality metadata and a mandatory, server-enforced counsel-review disclaimer.

Quick start (five calls)

export BASE=https://api.docuflex.net
# 1. key: Account settings → API keys (dfx_live_...), sent as x-api-key
# 2. stage a PDF
curl -s -H "x-api-key: $API_KEY" -X POST $BASE/v1/accounts/$ACCOUNT/uploads -F 'file=@contract.pdf;type=application/pdf'
# 3. create + send in one call (tab coordinates are fractions of the page, origin top-left)
curl -s -H "x-api-key: $API_KEY" -H 'content-type: application/json' -H "Idempotency-Key: $(uuidgen)" \
  -X POST $BASE/v1/accounts/$ACCOUNT/envelopes -d '{"subject":"Please sign the NDA","routingType":"sequential",
  "documents":[{"uploadId":"UPLOAD_ID","name":"contract.pdf"}],
  "recipients":[{"name":"Ada Lovelace","email":"ada@example.com","routingOrder":1}],
  "tabs":[{"documentIndex":0,"recipientIndex":0,"type":"signature","page":1,"x":0.1,"y":0.85,"width":0.3,"height":0.06}],
  "status":"sent"}'
# 4. embedded signing URL: POST .../envelopes/$ID/views/recipient
# 5. anyone can verify integrity: GET $BASE/v1/verify/$ID

Built for compliance evidence

ESIGN / UETA: intent (explicit adopt-sign-complete chain), consent (versioned disclosure, recorded with IP and user agent before signing), attribution (access code, SMS code, KBA, ID verification), retention (append-only records enforced by database triggers), copies (completed bundle emailed to every party at no charge).
Record integrity: SHA-256 at upload and after sealing, hash-chained audit events, PKCS#7 seal over the whole PDF byte range, independent /verify endpoint, Certificate of Completion as PDF and JSON.
eIDAS: Simple Electronic Signature delivered; Advanced and Qualified levels are documented gaps, not offered.

Feature-flagged, off in production

Notary / remote online notarization (commissions, sessions, journal) - data model built, provider mocked, off in production
Web forms that generate envelopes - scaffold, off in production
Multi-step workflows - scaffold, off in production
Clickwrap agreements - scaffold, off in production
Data verification / file connectors (extensions) - scaffold, off in production

Pricing

Free. Create an account at docuflex.net/sign-up and start sending; the web app and the REST API are included. On-premises: Docuflex can run entirely inside your own perimeter (private inference, your hardware, your data). Contact sales at info@docuflex.us for an on-prem deployment.

Explore

Pricing

Free to use. On-premises deployment available through sales.

API reference by resource

Envelopes, recipients, tabs, signing, verify, templates, bulk send, Connect webhooks, OAuth.

DocuSign alternative

How Docuflex concepts map to DocuSign eSignature, for teams migrating an integration.

Use cases

Leases, real estate, property management, HR, NDAs, contractors and more.

E-signature law by state

ESIGN, UETA and New York's ESRA, with the documents the federal act leaves out.

For AI agents

MCP endpoint, llms.txt and the OpenAPI spec so an assistant can send documents for you.

Frequently asked

What is Docuflex?

Docuflex is an e-signature platform with a full REST API: envelopes, signing ceremonies, templates, bulk send, webhooks, tamper-evident audit trails and digitally sealed PDFs. It is an original implementation that targets functional parity with DocuSign eSignature, so the same concepts (envelopes, recipients, tabs, Connect, JWT grant) apply.

Is Docuflex affiliated with DocuSign?

No. Docuflex is not affiliated with, endorsed by, or derived from DocuSign, Inc. DocuSign is referenced only to describe functional equivalence.

Are Docuflex signatures legally binding in the United States?

Docuflex implements the ESIGN Act and UETA requirements for intent, consent, attribution and record integrity: a versioned consent disclosure captured before signing, per-recipient authentication, a hash-chained audit trail, SHA-256 hashes at upload and after sealing, a PKCS#7 seal and a public verification endpoint. Enforceability of a given document is a legal question for counsel.

Does Docuflex work in the EU?

The standard flow satisfies eIDAS Simple Electronic Signature (SES). Advanced (AES) and Qualified (QES) levels are not yet offered.

How do I get an API key?

Create an account at docuflex.net/sign-up, open Account settings, API keys, and create a key. Keys are shown once and look like dfx_live_.... Send them in the x-api-key header.

What is the API base URL?

https://api.docuflex.net, with every tenant-scoped route under /v1/accounts/{accountId}/...

Can an AI agent use Docuflex?

Yes. Docuflex publishes a remote MCP server at https://docuflex.net/mcp with tools to create, send, check and verify envelopes, plus llms.txt and the OpenAPI spec.

What does Docuflex cost?

Docuflex is free to use: create an account and send. For an on-premises deployment that runs on hardware you control, contact sales at info@docuflex.us.