The DocsFlow AI API converts PDFs, scans, invoices, IDs, and websites into structured JSON through five core endpoints, Bearer-token authentication, and official SDKs for Python, Node.js, Go, and Ruby. This guide explains the endpoints, how authentication works, what each response contains, and how the API protects document data.
What is the DocsFlow AI API?
The DocsFlow AI API is a REST interface that converts PDFs, scans, invoices, IDs, contracts, and websites into structured JSON with a single HTTP call. It pairs OCR with AI layout understanding so responses contain validated fields, tables, line items, and per-field confidence scores — not raw text. Developers call https://api.docsflowai.com with a Bearer API key and receive machine-readable output ready for databases, ERPs, and automation workflows.
How do I get started with the DocsFlow AI API?
Create a free account to generate a scoped API key, then send your first request to POST /v1/parse with a document file or URL. You receive a job ID immediately and a structured JSON response once processing completes. The free Starter plan includes 100 documents per month, and official SDKs for Python, Node.js, Go, and Ruby remove most setup work.
Which API endpoints does DocsFlow AI provide?
The API exposes five core endpoints. POST /v1/parse extracts structured data from documents. POST /v1/crawl starts an async website crawl, including JavaScript-rendered pages. POST /v1/parse/url parses a document directly from a download URL without uploading it. GET /v1/jobs/:id polls asynchronous job status and results, and GET /v1/account returns plan limits and usage.
How does API authentication work?
Pass your API key as an Authorization: Bearer header on every request — never in query parameters. All traffic must use HTTPS with TLS 1.2 or higher. Keys are scoped to read-only, write, or admin permissions, can be rotated from the dashboard without downtime, and are rate-limited per key. Revoked or over-limit keys return 403, and rate limits return 429 with a retry-after header.
How does the API handle security and data privacy?
Every document is processed in an isolated container and deleted immediately after the response is returned — DocsFlow AI keeps zero data retention. Requests require TLS 1.2+, API keys are scoped and rotatable, and processing runs under the same SOC 2 Type II, GDPR, and HIPAA-compatible controls as the rest of the platform. No third parties access your documents at any stage.