Document processor outputs follow standardized formats based on the processor type. Understanding these formats is essential when working with evaluation sets, webhooks, and API responses.

​
Extraction output type (JSON Schema)

This section is relevant for processors using the JSON Schema config type. If you are using the Fields Array config type, please see the Extraction output type (Fields Array) documentation. If you aren’t sure which config type you are using, please see the Migrating to JSON Schema documentation.

The output structure for JSON Schema processors is composed of two properties: value and metadata.

The value object is the actual data extracted from the document which conforms to the JSON Schema defined in the processor config.

The metadata object holds details like confidence scores and citations for the extracted data. It uses keys that represent the path to the corresponding data within the value object. Crucially, the keys in the metadata object mirror the structure of the value object using a path-like notation (e.g., line_items[0].description), allowing you to precisely pinpoint metadata for any specific field, including those nested within objects or arrays. For instance, if your data has value.line_items[0].name, the metadata specifically for that name field will be found using the key ‘line_items[0].name’ within the metadata object.

​
Type definition

type ExtractionOutput = {
  value: ExtractionValue;
  metadata: ExtractionMetadata;
};

type ExtractionValue = Record<string, any>; // Conforms to the schema defined in the processor config
type ExtractionMetadata = {
  [key: string]: ExtractionMetadataEntry | undefined;
};

type ExtractionMetadataEntry {
  ocrConfidence?: number | null;
  logprobsConfidence: number | null;
  citations?: Citation[];
  insights?: OutputInsight[];
}

type Citation = {
  page?: number;
  referenceText?: string | null;
  polygon?: Point[];
};

type Point = {
  x: number;
  y: number;
};

type OutputInsight = {
  type: "reasoning";
  content: string;
};

​
Accessing Metadata

To access the metadata for a specific field, especially nested ones like items in an array, you use a path-like key string. For example, to get the metadata for the description of the first item in a line_items array, the key would be line_items[0].description.

Here are examples in Python and TypeScript:

const output = {
  value: {
    invoice_number: "INV-123",
    line_items: [
      { description: "Item A", quantity: 2, price: 10.0 },
      { description: "Item B", quantity: 1, price: 25.5 },
    ],
  },
  metadata: {
    invoice_number: {
      logprobsConfidence: 1,
      ocrConfidence: 0.99,
      citations: [
        {
          referenceText: "Invoice #: INV-123",
          page: 1,
          polygon: [
            { x: 296.73359999999997, y: 40.888799999999996 },
            { x: 386.4168, y: 40.464000000000006 },
            { x: 386.4744, y: 52.1712 },
            { x: 296.7912, y: 52.596000000000004 },
          ],
        },
      ],
    },
    line_items: {
      logprobsConfidence: 0.98,
      ocrConfidence: 0.98,
    },
    "line_items[0]": {
      logprobsConfidence: 0.98,
      ocrConfidence: 0.98,
      citations: [{ page: 1 }],
    },
    "line_items[0].description": { logprobsConfidence: 1, ocrConfidence: 0.95 },
    "line_items[0].quantity": { logprobsConfidence: 1, ocrConfidence: 0.98 },
    "line_items[0].price": { logprobsConfidence: 1, ocrConfidence: 0.98 },
    "line_items[1].description": { logprobsConfidence: 1, ocrConfidence: 0.96 },
    // Other metadata entries...
  },
};

// Traversing the output object and accessing metadata
const invoiceNumber = output.value.invoice_number;
const invoiceNumberMetadata = output.metadata.invoice_number;

// Access metadata for the line_items array itself
const lineItemsMetadata = output.metadata.line_items;

// Loop through line items array
for (let i = 0; i < output.value.line_items.length; i++) {
  const lineItemPath = `line_items[${i}]`;

  // Access the line item object and its metadata
  const lineItem = output.value.line_items[i];
  const lineItemMetadata = output.metadata[lineItemPath];

  // Access properties within the line item and their metadata
  const lineItemDescription = lineItem.description;
  const lineItemDescriptionMetadata =
    output.metadata[`${lineItemPath}.description`];
  const lineItemQuantity = lineItem.quantity;
  const lineItemQuantityMetadata = output.metadata[`${lineItemPath}.quantity`];
  const lineItemPrice = lineItem.price;
  const lineItemPriceMetadata = output.metadata[`${lineItemPath}.price`];
}

​
Examples

​
Extraction output type (Fields Array)

This section is relevant for the Fields Array config type. If you are using the JSON Schema config type, please see the Extraction output type (JSON Schema) documentation. If you aren’t sure which config type you are using, please see the Migrating to JSON Schema documentation.

For processors using the legacy Fields Array configuration, the extraction output is a flat dictionary where each key is the fieldName (or sometimes the id if names aren’t unique) you defined in the configuration, and the value is an ExtractionFieldResult object containing the extracted data and associated details.

​
Type definition

Each ExtractionFieldResult object contains the core id, type, and extracted value. It can also include the following optional details:

  • schema: The schema definition for nested fields (like objects or array items).
  • insights: Reasoning or explanations from the model (if enabled).
  • references: Location information, including the page number and specific Bounding Boxes relevant to the legacy Fields Array configuration (see Bounding Boxes Guide).
  • enum: The available options if the field type is enum.
type ExtractionOutput = {
  [fieldName: string]: ExtractionFieldResult;
};

type ExtractionFieldResult = {
  id: string;
  type:
    | "string"
    | "number"
    | "currency"
    | "boolean"
    | "date"
    | "enum"
    | "array"
    | "object"
    | "signature";
  value:
    | string
    | number
    | Currency
    | boolean
    | Date
    | ExtractionValueArray
    | ExtractionValueObject
    | Signature
    | null;

  /* The following fields are included in outputs, but not required for creating an evaluation set item */

  /* Includes the field schema of nested fields (e.g. array fields, object fields, signature fields etc) */
  schema: ExtractionFieldSchemaValue[];

  /* Insights the reasoning and other insights outputs of the model (when reasoning is enabled) */
  insights: Insight[];

  /* References for the extracted field, always includes the page number for all fields, and might include bounding boxes and citations when available. */
  references: ExtractionFieldResultReference[];

  /* The enum options for enum fields, only set when type=enum */
  enum: EnumOption[];
};

type Currency = {
  amount: number;
  iso_4217_currency_code: string;
};

type Signature = {
  printed_name: string;
  signature_date: string;
  is_signed: boolean;
  title_or_role: string;
};

type EnumOption = {
  value: string; // The enum value (e.g. "ANNUAL", "MONTHLY", etc.)
  description: string; // The description of the enum value
};

type ExtractionValueArray = Array<ExtractionValueObject>;
type ExtractionValueObject = Record<string, any>;

​
References

type ExtractionFieldResultReference = {
  /* The field id. When nested for arrays, this is the index of the row number */
  id: string;
  /* The field name */
  fieldName: string;
  /* The page number (starting at 1) that this bounding box is from */
  page: number;
  /**
   * Array of bounding box references for this field.
   * There can be multiple is the extraction result was drawn from multiple distinct sources on the page.
   */
  boundingBoxes: BoundingBox[];
};

/* See the Bounding boxes guide for information on how to use/interpret this data */
type BoundingBox = {
  /* The left most position of the bounding box */
  left: number;
  /* The top most position of the bounding box */
  top: number;
  /* The right most position of the bounding box */
  right: number;
  /* The bottom most position of the bounding box */
  bottom: number;
};

​
Examples

​
Classification Output Type

​
Type Definition

type ClassificationOutput = {
  id: string;
  type: string;
};

​
Example

{
  "id": "classification_123",
  "type": "INVOICE"
}

​
Splitter Output Type

​
Type Definition

type SplitterOutput = {
  splits: Split[];
};

type Split = {
  classificationId: string; // The id of the classification type (set in the processor config)
  type: string; // The type of the split document (set in the processor config), corresponds to the classificationId.
  startPage: number; // The start page of the split document
  endPage: number; // The end page of the split document

  // Fields included in outputs, but not required for creating an evaluation set item
  identifier?: string; // Identifier for the split document (e.g. invoice number)
  observation?: string; // Explanation of the results
};

​
Example

{
  "splits": [
    {
      "classificationId": "invoice",
      "type": "invoice",
      "startPage": 1,
      "endPage": 3
    },
    {
      "classificationId": "other",
      "type": "other",
      "startPage": 4,
      "endPage": 5
    }
  ]
}

​
Shared Types

Certain types are shared across different processor outputs. These provide additional context and information about the processor’s decisions.

​
Type Definition

type Insight = {
  type: "reasoning"; // Currently only reasoning is supported
  content: string; // The explanation or reasoning provided by the model
};

​
Example

{
  "insights": [
    {
      "type": "reasoning",
      "content": "This was classified as an invoice because it contains standard invoice elements including an invoice number, billing details, and itemized charges."
    }
  ]
}

Insights can appear in both Extraction and Classification outputs to provide transparency into the model’s decision-making process. They are particularly useful when debugging or validating processor results.