Supported Capabilities

Davix H2I provides a set of backend processing capabilities that allow applications, websites, and automation workflows to generate, transform, and analyze media and documents through a unified public API. These operations are exposed through the platform’s main /v1/* endpoint groups and are executed through the H2I engine (PixLab). Depending on the endpoint and action, the result may be returned as a generated file URL or as structured JSON data.

Capability Overview #

Davix H2I exposes the following core public processing endpoints:

• /v1/h2i — HTML rendering
• /v1/image — image processing
• /v1/pdf — PDF processing
• /v1/tools — analysis and utility tools.

Each endpoint supports a defined set of actions and route-specific parameters depending on the requested operation.

HTML Rendering #

HTML rendering is one of the central and defining capabilities of Davix H2I. It is also the original capability reflected in the H2I name, which stands for HTML to Image. The platform allows users to send HTML content and render it into either an image or a PDF document. Even as the platform has expanded into additional capability categories, HTML rendering remains one of its foundational features.

The public HTML-rendering endpoint is:

• /v1/h2i

This endpoint supports two actions:

• image
• pdf

For successful file-producing requests, /v1/h2i returns a signed output URL in the response.

Common use cases include:

• report generation
• certificates
• social media images
• dynamic document rendering
• automated visual and document outputs.

Image Processing #

Davix H2I provides a broad set of image-processing operations through:

• /v1/image

This endpoint accepts multipart/form-data uploads and supports a defined action surface for transforming and processing uploaded image files. The public action list is:

• format
• resize
• crop
• transform
• compress
• enhance
• padding
• frame
• background
• watermark
• pdf
• metadata
• multitask

These capabilities allow applications and workflows to perform operations such as:

• format conversion
• resizing and scaling
• cropping
• rotation and flipping
• compression and optimization
• enhancement
• padding and framing
• background manipulation
• watermarking
• metadata extraction
• multi-step transformations.

For most file-producing image operations, /v1/image returns signed output URLs under the public /image/* path. For the metadata action, the endpoint returns structured JSON metadata instead of hosted output files.

PDF Processing #

PDF-related operations are handled through:

• /v1/pdf

This endpoint accepts multipart/form-data PDF uploads and supports a broad public action surface for document workflows. The documented public actions are:

• merge
• to-images
• compress
• extract-images
• watermark
• rotate
• metadata
• reorder
• delete-pages
• extract
• flatten
• encrypt
• decrypt
• split

These capabilities enable workflows such as:

• merging multiple PDFs
• converting PDF pages to images
• compressing documents
• extracting embedded images
• watermarking pages
• rotating documents or pages
• reordering pages
• deleting pages
• extracting pages
• flattening documents
• encrypting and decrypting PDFs
• splitting documents into multiple outputs.

Successful file-producing PDF operations return signed output URL values, including single-output and multi-output response patterns depending on the action.

Media Conversion and Transformation #

Davix H2I supports conversion and transformation workflows across its image and PDF capability surfaces. Rather than exposing a separate public “media transformation” endpoint, the platform provides these capabilities through the operations supported under /v1/image, /v1/pdf, and related processing flows. This allows assets to be adapted between different formats and output structures depending on the requested task.

Analysis Tools #

Davix H2I includes analysis-oriented tooling through:

• /v1/tools

This endpoint accepts uploaded image files and supports single and multitask execution modes for analysis tools. The tools pipeline executes analyzers including:

• metadata
• EXIF
• hash
• palette
• similarity
• quality
• efficiency
• transparency.

These tools are intended for workflows that need structured inspection or analysis of media assets rather than only file transformation.

Unlike the file-producing output flows used by /v1/h2i, many /v1/image actions, and /v1/pdf, the current /v1/tools implementation returns structured JSON analysis results and does not currently persist generated tool outputs into public/tools.

Automation Workflows #

Davix H2I is designed to function as a processing component inside automated systems. Because its capabilities are accessible through API requests, workflows can generate content dynamically, submit that content for processing, receive either output files or structured results, and continue downstream processing automatically.

A typical workflow can include:

1. Generating content or preparing files in an application or automation.
2. Sending the content to the appropriate Davix H2I endpoint.
3. Receiving the result as a generated file URL or structured response data.
4. Storing, distributing, or further processing that result in the calling system.

Output Handling #

For file-producing operations, Davix H2I serves generated outputs through public output paths including:

• /h2i/*
• /image/*
• /pdf/*

When signed output protection is enabled, these output URLs are protected through signature and expiry validation.

Not all capabilities return hosted files. Some operations return structured JSON data instead. This is the case for /v1/tools and for metadata-oriented flows such as /v1/image action metadata.

Integration Flexibility #

Davix H2I can be integrated into backend services, automation pipelines, websites, CMS environments, and other systems capable of making HTTP requests or using supported integrations. This allows the platform to act as a reusable backend processing layer across many different environments.

Summary #

Davix H2I provides a structured set of backend processing capabilities through four main public endpoint groups: /v1/h2i, /v1/image, /v1/pdf, and /v1/tools. These capabilities include HTML rendering, image processing, PDF processing, media conversion and transformation workflows, and analysis-oriented tooling.

All supported operations are executed through the H2I engine (PixLab), but their outputs are not all shaped the same way. File-producing operations return signed output URL values, while analysis and metadata-oriented operations can return structured JSON payloads instead.