Many callas tools are available through a CLI or command-line interface. The interface use is extensive and highly detailed, and easily integrated in larger solutions. Often, testing production-level integrations are quickest and easiest using this flexible command-line interface.

The CLI is available on all supported platforms, and depending on licensing can be initiated multiple times on the same machine to increase processing speed. For integration into web applications the CLI modules are also available as ready-to-use docker images. Licensing can then take place using the License Server or through an OEM agreement.

The pdfEngine SDK offers the functionality available in the pdfToolbox and pdfaPilot products in a single software development kit.

The SDK supports integrations in C/C++, C#, .NET, and Java environments; it comes with full documentation and a sample application to enable rapid development.

The SDK is available on all supported platforms and supports multithreading.

This is the most straightforward way to integrate the callas technoloy into scalable web applications. It comes as ready-to-use docker images that support queuing. For pdfToolbox the REST API is identical to pdfToolbox in the cloud.

Licensing can take place using the License Server or through an OEM agreement.

Different callas solutions allow integration using (REST) APIs. 
More specifically:

• pdfToolbox in the Cloud is a complete SaaS implementation of the pdfToolbox engine. It allows performing pdfToolbox-related tasks without installing anything on the target machine. Anything that is possible using a process plan in pdfToolbox, can be automated through this SaaS solution. pdfToolbox in the cloud is available only via OEM licensing.
• pdfNest is a nesting and ganging API. Input consists of job parameters such as sheet and page sizes and the number of imprints. Nesting takes place using SVG contours. Output consists of coordinates. An integration with pdfChip is available to turn the output coordinates into ready-to-use print sheets.

Both pdfToolbox and pdfaPilot can be operated in a “server” mode. In this mode, they are able to scan a series of folders and pick up files from those folders for processing. Processing can be done using preflight profiles or process plans. Server mode supports processing as many files in parallel as possible on the local machine (depending on the number of available processing cores or virtual processing units), and as is allowed by the license.

pdfToolbox Portal also supports hot folders to inject files into the solution. It is also able to drop output files in designated folders for further processing, cutting, or printing.

pdfToolbox Portal comes with an extensive user interface that makes available many common workflow steps such as quality control, correcting files, inspecting files manually, online approval, imposition, RIPping etc.

The user interface for the solution can be rebranded to fit the solution of the OEM partner, and the available functionality can be limited to focus the solution on exactly what is needed for a particular use case.