📄DocParse Docs
Dashboard

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 /extract│ →  │ DocParse engine │ →  │ JSON back │
└──────────┘    └──────────────┘    └─────────────────┘    └───────────┘
                       ↑                                          ↓
                       │                                          │
                       └────── poll /status OR webhook ───────────┘
  1. Define an Extraction template in the dashboard — basically a schema: the fields you want, their types, optional examples.
  2. Upload documents to that template via the REST API.
  3. Get results back either synchronously (for fast jobs) or via the webhook you've configured.

Two completion patterns

  • Polling — call GET /extractions/{id}/status until status is processed. 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 →

Free tier

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

Where to next