Overview
Turn documents into structured data, from your first template to a production backend integration. These guides cover building and testing extraction in the app, then wiring it into your own systems through the API.
Get started
Section titled “Get started”Most teams set up extraction in this order:
- Create a template for one document type, with the fields you want to extract.
- Test it in Playground or Quick Run until the output looks right.
- Decide how files get processed going forward: pick them up automatically with workflows (no code), or call the API yourself (synchronous or async).
- If you’ll call the API, create an API key.
- Optionally add webhooks or document review if downstream systems need automation or human approval.
Choose the right path
Section titled “Choose the right path”| Goal | Recommended path | Read next |
|---|---|---|
| Try extraction on one document by hand | Template plus Playground or Quick Run | Templates, Filters & Workflows |
| Process files automatically, no code | Workflow | Templates, Filters & Workflows |
| Set up API access | API key | Authentication & Errors |
| Extract one file and get the result now | Synchronous request | Synchronous Extraction |
| Run extraction from your backend in production | Async job | Asynchronous Extraction |
| Route different document types automatically | Filter | Templates, Filters & Workflows |
| Get notified when async work finishes | Async job plus webhook | Webhooks |
| Hold low-confidence results for review | Async job or workflow with document review | Asynchronous Extraction |
| See all API endpoints | Endpoint reference | Endpoint Reference |