All Classes and Interfaces

Class
Description
Represents a chunk of a document after it has been processed by a Docling chunker.
 
Response returned by the Chunk API for a single conversion request.
 
Abstract options for configuring a document chunker.
Options for configuring the document conversion process with Docling.
 
Represents a request to convert a document.
 
Response returned by the Convert API for a single conversion request.
 
Docling Serve API interface.
A builder interface for constructing implementations of DoclingServeApi.
Represents the document being processed by a Docling chunker.
 
A simple mutable POJO representing the converted document returned by the Docling Convert API.
 
Represents an individual error produced during document conversion.
 
Content of the original converted document, before getting chunked.
 
Represents a file-based data source.
 
Simple health check response returned by the API.
 
Represents a request to convert a document and chunk it into smaller documents using the Docling hierarchical chunker.
 
Options for configuring the hierarchical chunker.
 
Represents an HTTP-based data source.
 
Represents a request to convert a document and chunk it into smaller documents using the Docling hybrid chunker.
 
Options for configuring the hybrid chunker.
 
The mode for how to handle image references in the document.
Target for including the converted document in the response body.
 
A document format supported by document backend parsers.
OCR engines supported by Docling.
Document formats supported for output in Docling.
PDF backends supported by Docling.
Configuration options for picture description API integration.
 
Configuration for local picture description generation.
 
Pipelines used by Docling to process documents.
A concrete Target implementation for delivering a converted document to a specified URI via an HTTP PUT operation.
 
Type of response generated by the model.
Source of the document.
Modes for the TableFormer model.
Represents an abstract target for defining where and how the converted document should be delivered.
Utility methods.
Utility class for validating method arguments.
API details for using a vision-language model for the VLM pipeline.
 
Options for running a local vision-language model for the VLM pipeline.
 
Inference framework to use.
Type of transformers auto-model to use.
Local and API models for the VLM pipeline.
Represents a specific Target that delivers the converted document as a zipped resource.