​
Document Processor Configuration Guide

Document processors are the core components that analyze and manipulate information from your documents. This guide explains how to configure processors through our API, including detailed examples for each processor type.

​
Overview

We support three types of document processors:
  • Extraction Processors: Extract specific fields from documents.
  • Classification Processors: Categorize documents.
  • Splitter Processors: Divide documents into logical sub-documents.
Generally we recommend using our UI for configuration, but the API can be useful in programmatic workflows, when you need to configure a large number of processors, or when you need to keep your configurations in source control and versioned. You can also use our webhook events to consume changes made to configurations in the Extend Dashboard and keep your saved configurations in sync.

​
Schema Definitions

​
Base Processor Schema

All processor configurations share these base properties: 
type BaseProcessorConfig = {
  // Base properties inherited by all processor types
  baseProcessor?: string;
  baseVersion?: string;
};
They will be set by default to latest available on processor creation unless otherwise specified - see Changelog for more details. Specify these if you need to pin your processor to a specific underlying model version for consistent behavior or to use features available only in certain versions.

​
Extraction Processor Configuration

Extraction processors extract specific fields from documents. 
// Either schema or fields must be provided, but not both
type ExtractionConfig = {
  type: "EXTRACT";
  baseProcessor?: string;
  baseVersion?: string;
  extractionRules?: string;
  schema: RootJSONSchema; // See the JSON Schema Structure section below
  fields: ExtractionField[]; // (Deprecated) See the Fields Array section below
  advancedOptions?: ExtractionAdvancedOptions;
};

type ExtractionAdvancedOptions = {
  documentKind?: string;
  keyDefinitions?: string;
  modelReasoningInsightsEnabled?: boolean;
  advancedMultimodalEnabled?: boolean;
  citationsEnabled?: boolean;
  autoReviewAssistantEnabled?: boolean;
  advancedFigureParsingEnabled?: boolean;
  chunkingOptions?: ExtractChunkingOptions;
  fixedPageLimit?: number;
};

type ExtractChunkingOptions = {
  chunkingStrategy?: "standard" | "semantic";
  pageChunkSize?: number;
  chunkSelectionStrategy?:
    | "intelligent"
    | "confidence"
    | "take_first"
    | "take_last";
  customSemanticChunkingRules?: string;
};

​
JSON Schema Structure (schema)

This section is relevant for processors using the JSON Schema config type. If you are using the legacy Fields Array config type, please see the Fields Array Structure documentation. If you aren’t sure which config type you are using, please see the Migrating to JSON Schema documentation.
We use JSON Schema to define the structure of the data we extract. Before you get started, we recommend familiarizing yourself with the JSON Schema documentation to understand how to define your schema. The standard JSON Schema is extremely flexible. We’ve implemented a subset of the standard to support the needs of document extraction. Your schema must follow these rules:
  • The root must be an object type
  • Allowed types are string, number, integer, boolean, object, and array
  • All primitive fields (string, number, boolean, integer) must be nullable (use array type with “null” as an option e.g. "type": ["string", "null"])
  • Maximum nesting level is 3 (each non-root object counts as 1 level)
  • Property keys and names must only contain lowercase letters, numbers, and underscores
  • Array items must be objects
  • Enums must only contain strings and must contain a null option
  • Custom types are supported by adding a "extend:type": "currency", "extend:type": "signature", or "extend:type": "date" property to the appropriate field type with the required properties. See below for examples.
  • Property names can be added using the "extend:name" property. If supplied, this will override the name of the property as it will appear to the model, but not in the output returned to you. This is useful for providing more descriptive names or instructions to the model without altering the actual keys in your output data structure.
  • You can add descriptions to individual enum values using the "extend:descriptions" property.

​
Unsupported Features

While we support the JSON Schema structure, we do not support many of the additional features some of which include:

​
Schema Examples

​
Primitive Schema

All primitive types must be nullable. 
{
  "field_name": {
    "type": ["string", "null"],
    "description": "Field description"
  },
  "numeric_field": {
    "type": ["number", "null"],
    "description": "A numeric field"
  },
  "integer_field": {
    "type": ["integer", "null"],
    "description": "An integer field"
  },
  "boolean_field": {
    "type": ["boolean", "null"],
    "description": "A boolean field"
  }
}

​
Object Schema

Objects must have properties. If you set a required array of the properties, we will respect that order when extracting. If you do not set required array, we will generate it and enforce order. 
{
  "address": {
    "type": "object",
    "properties": {
      "street": {
        "type": ["string", "null"],
        "description": "Street address"
      },
      "city": {
        "type": ["string", "null"],
        "description": "City name"
      }
    },
    "required": ["street", "city"]
  }
}

​
Array Schema

Arrays items must be objects. 
{
  "line_items": {
    "type": "array",
    "items": {
      "type": "object",
      "properties": {
        "description": {
          "type": ["string", "null"],
          "description": "Item description"
        },
        "quantity": {
          "type": ["number", "null"],
          "description": "Item quantity"
        },
        "price": {
          "type": ["number", "null"],
          "description": "Item price"
        }
      },
      "required": ["description", "quantity", "price"]
    },
    "description": "List of items in the invoice"
  }
}

​
Enum Schema

Enums must include null as an option. Only strings are supported for enums. The extend:descriptions is an optional array of strings. It is recommended to give more context for each enum option for more accurate extraction. 
{
  "status": {
    "enum": ["pending", "approved", "rejected", null],
    "extend:descriptions": [
      "Invoice is pending approval",
      "Invoice has been approved",
      "Invoice has been rejected",
      ""
    ],
    "description": "Current status of the invoice"
  }
}

​
Custom Field Types

The extend:type keyword enables custom pre-processing and post-processing of fields which bake in best practices and heuristics for the field type.

​
Date Schema

Date fields must be strings and use the extend:type keyword with the value date. This will guarantee the date format is always an ISO compliant date (yyyy-mm-dd). 
{
  "invoice_date": {
    "type": ["string", "null"],
    "extend:type": "date",
    "description": "The invoice date"
  }
}

​
Currency Schema

Currency fields must be objects with specific properties. 
{
  "price": {
    "type": "object",
    "extend:type": "currency",
    "properties": {
      "amount": {
        "type": ["number", "null"],
      },
      "iso_4217_currency_code": {
        "type": ["string", "null"],
      }
    },
    "required": ["amount", "iso_4217_currency_code"]
  }
}

​
Signature Schema

Signature fields must be objects with specific properties. This will auto-enable our advanced signature detection in the parsing step prior to extraction, and apply a number of prompt and post-processing heuristics to improve accuracy, particularly on reduction of false positives for signature blocks that are not actually signed. 
{
  "signature": {
    "type": "object",
    "extend:type": "signature",
    "properties": {
      "printed_name": {
        "type": ["string", "null"],
      },
      "signature_date": {
        "type": ["string", "null"],
        "extend:type": "date",
      },
      "is_signed": {
        "type": ["boolean", "null"],
      },
      "title_or_role": {
        "type": ["string", "null"],
      }
    },
    "required": ["printed_name", "signature_date", "is_signed", "title_or_role"]
  }
}

​
Configuration Examples

Basic Example

​
Type Definitions

​
Fields Array Structure (fields)

This section is relevant for the Fields Array config type. If you are using the JSON Schema config type, please see the JSON Schema Structure documentation. If you aren’t sure which config type you are using, please see the Migrating to JSON Schema documentation.
type ExtractionField = {
  id: string;
  name: string;
  type:
    | "string"
    | "number"
    | "currency"
    | "boolean"
    | "date"
    | "array"
    | "enum"
    | "object"
    | "signature";
  description: string;
  // Required for nested fields (arrays, objects, signatures)
  schema?: ExtractionField[];
  // Required for enums
  enum?: Enum[];
};

type Enum = {
  value: string;
  description: string;
};

​
Configuration Examples

Basic Example

​
Classification Processor Configuration

Classification processors categorize documents into predefined types. 
type ClassificationConfig = {
  type: "CLASSIFY";
  baseProcessor?: string;
  baseVersion?: string;
  classifications: Classification[];
  classificationRules?: string;
  advancedOptions?: ClassificationAdvancedOptions;
};

type Classification = {
  id: string;
  type: string;
  description: string;
};

type ClassificationAdvancedOptions = {
  context?: "default" | "max";
  advancedMultimodalEnabled?: boolean;
  fixedPageLimit?: number;
};

​
Configuration Example

const classificationConfig = {
  type: "CLASSIFY",
  classifications: [
    {
      id: "invoice",
      type: "INVOICE",
      description: "Standard invoice document ...",
    },
    {
      id: "bill_of_lading",
      type: "BILL_OF_LADING",
      description: "Bill of Lading document ...",
    },
  ],
  classificationRules: "- If ...", // Optional custom rules
};

​
Splitter Processor Configuration

Splitter processors divide documents into logical sub-documents based on defined classifications. 
type SplitterConfig = {
  type: "SPLITTER";
  baseProcessor?: string;
  baseVersion?: string;
  splitClassifications: Classification[];
  splitRules?: string;
  advancedOptions?: SplitterAdvancedOptions;
};

type SplitterAdvancedOptions = {
  splitIdentifierRules?: string;
  splitMethod?: "high_precision" | "low_latency";
  splitExcelDocumentsBySheetEnabled?: boolean;
  fixedPageLimit?: number;
};

​
Configuration Example

const splitterConfig = {
  type: "SPLITTER",
  splitClassifications: [
    {
      id: "purchase_contract",
      type: "PURCHASE_CONTRACT",
      description: "Purchase contract section",
    },
    {
      id: "addendum",
      type: "ADDENDUM",
      description: "Addendum section",
    },
  ],
  splitRules: "- If ...", // Optional custom rules
  advancedOptions: {
    splitMethod: "high_precision",
  },
};