DocuflexDocuflex › E-signature › API checklist
E-signature API comparison checklist
Questions worth asking any e-signature API before you build on it, and how Docuflex answers each one.
Create a Docuflex account Read the API reference Connect your AI agent
| Question | Docuflex |
|---|---|
| Can I send and sign entirely through the API? | Yes: upload, create+send in one call, embedded signing URL, status, documents, certificate, audit trail. |
| How is the signed PDF protected? | Fields flattened, PKCS#7 (PAdES-ready) seal over the whole byte range, SHA-256 before and after, Certificate of Completion. |
| Can a third party verify a document without my account? | Yes: public GET /v1/verify/{envelopeId} re-checks hashes, the audit chain and the seal. |
| How are webhooks secured? | HMAC-SHA256 signatures, retries with backoff, delivery log, replay. |
| What auth options exist? | API keys, OAuth2 authorization-code with PKCE, jwt-bearer grant. |
| Which laws does the consent flow address? | ESIGN and UETA (versioned disclosure recorded before signing); eIDAS SES. |
| Is there an OpenAPI spec and SDK? | OpenAPI 3 at /openapi.json; TypeScript SDK; Postman and Bruno collections. |
| Can my AI assistant use it? | Yes, through the public MCP server at https://docuflex.net/mcp. |