This recipe uses theDocumentation Index
Fetch the complete documentation index at: https://docs.anyformat.ai/llms.txt
Use this file to discover all available pages before exploring further.
object field type with nested_fields to capture tabular line-item data.
Workflow fields
| Field | Type | Description |
|---|---|---|
invoice_number | string | The unique invoice identifier |
vendor_name | string | Name of the company issuing the invoice |
issue_date | date | Date the invoice was issued |
due_date | date | Payment due date |
subtotal | float | Amount before tax |
tax_amount | float | Total tax applied |
total_amount | float | Final amount due including tax |
currency | enum | Currency code (USD, EUR, GBP, …) |
line_items | object | Individual line items (description, quantity, unit_price, amount) |
End-to-end
Python package + class names are provisional.
pip install anyformat-sdk and from anyformat.sdk import Client work today, but both are expected to change before the official launch — pin the version you ship with.- curl
- TypeScript
- Python
Three-step flow: create the workflow, run a document, poll the results endpoint until it returns For production integrations, use webhooks instead of polling — they deliver results immediately and don’t consume your rate limit.
200.Example response
The full envelope is documented in Response formats. The top-level keys arecollection_id, verification_url, parse, classifications, splits, and extractions. Each scalar field follows the ExtractedField shape (value, value_override, verification_status, confidence, evidence).
Tips
- Write specific field descriptions. “Total amount due including tax” extracts better than just “total”.
- If invoices span multiple currencies, add the
enum_optionsfor all currencies you expect. - Multi-page invoices are handled automatically; no special configuration needed.
Next steps
Field types
Object, enum, and other complex field types
Response formats
Full schema of every section in the results envelope
