Print Job Request
Last Updated: July 02, 2026
The Print Job Request API sends the print job to the Application Programming Interface (API) Print Service A PrinterLogic Output connector that lets source systems send print jobs through web requests rather than traditional print queues or drivers. Running on a Service Agent, the API Print Service accepts representational state transfer (RESTful) API calls so apps that do not natively support printing can still print. along with metadata about the file that dictates the destination location, color, duplex, and other finishing options. The Batch Open Request ensures files print in a specific order. It begins the batch printing process and includes an ordered list of print job UUIDs and files. After sending all associated files and the UUID list, the Batch Close Request closes the API call out.
Key Points
- This schema supports the API Print Service. For API Cloud Link schemas, refer to API Cloud Link Schemas.
- If you are using the statusURL callback, the webhook requires authentication. (OAuth for Epic, or username / password).
Troubleshooting Help
In some setups, external applications may need to reach the PrinterLogic Output Service Agent using a DNS name that resolves to an external IP address. However, this can cause issues the following issues:
- The Service Agent cannot resolve the DNS name to its internal IP address.
- External DNS resolution conflicts with internal requirements.
Check if the Service Agent can resolve the DNS name to its internal IP address. If the DNS name doesn't resolve correctly, you may need to modify the hosts file. See Troubleshoot DNS Resolution for Output Automation Service Client
Ensure that the DNS name in the UI matches the one in the certificate used by the Service Agent.
In this topic:
The API Print Service can send documents to the printer via LPR and RAW protocols.
The API Print Service runs on the PrinterLogic Output Service on a Windows or Debian Linux server either on-premise or in your cloud instance. This allows the API Print Service to reach your source application and printers unless Off-Network Print is utilized. This back-end configuration is flexible to your environment’s requirements to function seamlessly with your existing systems and processes.
The API Print Service accepts and processes print jobs concurrently for improved scalability and speed. Documents sent to the same printer will be printed in sequential order.
The Service’s maximum capacity depends on the hardware it is running on and network connection speeds. If capacity is reached, additional Service Agents can be utilized with a load balancer to distribute traffic to a highly available partner Service Agent.
PrinterLogic Output was built to scale with high volumes of input in mind and has been shown to process high volumes of documents in less than a second. Various factors, like job size, sequential printing, and hardware capacity, can affect print job speed.
Your documents sent to the API Print Service pass within a Transport Layer Security (TLS) tunnel to the HTTPS server. Files are also encrypted, while at rest, by the Service after receiving them.
If the API Print Service prints directly to printers on its network, standard LPR or RAW printing may be used, which will not encrypt print files between the Service and printer.
For unsecured or public networks between the Service and your printers, we recommend leveraging Off-Network Print to route documents from your system through a Vasion-hosted gateway in the cloud. The Internal Routing Service, hosted on a Service Agent, opens a communication line to receive and download files to the printer. All print traffic is encrypted during this process.
PrinterLogic Output is supported in both the PrinterLogic and Virtual Appliance platforms. PrinterLogic offers the most flexibility in terms of Vasion's available configuration options.
For print jobs from Epic or our API Service, the Batch Printing functionality lets you collect batches of documents and print them in a specific order every time, ensuring complex processes remain standardized and efficient.