Export Destinations

Push extracted data to where it needs to go automatically — a webhook, an automation platform (Zapier/Make), or your own service — instead of downloading files by hand.

Where to configure

Dashboard → open an extraction → Export → Add destination.

A destination has:

Field	Options
Target URL	Any `https://` (or `http://`) endpoint.
Format	`JSON` (full payload) or `CSV` (flattened row).
Trigger	`on processed` (as soon as extraction finishes) or `on confirmed` (after a reviewer approves).

What gets sent

For JSON, the body looks like:

json

{
  "event": "extraction.exported",
  "extractionId": "…",
  "fileId": "…",
  "fileName": "invoice-001.pdf",
  "data": { "...": "your extracted fields" }
}

Every request is signed so the receiver can verify it came from DocParse:

Header x-docparse-signature: v1,<base64 HMAC-SHA256> over the body, using the destination's secret.
Header x-docparse-extraction with the extraction id.

Triggers

on processed — fires for every document the moment it's extracted (including email-ingested ones, since they share the same pipeline).
on confirmed — fires only after a reviewer confirms the document in the Review Queue. Use this when you only want human-approved data downstream.

Testing & logs

Each destination has a Send test button that delivers a sample payload immediately and shows the HTTP status. Every real and test delivery is recorded in a delivery log (status code, success/failure, timestamp).

Export vs Webhooks

Export destinations push the extracted data itself to your URL (no code needed). Webhooks instead send a lightweight event (IDs + status) and expect your code to fetch the results. See the full comparison in Webhooks vs Export destinations.