DocParse Docs

Overview

A high-level picture of how DocParse works end-to-end. If you're new here, this gives you the mental model in 5 minutes.

The flow

plaintext
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Your app β”‚ β†’  β”‚ POST /api/v1/create…  β”‚ β†’  β”‚ DocParse engine β”‚ β†’  β”‚ JSON back β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           ↑                                               ↓
                           β”‚                                               β”‚
                           └──── poll getBatchResults OR webhook β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  1. Create an Extraction β€” call POST /api/v1/createExtraction with your field schema and files in a single multipart request.
  2. Upload more documents via POST /api/v1/uploadFiles β€” each call creates a new batch automatically.
  3. Get results back by polling POST /api/v1/getBatchResults or via the webhook you've configured.

Two completion patterns

  • Polling β€” call POST /api/v1/getBatchResults until all files reach a terminal status. Good for ad-hoc scripts and CLI tools.
  • Webhook β€” register a URL in the dashboard's API page. We POST the results to your endpoint when each file finishes. Good for production integrations.

See Polling vs Webhook for the detailed comparison.

Two products

DocParse has two API surfaces:

  • Data Extraction API β€” schema-driven field extraction. You define what fields to pull from invoices/receipts/forms; we return them as JSON. Endpoints β†’
  • Document Classification API β€” given a folder of mixed documents, sort each one into a category (invoice / contract / resume / etc.) and optionally chain into an extraction template per category. Endpoints β†’

Beyond extraction

Extraction is the start. DocParse also makes the data trustworthy, reviewable, automatically delivered, and measurable:

  • Validation Rules β€” business-rule checks that run after every document and flag bad data for review.
  • Review Queue β€” one cross-extraction inbox of documents needing a human; confirm or correct, and they clear.
  • Email Ingestion β€” a forwarding address per extraction; emailed attachments import and extract automatically.
  • Export Destinations β€” push results (JSON/CSV, signed) to a URL or automation tool on processed or on confirmed.
  • Analytics β€” straight-through-processing rate, exception rate, validation pass rate, and per-extraction breakdowns.

Free tier

Every account gets 100 pages every month, free, forever. Once you're past 100, see pricing.

Where to next