Changelog

Two new endpoints make bulk background processing easier:

• /extract/batch — queue thousands of files for extraction in the background without running into rate limits.
• /parse/batch — bulk background parse operations.

Composer is now available for splitters, so you can optimize them automatically from eval sets. Previously, Composer was only available for extractors and classifiers.

If you’re working on splitting, check out our Splitter Benchmark to see how we evaluate models.

The new parse engine can now parse formula blocks as LaTeX. Enable it as an advanced option to extract math content directly from documents.

The new parse engine now detects and annotates strikethrough text via a specialized model. Enable it as an advanced option in the parser config.

You can now create, update, and delete workflows and workflow versions entirely via API. Previously, workflows could only be managed in the Extend dashboard. This makes it easier to generate workflows programmatically, check configs into code, manage them with CI/CD, and build them with agents like Claude Code.

1
await client.workflows.update("workflow_abc123", {
2
    steps: [
3
      { "name": "trigger", "type": "TRIGGER", "next": [{ "step": "parse" }] },
4
      { "name": "parse", "type": "PARSE", "next": [{ "step": "split" }] },
5
      {
6
        "name": "split",
7
        "type": "SPLIT",
8
        "config": {
9
          "splitter": { "id": "spl_abc123", "version": "0.1" }
10
        },
11
        "next": [
12
          { "step": "extract_invoice", "classificationId": "cls_invoice" },
13
          { "step": "extract_receipt", "classificationId": "cls_receipt" },
14
          { "step": "review", "classificationId": "cls_other" }
15
        ]
16
      },
17
      { "name": "review", "type": "HUMAN_REVIEW", "next": [{ "step": "collect" }] },
18
      { "name": "collect", "type": "COLLECT", "next": [{ "step": "webhook" }] },
19
      { "name": "webhook", "type": "WEBHOOK_RESPONSE" }
20
    ]
21
});

See the full documentation.

The form detection and schema generation we offer in Studio is now available as a standalone API, making it faster to create forms and templates for known document types.

See the API reference.

The Light Parser now uses our new layout model, with smaller models for tables, forms, reading order, and other layout types — at a fraction of the cost and latency of the Performance Parser. It’s built for very high-volume ingestion workloads where cost matters, billed at 0.5 credits per page.

You can now include signature images in your e-signing workflows for more complete digital signing experiences.

See the API reference.

A new compare UI in the parse playground lets you quickly see differences between parse engines and advanced options side by side.

Forms often contain implicit conditional behavior — like “If you said ‘Yes’ to ___, then fill in ____.” In many industries, missing these rules can cause serious downstream issues in automated form-filling pipelines.

The Edit API now supports the full range of conditional logic expressible in JSON Schema, including if / then / else, dependentRequired, allOf, oneOf, anyOf, and not. You can also auto-generate these rules for a form from a single sample document.