The PDF endpoint lets you work directly with PDF files through the Davix H2I API. It is designed for document-processing tasks such as merging PDFs, converting PDF pages into images, compressing PDFs, extracting images, adding watermarks, rotating pages, updating metadata, reordering pages, deleting pages, extracting page ranges, flattening PDFs, encrypting, decrypting, and splitting files. 

The public PDF endpoint supports these actions: merge, to-images, compress, extract-images, watermark, rotate, metadata, reorder, delete-pages, extract, flatten, encrypt, decrypt, and split. 

Yes. Davix H2I is designed to support automated document workflows, including systems that need to generate, modify, transform, or route PDF files as part of larger applications and automation pipelines.

No. Davix H2I provides PDF-processing capabilities as a backend service, so you can add PDF operations to your workflows without building and maintaining the underlying infrastructure yourself. 

You connect to the PDF endpoint through the public API using your API key. The /v1/pdf route is part of the public Davix H2I API surface and is designed for direct integration into applications, backend services, and workflows.

The PDF endpoint accepts PDF uploads as its main input. It also supports one optional image upload for watermark-related workflows when needed.

Yes. The merge action is supported for combining PDF files into a single output document. 

Yes. The to-images action is supported for turning PDF pages into image outputs. The endpoint also includes options related to page selection, output format, quality, and density for these workflows. 

Yes. The extract-images action is supported for retrieving embedded images from PDF documents. 

Yes. The PDF endpoint supports watermarking. It includes support for text-based watermark settings and can also work with an uploaded image for watermark-related processing.

Yes. The PDF endpoint supports rotate, reorder, delete-pages, and extract, which makes it suitable for document-editing workflows that need page-level control. 

Yes. The split action is supported for dividing a PDF into multiple output files based on page ranges.

Yes. The metadata action is supported. The public PDF examples also show support for metadata fields such as title, author, subject, keywords, creator, and producer, along with an option to clean metadata before applying updates. 

Yes. The PDF endpoint supports both encrypt and decrypt, which allows it to be used in workflows that need password protection or controlled document access. 

Successful PDF requests return either a single output URL or a results array, depending on the action. Output files are returned through the public PDF output path under /pdf/*.

Yes. Davix H2I is designed to work across custom applications, backend services, websites, and automation environments, which makes the PDF endpoint suitable for many different implementation styles.

The PDF endpoint is suitable for developers, product teams, businesses, agencies, and automation builders who need document-processing features inside their own systems and workflows. 

If a request is invalid, missing required input, or uses unsupported files or parameters, the API returns a structured error response so your system can detect the problem and handle it correctly. For the full list of PDF-related errors, users should check the Errors and Limits section of the documentation.

Yes. The PDF endpoint is subject to upload rules, page-related limits for certain actions, and service-level usage controls. For the latest values and usage rules, users should check the Errors and Limits section of the documentation.

You get access to the Davix H2I PDF-processing capabilities through the public API, allowing your system to perform document operations without building a separate PDF-processing backend. For plan details and commercial information, users should check the Pricing page.