Email Ingestion

Each extraction can expose a unique forwarding address. Email or forward documents to it and the attachments are imported, extracted, and validated automatically — no manual uploading.

How it works

1. Open an extraction → Email import → toggle it on. DocParse generates a unique address like ingest-ab12xy@inbound.docparse.in.
2. Mail sent to that address is received by an inbound-email provider you configure (see below), which forwards it to the DocParse webhook POST /ingest/email.
3. DocParse reads the address, matches the token to your extraction, imports the attachments into a new batch, and runs the normal extraction + validation pipeline.

Toggle ingestion off any time, or rotate the address (which immediately invalidates the old one).

One-time setup (operator)

Email ingestion is provider-agnostic — pick whichever inbound-email service you prefer (SendGrid Inbound Parse, Mailgun Routes, Cloudflare Email Routing, etc.). Two steps:

1. DNS: add an MX record for the ingest subdomain (default inbound.docparse.in) pointing at your provider's inbound mail host. Leave your root-domain mail records untouched.
2. Provider: configure the provider to forward inbound mail to your DocParse backend at POST /ingest/email.

The webhook accepts both the multipart format providers like SendGrid and Mailgun send, and a simple JSON format, so switching providers needs no code change.

The forwarding address contains an unguessable, rotatable token. For production, also enable your provider's request-signature verification.