/// EDIT
3 credits

Split PDF by Type API — auto-sort a mixed PDF into separate documents

Feed in one scanned batch of mixed document types; get back one file per document, correctly grouped.

/// Quick answer

Split by Type classifies every page against your label set (the same labeling used by `pdf-classify`), then groups contiguous pages that share a label into one output document — a continuation heuristic keeps a low-confidence page attached to its neighbor's label rather than starting a spurious new document over one uncertain page. The response is a ZIP of one file per detected document plus a manifest listing each output's label, page range and confidence; a batch over 20 pages runs asynchronously and is polled like any other async job.

Try Split PDF by Type API — free →Read the docs

How does the Split PDF by Type API work?

One HTTP request from any language. Every ASHDOCS endpoint uses the same X-API-Key header.

curl -X POST 'https://api.ashdocs.com/api/v2/tools/pdf-split-by-type' \
  -H 'X-API-Key: ash_live_...' \
  -F 'file=@mixed-batch.pdf' -F 'options={"labels":[{"name":"invoice","description":"a bill"},{"name":"receipt","description":"a proof of payment"}]}'

Common use cases

Frequently asked questions

How much does the Split PDF by Type API tool cost?+

3 credits per successful call. Sandbox keys (prefix ash_test_) run the tool end-to-end without ever consuming credits — use them in CI or for tuning.

What is the endpoint URL for this tool?+

The endpoint is documented in the curl example on this page. All ASHDOCS endpoints share the base URL https://www.ashdocs.com and require an X-API-Key header.

Can I run this tool inside Make, Zapier, or n8n?+

Yes — through each platform's built-in HTTP mechanism (Make's HTTP module, Webhooks by Zapier, n8n's HTTP Request node). Nothing to install: point it at this exact endpoint with your X-API-Key header. See /integrations/make, /integrations/zapier or /integrations/n8n for step-by-step setup.

Does this tool support batch or scheduled runs?+

Yes. POST /api/v1/batch runs any tool over up to 50 files with a single credit ledger entry, and pipeline schedules let you trigger the same tool on a cron. Both are documented in /docs.

RELATED TOOLS